devicenet adapter - rs componentsdocs-europe.electrocomponents.com/webdocs/0034/... · the examples...

DeviceNetAdapter

20-COMM-DFRN 1.xxx

User Manual

Important User InformationSolid state equipment has operational characteristics differing from those ofelectromechanical equipment. “Safety Guidelines for the Application, Installationand Maintenance of Solid State Controls” (Publication SGI-1.1) describes someimportant differences between solid state equipment and hard-wiredelectromechanical devices. Because of this difference, and also because of thewide variety of uses for solid state equipment, all persons responsible for applyingthis equipment must satisfy themselves that each intended application of thisequipment is acceptable.

In no event will the Allen-Bradley Company be responsible or liable for indirect orconsequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrativepurposes. Because of the many variables and requirements associated with anyparticular installation, the Allen-Bradley Company cannot assume responsibility orliability for actual use based on the examples and diagrams.

No patent liability is assumed by Allen-Bradley Company with respect to use ofinformation, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without writtenpermission of the Allen-Bradley Company is prohibited.

Throughout this manual we use notes to make you aware of safety considerations.

Attentions help you:

• identify a hazard• avoid the hazard• recognize the consequences

Important: Identifies information that is especially important for successfulapplication and understanding of the product.

!ATTENTION: Identifies information about practices or circumstancesthat can lead to personal injury or death, property damage, or economicloss.

Shock Hazard labels may be located on or inside the drive to alertpeople that dangerous voltage may be present.

Table of Contents

Preface About This ManualRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . P-2Rockwell Automation Support. . . . . . . . . . . . . . . . . . . . . . . . P-2

Chapter 1 Getting StartedComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Compatible Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Chapter 2 Installing the AdapterPreparing for an Installation. . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Commissioning the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Connecting the Adapter to the Network. . . . . . . . . . . . . . . . . 2-3Connecting the Adapter to the Drive . . . . . . . . . . . . . . . . . . . 2-4Applying Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Chapter 3 Configuring the AdapterConfiguration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Using the PowerFlex HIM . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Using RSNetWorx for DeviceNet . . . . . . . . . . . . . . . . . . . . . 3-3Setting the Node Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Setting the Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Setting the I/O Configuration. . . . . . . . . . . . . . . . . . . . . . . . . 3-8Selecting Master-Slave or Peer-to-Peer . . . . . . . . . . . . . . . . . 3-8Selecting COS, Cyclic, or Polled I/O. . . . . . . . . . . . . . . . . . 3-14Setting a Fault Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Resetting the Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17Viewing the Adapter Configuration . . . . . . . . . . . . . . . . . . . 3-18

Chapter 4 Configuring the ScannerExample Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Setting Up the Scan List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Mapping the Drive Data in the Scanner . . . . . . . . . . . . . . . . . 4-5Saving the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

ii

Chapter 5 Using I/O MessagingAbout I/O Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Understanding the I/O Image. . . . . . . . . . . . . . . . . . . . . . . . . 5-2Using Logic Command/Status . . . . . . . . . . . . . . . . . . . . . . . . 5-4Using Reference/Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Using Datalinks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Example Ladder Logic Programs . . . . . . . . . . . . . . . . . . . . . 5-6ControlLogix Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7PLC-5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9SLC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Chapter 6 Using Explicit MessagingAbout Explicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Formatting Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . 6-2Running Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7ControlLogix Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8PLC-5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10SLC Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Chapter 7 TroubleshootingLocating the Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . 7-1PORT Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2MOD Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2NET A Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Module Diagnostic Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Viewing and Clearing Events . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Appendix A SpecificationsCommunications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Appendix B Adapter ParametersAbout Parameter Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

iii

Appendix C DeviceNet ObjectsIdentity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2Connection Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4Register Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6Parameter Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8Parameter Group Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11PCCC Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13DPI Device Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15DPI Parameter Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-18DPI Fault Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-26DPI Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-28DPI Time Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-30

Appendix D Logic Command/Status WordsPowerFlex 70 and PowerFlex 700 Drives . . . . . . . . . . . . . . D-1

Appendix E Master-Slave I/O ConfigurationM-S Input Parameter Configurations . . . . . . . . . . . . . . . . . . . E-1M-S Output Parameter Configurations. . . . . . . . . . . . . . . . . . E-5

Glossary

Index

iv

Notes:

Preface

About This Manual

Documentation can be obtained online at http://www.ab.com/manuals.

Topic PageRelated Documentation P-1Conventions Used in this Manual P-2Rockwell Automation Support P-2

Related Documentation

For: Refer to: PublicationDeviceNet™ Cablesand Components

DeviceNet Product Overview DN-2.5

DeviceNet NetworkInstallation

DeviceNet Cable System Planning and InstallationManual

DN-6.7.2

DeviceNetNetworks

DeviceNet Starter Kit DN-6.5.16

DriveExplorer™ DriveExplorer Getting Results ManualOnline help (installed with the software)

9306-5.2

DriveTools 2000™ DriveTools 2000 Online Help –DriveTools32™ DriveTools32 Getting Started Manual

Online help installed with the software9303-5.23

HIM HIM Quick Reference 20HIM-QR001…Logix 5550 ControlLogix DeviceNet Scanner Installation Instructions 1756-5.66PowerFlex™ 70Drive

PowerFlex 70 User ManualPowerFlex 70 Reference Manual

20A-UM001…20A-RM001…

PowerFlex 700Drive

PowerFlex 700 User ManualPowerFlex 700 Reference Manual

20B-UM001…20B-RM001…

RSLinx™ Getting Results with RSLinxOnline help (installed with the software)

9399-WAB32GR

RSLogix™ 5 RSLogix 5 Getting Results GuideOnline help (installed with the software)

9399-RL53GR

RSLogix 500 RSLogix 500 Getting Results GuideOnline help (installed with the software)

9399-RL50GR

RSLogix 5000 RSLogix 5000 Getting Results GuideOnline help (installed with the software)

9399-RLD300GR

RSNetWorx™ forDeviceNet

RSNetWorx for DeviceNet Getting Results GuideOnline help (installed with the software)

9398-DNETGR

SLC 500™ and1747-SDN

DeviceNet Scanner Module Installation InstructionsDeviceNet Scanner Module Configuration Manual

1747-5.81747-6.5.2

PLC-5™ and1771-SDN

DeviceNet Scanner Module Installation InstructionsDeviceNet Scanner Module Configuration Manual

1747-5.141771-6.5.118

P-2 About 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 theparameter name. For example Parameter 01 - [DPI Port].

• Menu commands are shown in bold type face and follow the formatMenu > Command. For example, if you read “Select File > Open,”you should click the File menu and then click the Open command.

• RSNetWorx for DeviceNet (version 2.22.18) and RSLinx (version2.10.118) were used for the examples in this manual. Differentversions of the software may differ in appearance and procedures.

• The firmware release is displayed as FRN X.xxx. The “FRN”signifies Firmware Release Number. The “X” is the major releasenumber. The “xxx” is the minor update number. This manual is forFirmware release 1.xxx.

• This manual provides information about the DeviceNet adapter andusing it with PowerFlex drives. The adapter can be used with otherproducts that implement DPI. Refer to the documentation for yourproduct for specific information about how it works with the adapter.

Rockwell Automation offers support services worldwide, with over 75sales/support offices, over 500 authorized distributors, and over 250authorized systems integrators located through the United States alone.In addition, Rockwell Automation representatives are in every majorcountry in the world.

Local Product Support

Contact your local Rockwell Automation representative for sales andorder support, product technical training, warranty support, and supportservice agreements.

Technical Product Assistance

If you need to contact Rockwell Automation for technical assistance,please review the information in Chapter 7, Troubleshooting first. If youstill have problems, then call your local Rockwell Automationrepresentative.

Conventions Used in this Manual

Rockwell Automation Support

Chapter 1

Getting Started

The 20-COMM-D DeviceNet adapter is an embedded communicationoption for any one drive in the PowerFlex family. It can also be usedwith other Allen-Bradley products implementing DPI™, a functionalenhancement to SCANport™.

Figure 1.1 Components of the Adapter

Topic Page Topic PageComponents 1-1 Safety Precautions 1-4Features 1-2 Quick Start 1-5Compatible Products 1-3 Modes of Operation 1-6Required Equipment 1-3

Components

# Part Description� Status

IndicatorsThree LEDs that indicate the status of the connected drive,adapter, and network. Refer to Chapter 7, Troubleshooting.

� DPIConnector

A 20-pin, single-row shrouded male header. An Internal Interfacecable is connected to this connector and a connector on the drive.

� DeviceNetConnector

A 5-pin connector to which a 5-pin linear plug can be connected.

� NodeAddressSwitches

Switches for setting the node address.

� Data RateSwitch

Switch for setting the DeviceNet data rate at which the adaptercommunicates.

�

�

�

�

�

1-2 Getting Started

The DeviceNet adapter features the following:

• The adapter is mounted in the PowerFlex drive. It receives therequired power from the drive and from the DeviceNet network.

• Switches let you set a node address and network data rate beforeapplying power to the PowerFlex drive. Alternatively, you candisable the switches and use parameters to configure these features.

• Captive screws are used to secure and ground the adapter to thedrive.

• A number of configuration tools can be used to configure the adapterand connected drive. The tools include the PowerFlex HIM on thedrive, network software such as RSNetWorx for DeviceNet, ordrive-configuration software such as DriveExplorer (version 2.01 orhigher) or DriveTools 2000 (version 1.xx or higher).

• Status indicators report the status of the drive communications,adapter, and network. They are visible both when the cover is openedand when it is closed.

• I/O, including Logic Command/Reference and up to four pairs ofDatalinks, may be configured for your application using a parameter.

• Explicit and UCMM (Unconnected Message Manager) Messages aresupported.

• Multiple data exchange methods, including Polled, Cyclic, andChange of State (COS), can be used to transmit data between thenetwork and adapter.

• Master-Slave or Peer-to-Peer hierarchies can be set up so that theadapter and connected PowerFlex drive transmit data to and fromeither a scanner or another PowerFlex drive on the network.

• User-defined fault actions determine how the adapter and PowerFlexdrive respond to communication disruptions on the network andcontrollers in idle mode.

• Faulted node recovery is supported. You can configure a device evenwhen it is faulted on the network if you have a configuration tool thatuses faulted node recovery and have set the data rate switch to“PGM” (Program). With the PGM setting, the adapter usesparameter settings for the data rate and node address instead ofswitch settings.

Features

Getting Started 1-3

The DeviceNet adapter is compatible with Allen-Bradley PowerFlexdrives and other products that support DPI. DPI is a second generationperipheral communication interface. It is a functional enhancement toSCANport. At the time of publication, compatible products include:

• PowerFlex 70 drives• PowerFlex 700 drives• PowerFlex 7000 drives

Equipment Shipped with the Adapter

When you unpack the adapter, verify that the package includes:

User-Supplied Equipment

To install and configure the DeviceNet adapter, you must supply:

Compatible Products

Required Equipment

❑ One DeviceNet adapter❑ A 2.54 cm (1 in.) and a 15.24 cm (6 in.) Internal Interface cable

(only one cable is needed to connect the adapter to the drive)❑ One five-pin linear DeviceNet plug

(connected to the DeviceNet connector on the adapter)❑ One grounding wrist strap❑ This manual

❑ A small flathead screwdriver❑ DeviceNet cable

– Thin cable with an outside diameter of 6.9 mm (0.27 in.) isrecommended

❑ Configuration tool, such as:– PowerFlex HIM– DriveExplorer (version 2.01 or higher)– DriveTools 2000 (version 1.xx or higher)– RSNetWorx for DeviceNet– Smart Self-powered Serial Converter (1203-SSS, v3.001 or higher)

❑ Computer with a DeviceNet communications adapter installed(Examples: 1784-PCD, 1784-PCID, 1784-PCIDS, or 1770-KFD)

❑ Controller configuration software(Examples: RSLogix5, RSLogix500, or RSLogix 5000)

1-4 Getting Started

Please read the following safety precautions carefully.

Safety Precautions

!ATTENTION: Risk of injury or equipment damage exists. Onlypersonnel familiar with drive and power products and the associatedmachinery should plan or implement the installation, start-up,configuration, and subsequent maintenance of the product using aDeviceNet adapter. Failure to comply may result in injury and/orequipment damage.

!ATTENTION: Risk of injury or death exists. The PowerFlex drivemay contain high voltages that can cause injury or death. Remove allpower from the PowerFlex drive, and then verify power has beenremoved before installing or removing a DeviceNet adapter.

!ATTENTION: Risk of injury or equipment damage exists. DPI orSCANport host products must not be directly connected together via1202 cables. Unpredictable behavior due to timing and other internalprocedures can result if two or more devices are connected in thismanner.

!ATTENTION: Risk of injury or equipment damage exists. If theDeviceNet adapter is transmitting control I/O to the drive, the drive mayfault when you reset the adapter. Determine how your drive willrespond before resetting an adapter.

!ATTENTION: Risk of injury or equipment damage exists.Parameters 10 - [Comm Flt Action], 11 - [Idle Flt Action], and 34 -[Peer Flt Action] let you determine the action of the adapter andconnected PowerFlex drive if communications are disrupted. Bydefault, these parameters fault the PowerFlex drive. You can set theseparameters so that the PowerFlex drive continues to run. Precautionsshould be taken to ensure that the settings of these parameters do notcreate a hazard of injury or equipment damage.

!ATTENTION: Hazard of injury or equipment damage exists. When asystem is configured for the first time, there may be unintended orincorrect machine motion. Disconnect the motor from the machine orprocess during initial system testing.

!ATTENTION: Hazard of injury or equipment damage exists. Theexamples in this publication are intended solely for purposes ofexample. There are many variables and requirements with anyapplication. Rockwell Automation does not assume responsibility orliability (to include intellectual property liability) for actual use of theexamples shown in this publication.

Getting Started 1-5

This section is designed to help experienced users start using theDeviceNet adapter. If you are unsure how to complete a step, refer to thereferenced chapter.

Quick Start

Step Refer to1 Review the safety precautions for the adapter. Throughout

This Manual2 Verify that the PowerFlex drive is properly installed. Drive User

Manual3 Commission the adapter.

Set a unique node address and the appropriate data rate using theswitches on the adapter. If desired, you can disable the switches anduse parameter settings instead.

Chapter 2,Installing theAdapter

4 Install the adapter.Verify that the PowerFlex drive and DeviceNet network are notpowered. Then, connect the adapter to the network using aDeviceNet cable and to the drive using the Internal Interface cable.Use the captive screws to secure and ground the adapter to thedrive.


5 Apply power to the adapter.The adapter receives power from the drive and network. Applypower to the network and to the drive. The status indicators shouldbe green. If they flash red, there is a problem. Refer to Chapter 7,Troubleshooting.


6 Configure the adapter for your application.Set the parameters for the following features as required by yourapplication:• Node address and data rate (if the Data Rate switch is set to

“PGM”).• I/O configuration.• Change of State, Cyclic, or polled I/O data exchange.• Master-slave or peer-to-peer hierarchy.• Fault actions.

Chapter 3,Configuringthe Adapter

7 Apply power to the DeviceNet master and other devices on thenetwork.Verify that the master and network are installed and functioning inaccordance with DeviceNet standards, and then apply power tothem.

DeviceNetCableSystemPlanning andInstallationManual

8 Configure the scanner to communicate with the adapter.Use a network tool such as RSNetWorx for DeviceNet to configurethe scanner on the network. Make sure to:• Set up the scan list.• Map the adapter data to the scan list.• Save your DeviceNet configuration to the scanner and a file.

Chapter 4,Configuringthe Scanner

9 Create a ladder logic program.Use a programming tool such as RSLogix to create a ladder logicprogram that enables you to do the following:• Control the adapter and connected drive.• Monitor or configure the drive using Explicit Messages.

Chapter 5,Using I/OMessaging

Chapter 6,Using ExplicitMessaging

1-6 Getting Started

The adapter uses three status indicators to report its operating status.They can be viewed on the adapter or through the drive cover. See Figure1.2.

Figure 1.2 Status Indicators (location on drive may vary)

Modes of Operation

# StatusIndicator

Status(1)

(1) If all status indicators are off, the adapter is not receiving power. Refer to Chapter 2,Installing the Adapter, for instructions on installing the adapter. If any other conditionsoccur, refer to Chapter 7, Troubleshooting.

Description

� PORT Green Normal Operation. The adapter is properly connected andis communicating with the drive.

FlashingGreen

The adapter is in the process of establishing a connectionto the drive. This status indicator will turn solid green orred.

� MOD Green Normal Operation. The adapter is operational and istransferring I/O data.

FlashingGreen

Normal Operation. The adapter is operational but is nottransferring I/O data.

� NET A Green Normal Operation. The adapter is properly connected andcommunicating on the network.

FlashingGreen

The adapter is properly connected but is notcommunicating with any devices on the network.

� NET B Off Not used for DeviceNet.

PWR

STS

PORT

MOD

NET A

NET B

�

�

�

��

�

Chapter 2

Installing the Adapter

Chapter 2 provides instructions for installing the adapter on a PowerFlexdrive.

Before installing the DeviceNet adapter:

• Read the DeviceNet Product Overview Manual, Publication DN-2.5,and the DeviceNet Cable System Planning and Installation Manual,Publication DN-6.7.2. These manuals will provide information onselecting cables, setting up a network, and network basics.

• Verify that you have all required equipment. Refer to Chapter 1,Getting Started.

To commission the adapter, you must set a unique node address and thedata rate that is used by the network. (Refer to the Glossary for detailsabout data rates and node addresses.)

Important: New settings are recognized only when power is applied tothe adapter. If you change a setting, cycle power.

Topic PagePreparing for an Installation 2-1Commissioning the Adapter 2-1Connecting the Adapter to the Network 2-3Connecting the Adapter to the Drive 2-4Applying Power 2-6

Preparing for an Installation

Commissioning the Adapter

!ATTENTION: Risk of equipment damage exists. The DeviceNetadapter contains ESD (Electrostatic Discharge) sensitive parts that canbe damaged if you do not follow ESD control procedures. Static controlprecautions are required when handling the adapter. If you areunfamiliar with static control procedures, refer to Guarding AgainstElectrostatic Damage, Publication 8000-4.5.2.

2-2 Installing the Adapter

1. Set the node address switches.

Figure 2.1 Setting the Node Address

2. Set the data rate switch.

Figure 2.2 Setting the Data Rate

Setting Description0-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 alluncommissioned devices. We recommend that you do not use this addressas the final adapter address.

Important: If the Data Rate switch is set to “PGM” (Program), the adapterwill use the setting of Parameter 03 - [DN Addr Cfg] for the node address.The default parameter setting is 63. Refer to Chapter 3, Configuring theAdapter.

64 – 99 Do not use. The adapter will not recognize these addresses.

Setting DescriptionAuto The adapter is set to the data rate used by other network devices. Another

device on the network must be set to a data rate.125 K250 K500 K

The adapter is set to the respective data rate.

PGM The adapter uses the setting of Parameter 05 - [DN Rate Cfg] for the datarate. This is the default parameter setting. Refer to Chapter 3, Configuringthe Adapter.

21

0

98

34

5

67

21

0

98

34

5

67

Tens OnesDigit Digit

125K

250K500K PGM

AUTO

Installing the Adapter 2-3

1. Remove power from the network and drive.

2. Use static control precautions.

3. Connect a DeviceNet cable to the network, and route it through thebottom of the PowerFlex drive. DeviceNet Thin cable with anoutside diameter of 6.9 mm (0.27 in.) is recommended. (See Figure2.5.)

Important: Maximum cable length depends on data rate. Refer tothe Glossary.

4. Connect a 5-pin linear plug to the DeviceNet cable.

A 10-pin linear plug is not supported. A 5-pin linear plug is shippedwith the adapter.

Figure 2.3 Connecting a 5-Pin Linear Plug to the Cable

5. Connect the DeviceNet cable to the adapter, and secure it with thetwo screws. (See Figure 2.4.)

Connecting the Adapter to the Network

!ATTENTION: Risk of injury or death exists. The PowerFlex drivemay contain high voltages that can cause injury or death. Removepower from the drive, and then verify power has been discharged beforeinstalling or removing an adapter.

Terminal Color Signal Function5 Red V+ Power Supply4 White CAN_H Signal High3 Bare SHIELD Shield2 Blue CAN_L Signal Low1 Black V– Common

WhiteBareBlueBlack

5 Red

4321


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 andthen to DPI connector on the adapter.

Figure 2.4 DPI Ports and Internal Interface Cables

Connecting the Adapter to the Drive

# Description # Description� 15.24 cm (6 in.) Internal Interface cable � DeviceNet cable� DPI Connector � 2.54 cm (1 in.) Internal Interface cable

PowerFlex 70 Drive

PowerFlex 700 Drive0 - 1 Frame

PowerFlex 700 Drive2 Frame & Larger

DeviceNet Adapter

�

�

�

�

Installing the Adapter 2-5

4. Mount the adapter on the drive, using the four captive screws tosecure it in place and ground it to the drive.

Important: On a PowerFlex 700 drive, tighten the screw in the lowerleft hole to ground the adapter.On a PowerFlex 70 drive, tighten the screw in the lowerright hole to ground the adapter.

Figure 2.5 Mounting the Adapter

PowerFlex 700 Drive (0 - 1 Frames)Adapter mounts on door.

PowerFlex 700 Drive (2 Frame & Larger)Adapter mounts in drive.

PowerFlex 70 DriveAdapter mounts in drive.


1. Close the door or reinstall the cover on the drive. The statusindicators can be viewed on the front of the drive after power hasbeen applied.

2. Ensure that the adapter will have a unique address on the networkand is set at the correct data rate or to autobaud. If a new data rate oraddress is needed, reset its switches (refer to Commissioning theAdapter in this chapter).

3. Apply power to the network.

4. Apply power to the PowerFlex drive. The adapter receives its powerfrom the connected drive and network. When you apply power to theproduct and network for the first time, the status indicators should begreen after an initialization. If the status indicators go red, there is aproblem. Refer to Chapter 7, Troubleshooting.

5. If the data rate switch is set to “PGM,” use a configuration tool to setthe data rate and node address parameters in the adapter (Chapter 3,Configuring the Adapter). If you are using RSNetWorx forDeviceNet, you need to create a point-to-point connection to thedrive.

6. Apply power to the master device (scanner) and other devices on thenetwork.

Applying Power

!ATTENTION: Risk of equipment damage, injury, or death exists.Unpredictable operation may occur if you fail to verify that parametersettings and switch settings are compatible with your application.Verify that settings are compatible with your application beforeapplying power to the drive.

Chapter 3

Configuring the Adapter

Chapter 3 provides instructions and information for setting theparameters in the adapter.

For a list of parameters, refer to Appendix B, Adapter Parameters. Fordefinitions of terms in this chapter, refer to the Glossary.

The DeviceNet adapter stores parameters and other information in itsown non-volatile memory. You must, therefore, access the adapter toview and edit its parameters. The following tools can be used to accessthe adapter parameters:

RSNetWorx for DeviceNet (version 2.22.18) and RSLinx (version2.10.118) were used for examples in this manual. Different versions ofsoftware may differ in appearance and procedures.

Topic Page Topic PageConfiguration Tools 3-1 Selecting Master-Slave or Peer-to-Peer 3-8Using the PowerFlex HIM 3-2 Selecting COS, Cyclic, or Polled I/O 3-14Using RSNetWorx for DeviceNet 3-3 Setting a Fault Action 3-16Setting the Node Address 3-7 Resetting the Adapter 3-17Setting the Data Rate 3-7 Viewing the Adapter Configuration 3-18Setting the I/O Configuration 3-8

Configuration Tools

Tool Refer To:DriveExplorer Software (version 2.01or higher)

DriveExplorer Getting Results Manual,Publication 9306-5.3, or the online help

DriveTools 2000 Software (version 1.xxor higher)

DriveTools 2000 Online Help

PowerFlex HIM page 3-2RSNetWorx for DeviceNet Software page 3-3

TIP: Explicit Messaging can also be used to configure an adapter anddrive. Refer to Chapter 6, Using Explicit Messaging.

3-2 Configuring the Adapter

If your drive has either an LED or LCD HIM (Human InterfaceModule), access parameters in the adapter as shown below. It isrecommended that you read through the steps for your HIM beforeperforming the sequence. For additional HIM information, refer to yourPowerFlex Drive User Manual or the HIM Quick Reference card.

Using an LED HIM

Using an LCD HIM

Using the PowerFlex HIM

Step Key(s) Example Screens1. Press the ALT and then Sel

(Device) to display the DeviceScreen.

2. Press the Up Arrow or DownArrow to scroll to the DeviceNetadapter. Letters represent files inthe drive, and numbers representports. The adapter is usuallyconnected to port 5.

3. Press the Enter key to enter yourselection. A parameter databaseis constructed, and then the firstparameter is displayed.

4. Edit the parameters using thesame techniques that you use toedit drive parameters.

Step Key(s) Example Screens1. In the main menu, press the Up

Arrow or Down Arrow to scroll toDevice Select.

2. Press Enter to enter yourselection.

3. Press the Up Arrow or DownArrow to scroll to the DeviceNetadapter (20-COMM-D).

4. Press Enter to select theDeviceNet adapter. A parameterdatabase is constructed, andthen the main menu for theadapter is displayed.

5. Edit the parameters using thesame techniques that you use toedit drive parameters.

OR

SelALT

Device

OR

ORF-> Stopped Auto

0.00 Hz

Main Menu:DiagnosticsParameterDevice Select

Port 5 Device

20-COMM-D


Configuring the Adapter 3-3

RSNetWorx for DeviceNet is a Rockwell Software application that canbe 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 inRSLinx. The driver provides a communications link between thecomputer and DeviceNet network.

Figure 3.1 Configure Drivers Dialog Box with a Configured Driver

Using RSNetWorx for DeviceNet

Step Icons1. Start RSLinx, and select Communications > Configure

Drivers to display the Configure Drivers dialog box.

2. In the Available Driver Types box, select DeviceNetDrivers, and then click Add New. The DeviceNet DriverSelection dialog box appears.

3. In the Available DeviceNet Drivers list, select the adapterconnected to your computer, and then click Select. A DriverConfiguration dialog box appears.

4. Configure the driver for your computer and networksettings, and then click OK. The Configure Drivers dialogbox reports the progress of the configuration. Then, theAdd New RSLinx Driver dialog box appears.

5. Type a name (if desired), and then click OK. The ConfigureDrivers dialog box reappears, and the new driver is in theConfigured Drivers List (Figure 3.1).

6. Click Close to close the dialog box. Leave RSLinx running.

Shortcut toRSLinx


To go online with RSNetWorx for DeviceNet

You can view the devices on a DeviceNet network by going online. Adevice may appear as an unrecognized device (node 63 in Figure 3.2) ifRSNetWorx for DeviceNet does not have an EDS file for it.

Figure 3.2 Example DeviceNet Network

Step Icons1. After setting up a driver in RSLinx, start RSNetWorx for

DeviceNet.

2. Select Network > Online. If the Browse for Network dialogbox appears, RSLinx has multiple drivers configured.Select your DeviceNet network, and click OK. A promptappears.

3. Click OK to go online. The devices on the network appearin the Configuration View. You can select Graph,Spreadsheet, or Master/Slave views. Figure 3.2 shows anexample network in a Graph view.

Shortcut toRSNetWorx


To create an EDS file

If the adapter and drive appear as an unrecognized device, create an EDSfile for it.

Figure 3.3 EDS Wizard

Step Icons1. Right-click the “Unrecognized Device” icon, and select

Register Device in the menu. The EDS Wizard (Figure3.3) appears.

2. Click Next to display the next step.

3. Select Upload EDS, and then click Next.

4. Type a description (if desired), and then click Next.

5. Under Polled, select Enabled, type 4 in the Input Size andOutput Size boxes, and then click Next. RSNetWorx willupload the EDS file from the drive and adapter.

6. Click Next to display the icon options for the node. Werecommend that you use the icon for your product. You canchange icons by clicking Change icon.

7. Click Next to view a summary, and then click Next again toaccept it.

8. Click Finish to finish the EDS creation. A new iconrepresents the PowerFlex drive and adapter in theConfiguration View.‘

Important: RSNetWorx for DeviceNet (versions 2.22.18and earlier) replaces 32-bit values with exponential values.For the EDS file to work in RSNetWorx, you must edit theEDS file, replacing exponential values with 32-bit values(typically 4294967295), and then restart RSNetWorx.


To access and edit parameters

Parameters in the drive and adapter can be edited with RSNetWorx. Theadapter parameters are appended to the list of drive parameters. InFigure 3.4, for example, the drive has 387 parameters, so parameter 388is the first adapter parameter.

Figure 3.4 Example PowerFlex Drive Dialog Box

Step Icons1. After creating an EDS file, right-click on the icon for the

PowerFlex drive and adapter and select Properties. ThePowerFlex Drive dialog box appears.

2. Click the Device Parameters tab (Figure 3.4). If an EDSEditor message appears, click Upload to load theparameter values in the drive to the computer.

Parameters are displayed in numerical order underParameter. You can either scroll through the list or select aspecific group of parameters in the Groups box. Theavailable groups and the numbers of the adapterparameters will vary based on the type of drive that isconnected to the adapter.

3. In the Current Value column, double-click a value to edit it.

4. Click Apply to save changes to the device.


If the adapter Data Rate switch is set to “PGM,” the value of Parameter03 - [DN Addr Cfg] determines the node address. We recommend thatyou do not use node address 63 because all new devices use it as thedefault address. Address 63 is also used for Automatic Device Recovery(ADR).

1. Set the value of Parameter 03 - [DN Addr Cfg] to a unique nodeaddress.

Figure 3.5 DeviceNet Node Address Screen on an LCD HIM

2. Reset the adapter. Refer to the Resetting the Adapter section in thischapter.

If the adapter Data Rate switch is set to “PGM,” the value of Parameter05 - [DN Rate Cfg] determines the DeviceNet data rate. The Autobaudsetting will detect the data rate used on the network if another device issetting the data rate. Your application may require a different setting.

1. Set the value of Parameter 05 - [DN Rate Cfg] to the data rate atwhich your network is operating.

Figure 3.6 DeviceNet Data Rate Screen on an LCD HIM


Setting the Node Address

Port 5 Device

20-COMM-D

Parameter #: 3DN Addr Cfg

630 <> 63

Default = 63

TIP: If you are using RSNetWorx for DeviceNet, select Network >Single Browse Path to see the new address; then delete the old address.

Setting the Data Rate

Value Baud Rate0 125 kbps1 250 kbps2 500 kbps3 Autobaud (Default)

Port 5 Device

20-COMM-D

Parameter #: 5DN Rate Cfg

3Autobaud


The I/O configuration determines the type of data sent to the drive. LogicCommand/Status, Reference/Feedback, and Datalinks may be enabledor 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

Bit 0 is the right-most bit. In Figure 3.7, it is highlighted and equals“1.”

2. Set a Master-Slave or Peer-to-Peer hierarchy. Refer to the SelectingMaster-Slave or Peer-to-Peer section in this chapter.

3. If you enabled Logic Command/Reference, configure the parametersin the drive to accept the logic and Reference from the adapter. Forexample, set Parameter 90 - [Speed Ref A Sel] in a PowerFlex 70or 700 drive to “DPI Port 5” so that the drive uses the Referencefrom the adapter. Also, verify that the mask parameters (for example,Parameter 276 - [Logic Mask]) in the drive are configured toreceive the desired logic from the adapter.

4. If you enabled one or more Datalinks, configure parameters in thedrive to determine the source and destination of data in theDatalink(s). Also, ensure that the DeviceNet adapter is the onlyadapter using the enabled Datalink(s).


A hierarchy determines the type of device with which the adapterexchanges data. In a Master-Slave hierarchy, an adapter exchanges datawith a scanner. In a Peer-to-Peer hierarchy, an adapter can exchange datawith one or more DeviceNet adapter(s) connected to PowerFlex drivesthat have similar data structures.

Setting the I/O Configuration

Bit Description0 Logic Command/Reference (Default)1 Datalink A2 Datalink B3 Datalink C4 Datalink D5 - 15 Not Used

Port 5 Device

20-COMM-D

Parameter #: 13DPI I/O Configx x x x x x x x x x x 0 0 0 0 1Cmd/Ref b00

Selecting Master-Slave or Peer-to-Peer


To set a Master-Slave hierarchy

1. Enable the desired I/O in Parameter 13 - [DPI I/O Config]. Refer toFigure 3.7.

2. Set the bits in the Parameter 25 - [M-S Input]. This parameterdetermines the data transmitted from the scanner to the drive. A “1”enables the I/O. A “0” disables the I/O.

Figure 3.8 Master-Slave Input Screen on an LCD HIM


3. Set the bits in the Parameter 26 - [M-S Output]. This parameterdetermines the data transmitted from the drive to the scanner. A “1”enables the I/O. A “0” disables the I/O.

Figure 3.9 Master-Slave Output Screen on an LCD HIM



The adapter is ready to receive I/O from the master (i.e., scanner). Youmust now configure the scanner to recognize and transmit I/O to theadapter. Refer to Chapter 4, Configuring the Scanner.

Bit Description0 Logic Command/Reference (Default)1 Datalink A Input2 Datalink B Input3 Datalink C Input4 Datalink D Input5 - 15 Not Used

Port 5 Device

20-COMM-D

Parameter #: 25M-S Inputx x x x x x x x x x x 0 0 0 0 1Cmd/Ref b00

Bit Description0 Status/Feedback (Default)1 Datalink A Output2 Datalink B Output3 Datalink C Output4 Datalink D Output5 - 15 Not Used

Port 5 Device

20-COMM-D

Parameter #: 26M-S Outputx x x x x x x x x x x 0 0 0 0 1Status/Fdbk b00


To set an adapter to transmit Peer-to-Peer data

1. Verify that Parameter 41 - [Peer Out Enable] is set to Off. Thisparameter must be set to Off while you configure some of the peeroutput parameters.

Figure 3.10 Peer Out Enable Screen on an LCD HIM

2. Select the source of the data to output to the network in Parameter39 - [Peer A Output].

Figure 3.11 Peer A Output Screen on an LCD HIM

If you are transmitting a 32-bit Reference or 32-bit Datalink, onlyPeer A Output will be available. Peer B Output cannot be used.

3. If desired, select an additional source of the data to output to thenetwork in Parameter 40 - [Peer B Output].

Figure 3.12 Peer B Output Screen on an LCD HIM

Value Setting0 Off (Default)1 On

Port 5 Device

20-COMM-D

Parameter #: 41Peer Out Enable

0Off

Port 5 Device

20-COMM-D

Parameter #: 39Peer A Output

1Cmd/Ref

Value Description0 Off (Default)1 Logic Command/Reference2 - 5 Datalink A, B, C, or D

Input6 - 9 Datalink A, B, C, or D

Output

Port 5 Device

20-COMM-D

Parameter #: 40Peer B Output

2DL A Input


Input6 - 9 Datalink A, B, C, or D

Output


4. Set Parameters 42 - [Peer Out Time] and 43 - [Peer Out Skip] toestablish the minimum and maximum intervals between Peermessages. The minimum interval is set in Parameter 42 - [Peer OutTime]. The maximum interval is the value of Parameter 42 - [PeerOut Time] multiplied by the value of Parameter 43 - [Peer Out Skip].

Figure 3.13 Min Peer TX Time and Peer Out Skip Screens on an LCD HIM

5. Set Parameter 41 - [Peer Out Enable] to On. The adapter willtransmit the data selected in Parameters 39 - [Peer A Output] and40 - [Peer B Output] to the network. Another adapter must beconfigured to receive the data.

To set an adapter to receive Peer-to-Peer data

1. Verify that Parameter 37 - [Peer Inp Enable] is set to Off. Thisparameter must be set to Off while you configure some of the peerinput parameters.

Figure 3.14 Peer Input Enable Screen on an LCD HIM

2. Select the node from which you want to receive data in Parameter35 - [Peer Node to Inp]. Valid nodes must have 20-COMM-Dadapters connected to drives with similar data structures.

Figure 3.15 Peer Node to Input Screen on an LCD HIM

Port 5 Device

20-COMM-D

Parameter #: 42Peer Out Time

10.00 Secs.0 <> 10.00

Port 5 Device

20-COMM-D

Parameter #: 43Peer Out Skip

11 <>16

Value Setting0 Off (Default)1 On

Port 5 Device

20-COMM-D

Parameter #: 37Peer Inp Enable

0Off

Port 5 Device

20-COMM-D

Parameter #: 35Peer Node to Inp

00 <>63

Default = 0


3. Select the destination of the data that is input to the drive inParameter 30 - [Peer A Input].

Figure 3.16 Peer A Input Screen on an LCD HIM

If you are receiving a 32-bit Reference or 32-bit Datalink, only PeerA Input will be available. Peer B Input cannot be used.

4. If desired, select the destination of the data to input to the drive inParameter 31 - [Peer B Input].

Figure 3.17 Peer B Input Screen on an LCD HIM

5. If you are receiving a Logic Command, set the bits in it that shouldbe used in Parameter 32 - [Peer Cmd Mask]. The bit definitions forthe Logic Command word will depend on the drive to which theadapter is connected. Refer to the drive documentation.

Figure 3.18 Peer Logic Command Mask Screen on an LCD HIM

If the adapter receives a Logic Command from both a Master deviceand a Peer device, each command bit must have only one source. Thesource of command bits set to “0” will be the Master device. Thesource of command bits set to “1” will be the Peer device.

Port 5 Device

20-COMM-D

Parameter #: 30Peer A Input

1Cmd/Ref


Input

Port 5 Device

20-COMM-D

Parameter #: 31Peer B Input

2DL A Input


Input

Value Description0 Ignore this command bit.

(Default)1 Use this command bit.

Port 5 Device

20-COMM-D

Parameter #: 32Peer Cmd Mask0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0Bit 0 B00


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

Figure 3.19 Peer Reference Adjust Screen on an LCD HIM

7. Set Parameter 36 - [Peer Inp Timeout] to the maximum amount oftime the adapter will wait for a message before timing out.

Important: This value must be greater than the product ofParameter 42 - [Peer Out Time] multiplied byParameter 43 - [Peer Out Skip] in the adapter fromwhich you are receiving I/O.

Figure 3.20 Minimum Peer Receiving Time Screen on an LCD HIM

!ATTENTION: To guard against equipment damage and/orpersonal injury, note that changes to Parameter 33 - [PeerRef Adjust] take effect immediately. A drive receiving itsReference from peer I/O will receive the newly scaledReference, resulting in a change of speed.

Port 5 Device

20-COMM-D

Parameter #: 33Peer Ref Adjust

0.00 %0.00 <> 199.99

Default = 0.00%

Port 5 Device

20-COMM-D

Parameter #: 36Min Peer Rx Time

10.00 Secs.0.01 <> 180.00

Default = 10.00 Secs


8. Parameter 34 - [Peer Flt Action] sets the action that the adapterwill take if it times out.

Figure 3.21 Peer Fault Action Screen on an LCD HIM

For details, refer to the Setting a Fault Action section in this chapter.

9. Set Parameter 37 - [Peer Inp Enable] to On. The adapter is nowconfigured to receive I/O from the specified node. Ensure that thespecified node is configured to transmit I/O.

The data exchange (sometimes called allocation) is the method that theadapter uses to exchange data on the DeviceNet network. The adaptercan be configured to use one of the following data exchanges:

If “Polled and COS” or “Polled and Cyclic” is used, the adapter receivesthe I/O from the polled messages. It transmits its Logic Status andFeedback in COS or Cyclic messages. Other data is transmitted in Polledmessages.

Cyclic and Polled data exchanges are configured in the scanner, so youonly need to set the I/O configuration in the adapter. COS data exchangemust be configured in both the adapter and the scanner. You need to setthe I/O configuration and COS parameters in the adapter.

!ATTENTION: Risk of injury or equipment damage exists.Parameter 34 - [Peer Flt Action] lets you determine the action of theadapter and connected drive if communications are disrupted. Bydefault, this parameter faults the drive. You can set this parameter sothat the drive continues to run. Precautions should be taken to ensurethat the setting of this parameter does not create a hazard of injury orequipment damage.

Port 5 Device

20-COMM-D

Parameter #: 34Peer Flt Action

0Fault

Value Description0 Fault (Default)1 Stop2 Zero Data3 Hold Last4 Send Flt Cfg

Selecting COS, Cyclic, or Polled I/O

• COS (Change of State) • Polled and COS• Cyclic • Polled and Cyclic• Polled


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 inCOS data exchange.

Figure 3.22 I/O Configuration Screens on an LCD HIM

2. Set the bits in the Logic Status word that should be checked forchanges in Parameter 27 - [COS Status Mask]. The bit definitionsfor the Status Mask will depend on the drive to which you areconnected. Refer to its documentation.

Figure 3.23 COS Status Mask Configuration Screen on an LCD HIM

3. Set the amount of change to the Feedback that is required to trigger aChange of State message in Parameter 28 - [COS Fdbk Change].

Figure 3.24 COS Fdbk Change Configuration Screen on an LCD HIM

The adapter is now configured for COS data exchange. You mustconfigure the scanner to allocate it using COS (Chapter 4, Configuringthe Scanner).

Port 5 Device

20-COMM-D

Parameter #: 13DPI I/O Configx x x x x x x x x x x 0 0 0 0 1Cmd/Ref b00

Port 5 Device

20-COMM-D

Parameter #: 26M-S Outputx x x x x x x x x x x 0 0 0 0 1Status/Fdbk b00

Port 5 Device

20-COMM-D

Parameter #: 27COS Status Mask0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1Bit 0 b00

Value Description0 Ignore this logic bit. (Default)1 Check this logic bit.

Port 5 Device

20-COMM-D

Parameter #: 28COS Fdbk Change

00 <> 4294967295


By default, when communications are disrupted (for example, a cable isdisconnected) or the scanner is idle, the drive responds by faulting if it isusing I/O from the network. You can configure a different response tocommunication disruptions using Parameter 10 - [Comm Flt Action]and a different response to an idle scanner using Parameter 11 - [IdleFlt Action].

To change the fault action• Set the values of Parameters 10 - [Comm Flt Action] and 11 - [Idle

Flt Action] to the desired responses:

Figure 3.25 Fault Action Screens on an LCD HIM

Changes to these parameters take effect immediately. A reset is notrequired.

Setting a Fault Action

!ATTENTION: Risk of injury or equipment damage exists.Parameters 10 - [Comm Flt Action] and 11 - [Idle Flt Action] let youdetermine the action of the adapter and connected drive ifcommunications are disrupted or the scanner is idle. By default, theseparameters fault the drive. You can set these parameters so that the drivecontinues to run. Precautions should be taken to ensure that the settingsof these parameters do not create a hazard of injury or equipmentdamage.

Value Action Description0 Fault (default) The drive is faulted and stopped. (Default)1 Stop The drive is stopped, but not faulted.2 Zero Data The drive is sent 0 for output data after a

communications disruption. This does notcommand a stop.

3 Hold Last The drive continues in its present state after acommunications disruption.

4 Send Flt Cfg The drive is sent the data that you set in the faultconfiguration parameters (Parameters 15 - [Flt CfgLogic] through 24 - [Flt Cfg D2 In]).

Port 5 Device

20-COMM-D

Parameter #: 10Comm Flt Action

0Fault

Port 5 Device

20-COMM-D

Parameter #: 11Idle Flt Action

0Fault


To set the fault configuration parameters

If you set Parameter 10 - [Comm Flt Action], 11 - [Idle Flt Action], or34 - [Peer Flt Action] to the “Send Flt Cfg,” the values in the followingparameters are sent to the drive after a communications fault and/or idlefault occurs. You must set these parameters to values required by yourapplication.

Changes to these parameters take effect immediately. A reset is notrequired.

Changes to switch settings on some adapter parameters require that youreset the adapter before the new settings take effect. You can reset theadapter by cycling power to the drive or by using the followingparameter:

• Set the Parameter 09 - [Reset Module] to Reset Module:

Figure 3.26 Reset Screen on an LCD HIM

When you enter 1 = Reset Module, the adapter will be immediatelyreset. When you enter 2 = Set Defaults, the adapter will set all adapterparameters to their factory-default settings. The value of this parameterwill be restored to 0 = Ready after the adapter is reset.

Parameter Name Description15 Flt Cfg Logic A 16-bit value sent to the drive for Logic Command.16 Flt Cfg Ref A 32-bit value (0 – 4294967295) sent to the drive as a

Reference or Datalink.Important: If the drive uses a 16-bit Reference or 16-bitDatalinks, the most significant word of the value must beset to zero (0) or a fault will occur.

17 – 24 Flt Cfg x1 In orFlt Cfg x2 In

Resetting the Adapter

!ATTENTION: Risk of injury or equipment damage exists. If theadapter is transmitting control I/O to the drive, the drive may fault whenyou reset the adapter. Determine how your drive will respond beforeresetting a connected adapter.

Value Description0 Ready (Default)1 Reset Module2 Set Defaults

Port 5 Device

20-COMM-D

Parameter #: 9Reset Module

1Reset Module


The following parameters provide information about how the adapter isconfigured. You can view these parameters at any time.

Viewing the Adapter Configuration

Number Name Description01 DPI Port The port on the drive to which the adapter is connected. Usually, it is

port 5.02 DPI Data

RateThe data rate used by DPI in the drive. It will be either 125 kbps or500 kbps. It is set in the drive, and the adapter detects it.

04 DN AddrActual

The node address used by the adapter. This will be one of thefollowing values:• The address set by the rotary switches.• The value of Parameter 03 - [DN Addr Cfg] if the switches have

been disabled.• An old address of the switches or parameter if they have been

changed and the adapter has not been reset.06 DN Rate

ActualThe data rate used by the adapter. This will be one of the followingvalues:• The data rate set by the DIP switch.• The value of Parameter 05 - [DN Rate Cfg] if the switches have

been disabled.• An old data rate of the switches or parameter if they have been

changed and the adapter has not been reset.07 Ref/Fdbk Size The size of the Reference/Feedback. It will either be 16 bits or 32

bits. It is set in the drive and the adapter automatically uses thecorrect size.

08 Datalink Size The size of the Datalinks. It will either be 16 bits or 32 bits. It is set inthe drive and the adapter automatically uses the correct size.

12 DN Active Cfg Source from which the adapter node address and data rate aretaken. This will be either switches or parameters in EEPROM. It isdetermined by the settings of the switches on the adapter.

14 DPI I/O Active The Reference/Feedback and Datalinks used by the adapter. Thisvalue is the same as Parameter 13 - [DPI I/O Config] unless theparameter was changed and the adapter was not reset.

Bit Definitions0 = Cmd/Ref1 = Datalink A2 = Datalink B3 = Datalink C4 = Datalink D5 = Not Used6 = Not Used7 = Not Used

BitDefault 10000x xx

0123457 6

Chapter 4

Configuring the Scanner

Chapter 4 provides instructions on how to configure a scanner tocommunicate with the adapter and connected PowerFlex drive.

After the adapter is configured, the connected drive and adapter will be asingle node on the network. This chapter provides the steps that areneeded to configure a simple network like the network in Figure 4.1. Inour example, we will configure the drive for using Logic Command/Status and Reference Feedback over the network.

Figure 4.1 Example DeviceNet Network

Topic Page Topic PageExample Network 4-1 Mapping the Drive Data in the Scanner 4-5Setting Up the Scan List 4-2 Saving the Configuration 4-8

Example Network

Node 0SLC 500 Controller with1747-SDN Scanner

Node 62Computer with 1770-KFD andRSNetWorx for DeviceNet

Node 1PowerFlex 70 Drive withDeviceNet Adapter

4-2 Configuring the Scanner

For the scanner to communicate with a drive, the scanner must beconfigured and the drive’s node number must be added to its scan list.

1. Go online with RSNetWorx for DeviceNet. Refer to the UsingRSNetWorx for DeviceNet section in Chapter 3. The devices on thenetwork are displayed in the configuration view.

Figure 4.2 Configuration View (Graph)

2. Right-click the DeviceNet scanner (node 00 in Figure 4.2) and selectProperties. The Scanner Module dialog box appears.

Important: If your scanner is an unrecognized device, you mustcreate an EDS file for it and then configure it. Create anEDS file by following the instructions in the UsingRSNetWorx for DeviceNet section in Chapter 3.Configure the scanner using the General and Moduletabs. Click Help or refer to your scanner documentationif you need more information.

3. Click the Scanlist tab. A message box prompts you to upload.

4. Click Upload. Data is uploaded from the scanner, and then theScanlist page (Figure 4.3) appears.

5. Select the Automap on Add box (a check mark will appear).

Setting Up the Scan List

Configuring the Scanner 4-3

6. Under Available Devices, select the drive, and then click > (RightArrow) 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/OParameters. The Edit I/O Parameters dialog box (Figure 4.4)appears.


Figure 4.4 Edit I/O Parameters Dialog Box

8. Select the type(s) of data exchange (Polled, Change of State, and /orCyclic). In our example, we selected Polled.

9. Type the number of bytes that are required for your I/O in the RxSize and Tx Size boxes. The size will depend on the following:

• I/O that you enabled in the adapter. This information can befound in Parameter 14 - [DPI I/O Active] in the adapter.

• Size of the Reference/Feedback and Datalinks in your drive. Thisinformation can be viewed using Parameters 07 - [Ref/FdbkSize] and 08 - [Datalink Size] in the adapter. A 16-bit word istwo bytes, and a 32-bit word is four bytes.

• The actual size value used in the Rx Size box can be determinedby the setting of the M-S Input parameter as shown in Table E.Aor Table E.B for “Poll Only.”

• The actual size value used in the Tx Size box can be determinedby the setting of the M-S Output parameter as shown in TableE.C or Table E.D for “Poll Only.”

• Table 4.A and Table 4.B show common configuration Tx/Rxsizes.

In our example, we typed 4 in the Rx Size and Tx Size boxes becausewe enabled only the Logic Command/Status for I/O in the adapterand our drive uses a 16-bit Reference/Feedback.

Both the M-S Input and M-S Output parameters are set to 00001.Therefore, the Logic Command/Status uses 2 bytes and theReference/Feedback uses 2 bytes totaling 4 bytes.


Table 4.A Host Products using 16-bit Reference/Feedback & Datalinks(1)

Table 4.B Host Products using 32-bit Reference/Feedback & Datalinks

10. Set the scan rate. (Click Help for more information.)

11. Click OK. If you changed any settings, a Scanner Applet asks if it isOK to unmap the I/O. Click Yes to continue. The Edit I/OParameters dialog box closes and then the Scanner Module dialogbox (Figure 4.3) reappears. You will map the I/O in the next sectionin this chapter.

Data from I/O messages must be mapped in the scanner. This mappingdetermines where a ladder logic program can find data that is passedover the network. You must map both the Input I/O and the Output I/O.

RxSize

TxSize

Logic Command/Status

Reference/Feedback (16-bit)

Datalinks (16-bit)A B C D

4 4 ✔ ✔

8 8 ✔ ✔ ✔

12 12 ✔ ✔ ✔ ✔

16 16 ✔ ✔ ✔ ✔ ✔

20 20 ✔ ✔ ✔ ✔ ✔ ✔

(1) PowerFlex 70 & 700 use 16-bit.

RxSize

TxSize

Logic Command/Status

Reference/Feedback (32-bit)

Datalinks (32-bit)A B C D

8 8 ✔ ✔

16 16 ✔ ✔ ✔

24 24 ✔ ✔ ✔ ✔

32 32 ✔ ✔ ✔ ✔ ✔

40 40 ✔ ✔ ✔ ✔ ✔ ✔

Data Exchange Rate to setPolled Polled RateChange of State Heartbeat RateCyclic Send Rate

Mapping the Drive Data in the Scanner

For: Refer to:Mapping the Input I/O 4-6Mapping the Output I/O 4-7


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) todisplay 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 (Figure4.3), RSNetWorx has already mapped the I/O. If it is not mapped, clickAutomap to map it. If you need to change the mapping, click Advancedand change the settings. Click Help for assistance.

2. In the Memory box, select a location in scanner memory.

In our example, we are using a 1747-SDN and selected Discrete.

3. In the Start Word box, select the word in memory at which the datashould start. In our example, we selected 1. Logic Status and SpeedFeedback information will be found in I:1.1 and I:1.2, respectively.

Scanner Memory Locations1747-SDN Discrete or M-File1756-DNB Assembly Data1771-SDN Block Xfer 62 – 57


Mapping the Output I/O

1. In the Scanner Module dialog box, click the Output tab. To displaythis 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 (Figure4.3), RSNetWorx has already mapped the I/O. If it is not mapped, clickAutomap to map it. If you need to change the mapping, click Advancedand change the settings. Click Help for assistance.

2. In the Memory box, select a location in scanner memory.

In our example, we are using a 1747-SDN and selected Discrete.

3. In the Start Word box, select the word in memory at which the datashould start. In our example, we selected 1. Logic Command andSpeed Reference data should be written to O:1.1 and O:1.2,respectively.

Scanner Memory Locations1747-SDN Discrete or M-File1756-DNB Assembly Data1771-SDN Block Xfer 62 – 57


After configuring a scanner, you must download it to the scanner. Youshould also save it to a file on your computer.

1. In the Scanner Module dialog box (Figure 4.6), click Apply to savethe configuration to the scanner. A Scanner Configuration Appletappears and asks if it is OK to download the changes.

2. Click Yes to download the changes. The changes are downloadedand then the Scanner Module dialog box reappears.

3. Click OK to close the Scanner Module dialog box.

4. Select File > Save. If this is the first time that you saved the project,the Save As dialog box appears. Navigate to a folder, type a filename, and click Save to save the configuration to a file.

Saving the Configuration

Chapter 5

Using I/O Messaging

Chapter 5 provides information and examples that explain how to useI/O Messaging to control a PowerFlex drive.

On DeviceNet, I/O Messaging is used to transfer the data which controlsthe PowerFlex drive and sets its Reference. I/O can also be used totransfer data to and from Datalinks in PowerFlex drives.

The DeviceNet adapter provides many options for configuring and usingI/O, including the following:

• The size of I/O can be configured by enabling or disabling the LogicCommand/Reference and Datalinks.

• A Master-Slave hierarchy or Peer-to-Peer communications can be setup.

• Change of State, Cyclic, or Polled data exchange methods can beused.

Chapter 3, Configuring the Adapter and Chapter 4, Configuring theScanner discuss how to configure the adapter and scanner on the networkfor these options. The Glossary defines the different options. Thischapter discusses how to use I/O after you have configured the adapterand scanner.

Topic Page Topic PageAbout I/O Messaging 5-1 Example Ladder Logic Programs 5-6Understanding the I/O Image 5-2 ControlLogix Example 5-7Using Logic Command/Status 5-4 PLC-5 Example 5-9Using Reference/Feedback 5-4 SLC Example 5-11Using Datalinks 5-4


About I/O Messaging

5-2 Using I/O Messaging

The DeviceNet specification requires that the terms input and output bedefined from scanner’s point of view. Therefore, Output I/O is data thatis output from the scanner and consumed by the DeviceNet adapter.Input I/O is status data that is produced by the adapter and consumed asinput by the scanner. The I/O image table will vary based on thefollowing:

• Size (either 16-bit or 32-bit) of the Reference/Feedback word andDatalink words used by the drive.

• Configuration of Parameter 13 - [DPI I/O Config] in the adapter. Ifall I/O is not enabled, the image table is truncated. The image tablealways uses consecutive words starting at word 0.

Figure 5.1 illustrates an example of an I/O image with 16-bit words.

Figure 5.1 Example I/O Image with All I/O Enabled

Understanding the I/O Image

Controller Scanner Adapter PowerFlexDrive

DeviceNet DPI

OutputImage(Write)

InputImage(Read)

MessageHandler

MessageBuffer

MessageHandler

0 Logic Status1 Feedback2 Datalink Out A13 Datalink Out A24 Datalink Out B15 Datalink Out B26 Datalink Out C17 Datalink Out C28 Datalink Out D19 Datalink Out D2

0 Logic Command1 Reference2 Datalink In A13 Datalink In A24 Datalink In B15 Datalink In B26 Datalink In C17 Datalink In C28 Datalink In D19 Datalink In D2

Logic CommandReferenceData In A1Data In A2Data In B1Data In B2Data In C1Data In C2Data In D1Data In D2

Logic StatusFeedbackData Out A1Data Out A2Data Out B1Data Out B2Data Out C1Data Out C2Data Out D1Data Out D2

Word and I/O

Using I/O Messaging 5-3

An image that uses 32-bit words for Reference and Datalinks wouldchange the I/O image in Figure 5.1 as follows:

Figure 5.2 illustrates an example of an I/O image that does not use all ofthe I/O data. Only the Logic Command/Reference and Datalink B areenabled. In this example, the Reference is a 32-bit word, and Datalinksare 16-bit words.

Figure 5.2 Example I/O Image with Only Logic/Reference and Datalink B Enabled

LSW = Least Significant Word (Bits 15 - 0)MSW = Most Significant Word (Bits 31 - 16)

Word I/O Word I/O0 Logic Command/Status 7 - 10 Datalink B1 - 2 Reference/Feedback 11 - 14 Datalink C3 - 6 Datalink A 15 - 18 Datalink D

Controller Scanner Adapter PowerFlexDrive

DeviceNet DPI

OutputImage(Write)

InputImage(Read)

MessageHandler

MessageBuffer

MessageHandler

0 Logic Status1 Feedback (LSW)2 Feedback (MSW)3 Datalink Out B14 Datalink Out B2

0 Logic Command1 Reference (LSW)2 Reference (MSW)3 Datalink In B14 Datalink In B2

Logic CommandReferenceData In A1Data In A2Data In B1Data In B2Data In C1Data In C2Data In D1Data In D2

Logic StatusFeedbackData Out A1Data Out A2Data Out B1Data Out B2Data Out C1Data Out C2Data Out D1Data Out D2

Word and I/O


When enabled, the Logic Command/Status word is always word 0 in theI/O image. The Logic Command is a 16-bit word of control produced bythe scanner and consumed by the adapter. The Logic Status is a 16-bitword of status produced by the adapter and consumed by the scanner.

This manual contains the bit definitions for compatible productsavailable at the time of publication in Appendix D, Logic Command/Status Words. For other products, refer to their documentation.

When enabled, Reference/Feedback always begins at word 1 in the I/Oimage. The Reference (16 bits or 32 bits) is produced by the controllerand consumed by the adapter. The Feedback (16 bits or 32 bits) isproduced by the adapter and consumed by the controller. The size of theReference/Feedback is determined by the drive and displayed inParameter 07 - [Ref/Fdbk Size] in the adapter.

A Datalink is a mechanism used by PowerFlex drives to transfer data toand from the controller. Datalinks allow a parameter value to be changedwithout using an Explicit Message. When enabled, each Datalinkoccupies two 16 or 32-bit words in both the input and output image.Parameter 08 - [Datalink Size] will indicate whether the drive uses 16or 32-bit words for Datalinks.

Rules for Using Datalinks• Each set of Datalink parameters in a PowerFlex drive can be used by

only one adapter. If more than one adapter is connected to a singledrive, multiple adapters must not try to use the same Datalink.

• Parameter settings in the drive determine the data passed through theDatalink mechanism. Refer to the documentation for your drive.

• When you use a Datalink to change a value, the value is not writtento the Non-Volatile Storage (NVS). The value is stored in volatilememory and lost when the drive loses power.

Using Logic Command/Status

Using Reference/Feedback

Size Valid Values In I/O Image Example16-bit -32768 to 32767 Word 1 Figure 5.132-bit -2147483648 to 2147483647 Word 1 and Word 2 Figure 5.2

Using Datalinks


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. Forexample, to read Parameter 09 - [Elapsed MWh], both Datalink A1and A2 are set to “9.” Datalink A1 will contain the least significant word(LSW) and Datalink A2 the most significant word (MSW). In thisexample, the parameter 9 value of 5.8MWh is read as a “58” in DatalinkA1.

Regardless of the Datalink combination, x1 will always contain the LSWand x2 will always contain the MSW. In the following examplesParameter 242 - [Power Up Marker] contains a value of 88.4541hours.

32-bit data is stored in binary as follows:

Example:Parameter 242 - [Power Up Marker] = 88.4541 hoursMSW = 13decimal = 1101binary = 216 + 218 + 219 = 851968LSW = 32573851968 + 32573 = 884541

Datalink Most/Least Significant Word Parameter Data (decimal)A1 LSW 9 58A2 MSW 9 0

Datalink Most/Least Significant Word Parameter Data (decimal)A1 LSW 242 32573A2 - Not Used - 0 0

Datalink Most/Least Significant Word Parameter Data (decimal)A1 - Not Used - 0 0A2 MSW 242 13

Datalink Most/Least Significant Word Parameter Data (decimal)A2 MSW 242 13B1 LSW 242 32573

MSW 231 through 216

LSW 215 through 20


These example ladder logic programs (Figure 5.4 – Figure 5.7) workwith PowerFlex 70 or PowerFlex 700 drives.

Functions of the Example Programs

The example programs use an operator station wired to an I/O module inSlot 0, Module Group 0, Rack 0. The operator can perform the followingactions:

• Obtain status information from the drive.• Use the Logic Command to control the drive (for example, start,

stop).• Send a Reference to the drive.

Adapter Settings for the Example Programs• Node address 1 is set using the switches.• Logic Command/Reference and Datalink A are enabled in

Parameter 13 - [DN I/O Config].• Master-Slave Hierarchy is set using Parameters 25 - [M-S Input]

and 26 - [M-S Output].• Polled I/O was enabled during the scanner configuration.

Scanner Settings for the Example Programs• The scanner is node 0 on the DeviceNet network.• The scanner is in slot 1.• The adapter I/O is mapped in word 0 and word 1.• Data files, when used, are pointed out in the examples.

Logic Command/Status Words

These examples use the Logic Command word and Logic Status wordfor PowerFlex 70 and PowerFlex 700 drives. Refer to Appendix D,Logic Command/Status Words to view these. The definition of the bits inthese words may vary if you are using a different DPI product. Refer tothe documentation for your drive.

Example Ladder Logic Programs


Figure 5.3 Tags for the Example Program

Figure 5.4 Example ControlLogix Ladder Logic Program

ControlLogix Example

Tag Name Type Tag Name TypeLocal:1:I DINT[] DriveFeedback INTLocal:1:O DINT[] DriveInputImage INT[2]DriveCommandClearFault BOOL DriveOutputImage INT[2]DriveCommandJog BOOL DriveReference INTDriveCommandStart BOOL DriveStatusFaulted BOOLDriveCommandStop BOOL DriveStatusRunning BOOL

0Local:1:O.CommandRegister.Run

1 Copy FileSource Local:1:I.Data[0]Dest DriveInputImage[0]Length 2

COP

2 DriveInputImage[0].1 DriveStatusRunning

3 DriveInputImage[0].7 DriveStatusFaulted

4 Copy FileSource DriveInputImage[1]Dest DriveFeedbackLength 1

COP

5DriveCommandStart DriveOutputImage[0].1

6DriveCommandStop DriveOutputImage[0].0

7DriveCommandJog DriveOutputImage[0].2

This rung enables the DeviceNet scanner.

This rung copies the 32-bit DeviceNet scanner input image intoan array of two 16-bit words. The length in this instruction is twobecause two 16-bit array elements of the destination are used.

These rungs read the Running and Faulted status bits from theinput image of the drive and place the data in respective tags.

This rung reads the drive’s Feedback word and places it inthe Feedback tag.

These rungs move the inputs of the operator from theoperator station to the drive’s output image.


Figure 5.4 Example ControlLogix Ladder Logic Program (Continued)

9 Copy FileSource DriveReferenceDest DriveOutputImage[1]Length 1

COP

10 Copy FileSource DriveOutputImage[0]Dest Local:1:O.Data[0]Length 1

COP

(End)

DriveCommandClearFault DriveOutputImage[0].38

This rung transfers the reference tag to the drive’soutput image.

This rung copies the output image into the 32-bitDeviceNet scanner output structure. The length in thisinstruction is one because only one 32-bit arrayelement of the destination is used.


Figure 5.5 Control File for Block Transfers

Figure 5.6 Example PLC-5 Ladder Logic Program

PLC-5 Example

EN ST DN ER CO EW NR TO RW RLEN DLEN FILE ELEM R G SBT20:0 0 0 0 0 0 0 0 0 0 62 0 9 0 00 0 0BT20:1 0 0 0 0 0 0 0 0 0 62 0 10 0 00 0 0

0000BT20:0

ENEN

DN

ER

BTRBlock Transfer ReadModule Type Generic Block TransferRack 000Group 0Module 0Control Block BT20:0Data File N9:0Length 62Continuous No

0001N9:1

1

PowerFlex 70RUNNINGStatus Bit

O:000

10

Operator DisplayDrive RunningStatus Bit

0002N9:1

7

PowerFlex 70FAULTEDStatus Bit

O:000

11

Operator DisplayDrive FaultedStatus Bit

0003MO

MoveSource N9:2

0<Dest N21:1

0<

MOV

Operator DisplayDrive FeedbackStatus Word

0004N10:0

0

1771-SDN ScannerPort A Enable

0005I:000

10

Operator InputDrive StartCommand Bit

N10:1

1

PowerFlex 70STARTCommand Bit

The scanner gathers drive status data via the DeviceNet network. The Block Transfer Readin this rung then moves the drive status data from the scanner to the N9 data file in the PLC.

These rungs move the drive status from the BlockTransfer Read data file to an operator display.

This rung enables the scanner.

These rungs move the inputs of the operator fromthe operator station to the Block Transfer Writedata file. They will then be sent to the scannerand out to the drive via the DeviceNet network.


Figure 5.6 Example PLC-5 Ladder Logic Program (Continued)

000712

N10:1

2

PowerFlex 70JOGCommand Bit

000813

N10:1

3

PowerFlex 70CLEAR FAULTCommand Bit

0009MOV

MoveSource N21:0

0<Dest N10:2

0<

PowerFlex 70REFERENCECommand Word

0010BT20:1

ENEN

DN

ER

BTW

0011 END

Operator InputDrive JogCommand Bit

Operator InputDrive Clear FaultsCommand Bit

I:000

I:000

Block Transfer WriteModule Type Generic Block TransferRack 000Group 0Module 0Control Block BT20:1Data File N10:0Length 62Continuous No

11

N10:1

0

PowerFlex 70STOPCommand Bit

Operator InputDrive StopCommand Bit

I:0000006

The Block Transfer Write in this rung sends the drivecommand data to the scanner and out to the drive viathe DeviceNet network.


Figure 5.7 Example SLC Ladder Logic Program

SLC Example

0000 Copy FileSource #M1:1:0Dest #N9:0Length 128

CO P

0001N9:0

1

PowerFlex 70RUNNINGStatus Bit

O:3.0

01746-O*8

Operator DisplayDrive RunningStatus Bit

00027 1

0003 MoveSource N9:1

0<Dest N21:1

0<

MOV

0004I:2.0

01746-I*16

Operator InputDrive StartCommand Bit

N10:0

1

PowerFlex 70STARTCommand Bit

0005I:2.0

1 0

00062 2

O:3.0

Operator DisplayDrive FaultedStatus Bit

1746-O*8

N9:0

PowerFlex 70FAULTEDStatus Bit

Operator DisplayDrive FeedbackStatus Word

Operator InputDrive StopCommand Bit

I:2.0

Operator InputDrive JogCommand Bit

1746-I*16

N10:0

PowerFlex 70STOPCommand Bit

N10:0

PowerFlex 70JOGCommand Bit

1746-I*16

These rungs move the inputs of theoperator from the operator station to theN9 data file. They will then be sent to thescanner and out to the drive via theDeviceNet network.

These rungs move the drive status fromthe N9 data file to an operator display.

The scanner gathers drive status data via the DeviceNetnetwork. The M-File is copied into the N9 data file in the SLCto move the drive status information to a convenient location.


Figure 5.7 Example SLC Ladder Logic Program (Continued)

0008MOV

MoveSource N21:0

0<Dest N10:1

0<

0009O:1.0

01747-SDN

1747-SDNScannerEnableBit

0010COP

Copy FileSource #N10:0Dest #M0:1.0Length 128

0011 END

PowerFlex 70REFERENCECommand Word

0007

3 3

I:2.0

Operator InputDrive Clear FaultsCommand Bit

1746-I*16

N10:0

PowerFlex 70CLEAR FAULTSCommand Bit

This rung enables the scanner. It changes the scanner to RUN mode.

This rung copies the drive command data to thescanner and out to the drive via the DeviceNet network.

Chapter 6

Using Explicit Messaging

Chapter 6 provides information and examples that explain how to useExplicit Messaging to monitor and configure the adapter and connectedPowerFlex drive.

Explicit Messaging is used to transfer data that does not requirecontinuous updates. With Explicit Messaging, you can configure andmonitor a slave device’s parameters on the DeviceNet network.

Topic Page Topic PageAbout Explicit Messaging 6-1 ControlLogix Example 6-8Formatting Explicit Messages 6-2 PLC-5 Example 6-10Running Explicit Messages 6-7 SLC Example 6-12


!ATTENTION: Hazard of equipment damage exists. If ExplicitMessages are programmed to write parameter data to Non-VolatileStorage (NVS) frequently, the NVS will quickly exceed its life cycleand cause the drive to malfunction. Do not create a program thatfrequently uses Explicit Messages to write parameter data to NVS.Datalinks do not write to NVS and should be used for frequentlychanged parameters.

About Explicit Messaging

6-2 Using Explicit Messaging

Explicit Messages for a ControlLogix Controller

ControlLogix scanners accommodate both downloading ExplicitMessage Requests and uploading Explicit Message Responses. Thescanner module can accommodate one request or response for eachtransaction block. Each transaction block must be formatted as shown inFigure 6.1.

Figure 6.1 ControlLogix Message Format in RSLogix 5000

Refer to Page 6-3 for a description of the data that is required in eachbox (1 – 9).

Formatting Explicit Messages

�

��

�

�

TIP: To display the Message Configuration dialog box in RSLogix5000, add a message instruction, create a tag for the message (properties:base tag, MESSAGE data type, controller scope), and click the blue boxinside the message.

Using Explicit Messaging 6-3

The following table identifies the number of Explicit Messages that canbe executed at a time.

ControlLogix Message Requests and Responses

Scanner Messages atOne Time

Refer To

1756-DNB 5 Figure 6.1

Box Description� Message Type

The message type must be CIP Generic.� Service Code

The service code is the requested DeviceNet service. Available servicesdepend on the class and instance that you are using. Refer to Appendix C,DeviceNet Objects.

� Object TypeThe object type is a DeviceNet class. Refer to Appendix C, DeviceNet Objects,for available classes.

� Object IDThe object ID is an instance of a DeviceNet class. Refer to Appendix C,DeviceNet Objects, for available instances.

� Object AttributeThe object attribute is a class or instance attribute. Refer to Appendix C,DeviceNet Objects, for available classes.

� SourceThis box contains the name of the tag for any service data to be sent from thescanner to the adapter and drive. A tag must be specified even if it is not used.

Num. of ElementsThis box contains the number of bytes of service data to be sent or received inthe message.

DestinationThis box contains the name of the tag that will receive service response datafrom the adapter and drive. A tag must be specified even if it is not used.

� PathThe path includes the following:• Name of the DeviceNet scanner.• Communication port on the front of the 1756-DNB scanner. Always 2.• Node address of the DeviceNet adapter. This is set with switches or

parameters in the DeviceNet adapter.Tip: Click Browse to find the path or type in the name of a module that youpreviously mapped.


Explicit Messages for a PLC or SLC Controller

Transaction blocks in PLC and SLC scanners accommodate bothdownloading Explicit Message Requests and uploading ExplicitMessage Responses. The scanner module can accommodate one requestor response for each transaction block. Each transaction block must beformatted as shown in Figure 6.2 or Figure 6.3.

Figure 6.2 PLC Explicit Message Format

Figure 6.3 SLC Explicit Message Format

Refer to Page 6-5 and Page 6-6 for a description of the data that isrequired in each word.

Bit 15 0 15 0Word 0 TXID Command TXID Status

Port Size Port Size

Service Address Service Address

Class Service Response Data

Instance

Attribute

Word 6 - 31 Service Data

Word 32 TXID Command TXID Status

Port Size Port Size



Instance

Attribute


Bit 15 0 15 0Word 0 TXID Command TXID Status

Port Size Port Size



Instance

Attribute


Request Response

Request Response


The following table identifies the number of transaction blocks within ascanner that are reserved for Explicit Messaging.

PLC / SLC Explicit Message Requests

Scanner Number ofTransaction Blocks

Words in EachTransaction Block

Refer To

1747-SDN 10 32 Figure 6.31771-SDN 10 32 (two blocks can

be moved at once)Figure 6.2

Word Description0 Command (Least Significant Byte)

The Command is a code that instructs the scanner how to administer therequest during each download.00 = Ignore transaction block (empty)01 = Execute this transaction block02 = Get status of transaction TXID03 = Reset all client/server transactions04 = Delete this transaction block (available only for SLC)05 – 255 = ReservedTXID (Most Significant Byte)The Transaction ID is a 1-byte integer between 1 and 255. It is assigned in theladder logic program when the processor creates and downloads a request tothe scanner. The scanner uses it to track the transaction to completion. Itreturns this value with the response that matches the request downloaded bythe processor.

1 Size (Least Significant Byte)The size of the service data is in bytes. Service data includes the words for theclass, instance, attribute, and any data. The maximum size is 58 bytes (29words).Port (Most Significant Byte)The port that is used by the message is always zero (Channel A) on an SLCscanner. It is zero (Channel A) or one (Channel B) for a PLC scanner.

2 Address (Least Significant Byte)The node address of the slave device to which the transaction is sent. For theExplicit Message to be successful, the slave device must be in the scanlist ofthe scanner, and it must be online.Service (Most Significant Byte)Available services depend on the class and instance that you are using.Refer to Appendix C, DeviceNet Objects.

3 ClassRefer to Appendix C, DeviceNet Objects, for available classes.

4 InstanceRefer to Appendix C, DeviceNet Objects, for available instances.

5 AttributeRefer to Appendix C, DeviceNet Objects, for available attributes.

6 – 31 Request DataThis is data used for the message. For example, it may be the value written to aparameter.


PLC / SLC Explicit Message Responses

Refer to Page 6-5 for a description of the words in a PLC/SLC ExplicitMessage request.

Word Description0 Status (Least Significant Byte)

One of the following status codes is provided during each upload:00 = Ignore transaction block (empty)01 = Transaction completed successfully02 = Transaction in progress (not ready)03 = Slave not in scan list04 = Slave offline05 = DeviceNet port disabled or offline06 = Transaction TXID unknown08 = Invalid command code09 = Scanner out of buffers10 = Other client/server transaction in progress11 = Could not connect to slave device12 = Response data too large for block13 = Invalid port14 = Invalid size specified15 = Connection busy16 – 255 = ReservedTXID (Most Significant Byte)The transaction ID is a 1-byte integer in word 31 with a range of 1 to 255. It isassigned in the ladder logic program when the processor creates anddownloads a request to the scanner. The scanner uses it to track thetransaction to completion. It returns this value with the response that matchesthe request downloaded by the processor.

1 Size (Least Significant Byte)The size of the service data is in bytes. The service data includes words usedfor the response data. The maximum size is 58 bytes (29 words).Port (Most Significant Byte)The port that is used by the message is always zero (Channel A) on an SLCscanner. It is zero (Channel A) or one (Channel B) for a PLC scanner.

2 Address (Least Significant Byte)The node address of the slave device to which the transaction is sent. For theExplicit Message to be successful, the slave device must be in the scanlist ofthe scanner, and it must be online.Service (Most Significant Byte)If the message was successful, 0x80 is added to the service. If it isunsuccessful, 0x94 is returned.

3 – 31 Response DataThis is data used for the message. For example, it may be the value read from aparameter.


There are five basic events in the Explicit Messaging process. The detailsof 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 messagefor all Explicit Messages, whether you are reading orwriting data.

Figure 6.4 Explicit Message Process

1. You format the required data and set up the ladder logic program tosend an Explicit Message request to the scanner module (download).

2. The scanner module transmits the Explicit Message Request to theslave device over the DeviceNet network.

3. The slave device transmits the Explicit Message Response back tothe scanner. The data is stored in the scanner buffer.

4. The controller retrieves the Explicit Message Response from thescanner’s buffer (upload).

5. The Explicit Message is complete. If you are using a PLC or SLC,delete the transaction ID so that it can be reused.

Running Explicit Messages

PWR

STS

PORT

MOD

NET A

NET B

�

�

�

�

�

Set up and send Explicit

Retrieve ExplicitMessage Response

Message Request

Complete ExplicitMessage


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 descriptionof the content in each box.

ControlLogix Example

Configuration Value Description Refer to . . .Service CodeObject TypeObject IDObject Attribute

e (hex)f (hex)101 (dec)1 (hex)

Get_Attribute_SingleParameter ObjectParameter AddressParameter Value

C-10C-8

C-9


Figure 6.5 Tags for the Example Explicit Messaging Program

Figure 6.6 Example ControlLogix Ladder Logic Program

Configuration Value Description Refer to . . .Service CodeObject TypeObject IDObject Attribute

10 (hex)f (hex)101 (dec)1 (hex)

Set_Attribute_SingleParameter ObjectParameter AddressParameter Value

C-10C-8

C-9

Tag Namesfor Read Message Type

Tag Namesfor Write Messages Type

StartParameterRead BOOL StartParameterWrite BOOLParameterReadDestination INT ParameterWriteDestination INTParameterReadMessage MESSAGE ParameterWriteMessage MESSAGEParameterReadSource INT ParameterWriteSource INT

0

StartParameterRead

ENDNER

Type - CIP GenericMessage Control ParameterReadMessage ...

MSG

1 StartParameterWrite

ENDNER

Type - CIP GenericMessage Control ParameterWriteMessage

MSG

(End)

...

This rung writes the value of parameter 101. The value is taken from the WriteSource tag.

This rung reads the value of parameter 101. The value is in the ReadDestination tag.




Refer to Formatting Explicit Messages in this chapter for a descriptionof the content of the data file.

Request Data for Read of Drive Parameter 101

Response Data for Read of Drive Parameter 101

Request Data for Write to Drive Parameter 101

Response Data for Write to Drive Parameter 101

PLC-5 Example

Address Value (hex) Description Refer to . . .N30:0 0101 TXID = 01, Command = 01 (execute) 6-5N30:1 0006 Port = 00, Size = 06 bytes 6-5N30:2 0E01 Service = 0E (Get_Attribute_Single) C-10

Address = 01 (Node Address) 6-5N30:3 000F Class = 0F (Parameter Object) C-8N30:4 0065 Instance = Parameter 101 (65 hex)N30:5 0001 Attribute = 01 (Parameter Value) C-9

Address Value (hex) Description Refer to . . .N30:70 0101 TXID = 01, Status = 01 (successful) 6-6N30:71 0002 Port = 00, Size = 02 bytes 6-6N30:72 8E01 Service = 8E (successful), Address = 01 (Node

Address)6-6

N30:73 03E8 Response Data = 1000 (3E8 hex) = 10.00seconds

Address Value (hex) Description Refer to . . .N30:0 0101 TXID = 01, Command = 01 (execute) 6-5N30:1 0008 Port = 00, Size = 08 bytes 6-5N30:2 1001 Service = 10 (Set_Attribute_Single) C-10

Address = 01 (Node Address) 6-5N30:3 000F Class = 0F (Parameter Object) C-8N30:4 0065 Instance = Parameter 101 (65 hex)N30:5 0001 Attribute = 01 (Parameter Value) C-9N30:6 07D0 Data = 2000 (7D0 hex) = 20.00 seconds

Address Value (hex) Description Refer to . . .N30:70 0101 TXID = 01, Status = 01 (successful transaction) 6-6N30:71 0000 Port = 00, Size = 00 bytes 6-6N30:72 9001 Service = 90 (successful)

Address = 01 (Node Address)6-6


Ladder Logic Program

Figure 6.7 Example PLC-5 Ladder Logic Program

0000I:000

17ONSB3:0

0EN

DN

ER

BTWBlock Transfer WriteModule Type 1771-SDN DeviceNet Scanner ModuleRack 000Group 0Module 0Control Block BT20:2Data File N30:0Length 64Continuous No

MOVMoveSource 0

0<Dest N30:70

257<

0001BT20:2

DN

CMPComparisonExpression N30:70 <> N30:0

BT20:3

EN

EN

DN

ER

BTR

00000

BT20:3N30:70

64No

0002 END

Block Transfer ReadModule Type 1771-SDN DeviceNet Scanner ModuleRackGroupModuleControl BlockData FileLengthContinuous

When I:000/17 is set to true, a one-time Block Transfer Write sends data to the scanner. The Moveinstruction then initializes the first word of the data file that is used by the Block Transfer Read instruction inthe next rung.

When BT20:2.DN is true, the Block Transfer Write is complete. Thecompare instruction compares the first word of data sent from thescanner to the first word of data you send to the scanner. When themessaging function is complete, the two words are equal.If the Block Transfer Read is not enabled, this instruction enables itwhen BT20:2.DN and the compare are true. The Block TransferRead reads 64 words of data.




Refer to Formatting Explicit Messages in this chapter for a descriptionof the content of the data file.

Request Data for Read of Drive Parameter 101

Response Data for Read of Drive Parameter 101

Request Data for Write to Drive Parameter 101

Response Data for Write to Drive Parameter 101

SLC Example

Address Value (hex) Description Refer to . . .N20:10 0101 TXID = 01, Command = 01 (execute) 6-5N20:11 0006 Port = 00, Size = 06 bytes 6-5N20:12 0E01 Service = 0E (Get_Attribute_Single) C-10

Address = 01 (Node Address) 6-5N20:13 000F Class = 0F (Parameter Object) C-8N20:14 0065 Instance = Parameter 101 (65 hex)N20:15 0001 Attribute = 01 (Parameter Value) C-9

Address Value (hex) Description Refer to . . .N20:50 0101 TXID = 01, Status = 01 (successful) 6-6N20:51 0002 Port = 00, Size = 02 bytes 6-6N20:52 8E01 Service = 8E (successful)


N20:53 03E8 Response Data = 1000 (3E8 hex) = 10.00seconds

Address Value (hex) Description Refer to . . .N20:10 0101 TXID = 01, Command = 01 (execute) 6-5N20:11 0008 Port = 00, Size = 08 bytes 6-5N20:12 1001 Service = 10 (Set_Attribute_Single) C-10

Address = 01 (Node Address) 6-5N20:13 000F Class = 0F (Parameter Object) C-8N20:14 0065 Instance = Parameter 101 (65 hex)N20:15 0001 Attribute = 01 (Parameter Value) C-9N20:16 07D0 Data = 2000 (7D0 hex) = 20.00 seconds

Address Value (hex) Description Refer to . . .N20:50 0101 TXID = 01, Status = 01 (successful transaction) 6-6N20:51 0000 Port = 00, Size = 00 bytes 6-6N20:52 9001 Service = 90 (successful)



Program

Important: To originate a scanner transaction, use a copy operation toM0:[slot number]:224. Then, use a copy operation to readM1:1.224 for the result. If more than one message isenabled, use the TXID to determine which message you arereading.

Figure 6.8 Example SLC Ladder Logic Program

0000B3:0

0

COP

#N20:10#M0:1:224

32

UB3 :0

0

InitiateExplicitMessage

0001I:1.0

151747-SDN

ExplicitMessageResponseAvailable

COPCopy FileSource #M1:1:224Dest #N20:50Length 32

ExplicitMessageResponse

EQUEqualSource A N20:10

257 <Source B N20:50

257 <

MVMMask MoveSource N20:0

4<Mask 00FFh

255 <Dest M0:1.224

?<

ExplicitMessage

0002 END

InitiateExplicitMessage

ExplicitMessage

Copy FileSourceDestLength

When B3:0/0 is set to true, this rung willcopy the 32 words of Explicit Message fromthe buffer at N20:10 to M0-File ExplicitMessage buffer. The scanner will send themessage out over DeviceNet.

When I:1.0/15 is set to true and the ExplicitMessage Response has been received in theM1-File, this rung performs the following:- Copies the response message into N10:50.- Copies a command of four (4) into the

M1-File.The four (4) commands the 1747-SDNscanner to discard the response data so that thebuffer can be used for the next messageresponse.


Notes:

Chapter 7

Troubleshooting

Chapter 7 contains troubleshooting information.

The DeviceNet adapter has three status indicators. They can be viewedon the adapter or through the drive cover. See Figure 7.1.

Figure 7.1 Status Indicators (location on drive may vary)

Topic Page Topic PageLocating the Status Indicators 7-1 NET A Status Indicator 7-3PORT Status Indicator 7-2 Module Diagnostic Items 7-4MOD Status Indicator 7-2 Viewing and Clearing Events 7-5

Locating the Status Indicators

Number Status Indicator Description Page� PORT DPI Connection Status 7-2� MOD Adapter Status 7-2� NET A DeviceNet Status 7-3� NET B Not Used for DeviceNet

PWR

STS

PORT

MOD

NET A

NET B

�

�

�

��

�

7-2 Troubleshooting

PORT Status Indicator

Status Cause Corrective ActionOff The adapter is not powered or

is not connected properly tothe drive.

• Securely connect the adapter to the driveusing the ribbon cable.

• Apply power to the drive.FlashingRed

The adapter is not receiving aping message from the drive.

• Verify that cables are securely connected.• Cycle power to the drive.

SolidRed

The drive has refused anI/O connection from theadapter.

Another DPI peripheral isusing the same DPI port asthe adapter.

Important: Cycle power to the product aftermaking any of the following corrections.• Verify that all DPI cables on the

PowerFlex drive are securely connectedand not damaged. Replace cables ifnecessary.

• Verify that the PowerFlex drive supportsDatalinks.

• Configure the adapter and PowerFlexdrive to use a Datalink that is not alreadybeing used by another peripheral.

Orange The adapter is connected to aproduct that does not supportAllen-Bradley DPIcommunications.

• Connect the adapter to a product thatsupports Allen-Bradley DPIcommunications (for example, PowerFlexdrives).

FlashingGreen

The adapter is establishing anI/O connection to the drive.

• No Action. This status indicator will turnsolid green or red.

SolidGreen

The adapter is properlyconnected and iscommunicating with the drive.

• No Action.

MOD Status Indicator

Status Cause Corrective ActionOff The adapter is not

powered.• Securely connect the adapter to the drive

using the ribbon cable.• Apply power to the drive.

FlashingRed

The adapter has failed thefirmware test or the nodeaddress switch setting isinvalid.

• Verify that the node address switch setting isbetween 0 and 63.

• Clear faults in the adapter.• Cycle power to the drive.• If cycling power does not correct the

problem, the parameter settings may havebeen corrupted. Reset defaults andreconfigure the module.

• If resetting defaults does not correct theproblem, flash the adapter with the latestfirmware release.

SolidRed

The adapter has failed thehardware test.

• Cycle power to the drive.• Replace the adapter.

FlashingGreen

The adapter is operational,but is not transferring I/Odata.

• Place the scanner in RUN mode.• Program the controller to recognize and

transmit I/O to the adapter.• Configure the adapter for the program in the

controller.SolidGreen

The adapter is operationaland transferring I/O data.

• No Action.

Troubleshooting 7-3

NET A Status Indicator

Status Cause Corrective ActionsOff The adapter and/or

network is not powered oradapter is not connectedproperly to the network.

• Securely connect the adapter to the driveusing the Internal Interface cable and to thenetwork using a DeviceNet cable.

• Correctly connect the DeviceNet cable to theDeviceNet plug.

• Apply power to the drive and network.FlashingRed/Green

The adapter has receivedan Identify Comm Faultrequest.

• Wait for the faulted node recovery tocomplete.

FlashingRed

A DeviceNet I/Oconnection has timed out.

• Place the scanner in RUN mode, or applypower to the peer device that will send I/O.

• Check the amount of traffic on the network.SolidRed

Failed duplicate nodedetection test or bus off.

• Configure the adapter to use a unique nodeaddress on the DeviceNet network.

• Configure the adapter to use the correctnetwork data rate.

• Ensure network has correct media installed.FlashingGreen

The adapter is properlyconnected but is notcommunicating with anydevices on the network.

• Place the controller in RUN mode, or applypower to the peer device that will send I/O.

• Program a controller or peer device torecognize and transmit I/O to the adapter.

• Configure the adapter for the program in thecontroller or the I/O from the peer device.

SolidGreen

The adapter is properlyconnected andcommunicating on thenetwork.

• No action required.

7-4 Troubleshooting

The following diagnostic items can be accessed using DriveExplorer(version 2.01 or higher).

Module Diagnostic Items

No. Name Description1 Common Logic

CmdCurrent value of the Common Logic Command being transmitted to the hostby this peripheral.

2 Prod Logic Cmd Current value of the Product Specific Logic Command being transmitted tothe host by this peripheral.

3 Reference Current value of the Product Specific Reference being transmitted to the hostby this peripheral.

4 Common LogicSts

Current value of the Common Logic Status being received from the host bythis peripheral.

5 Prod Logic Sts Current value of the Product Specific Logic Status being received from thehost by this peripheral.

6 Feedback Current value of the Product Specific Feedback being received from the hostby this peripheral.

7 Datalink A1 In Current value of Datalink A1 In being transmitted to the host by this peripheral(if not using Datalink A1, this parameter should have a value of zero).

8 Datalink A2 In Current value of Datalink A2 In being transmitted to the host by this peripheral(if not using Datalink A2, this parameter should have a value of zero).

9 Datalink B1 In Current value of Datalink B1 In being transmitted to the host by this peripheral(if not using Datalink B1, this parameter should have a value of zero).

10 Datalink B2 In Current value of Datalink B2 In being transmitted to the host by this peripheral(if not using Datalink B2, this parameter should have a value of zero).

11 Datalink C1 In Current value of Datalink C1 In being transmitted to the host by this peripheral(if not using Datalink C1, this parameter should have a value of zero).

12 Datalink C2 In Current value of Datalink C2 In being transmitted to the host by this peripheral(if not using Datalink C2, this parameter should have a value of zero).

13 Datalink D1 In Current value of Datalink D1 In being transmitted to the host by this peripheral(if not using Datalink D1, this parameter should have a value of zero).

14 Datalink D2 In Current value of Datalink D2 In being transmitted to the host by this peripheral(if not using Datalink D2, this parameter should have a value of zero).

15 Datalink A1 Out Current value of Datalink A1 being received from the host by this peripheral.16 Datalink A2 Out Current value of Datalink A2 being received from the host by this peripheral.17 Datalink B1 Out Current value of Datalink B1 being received from the host by this peripheral.18 Datalink B2 Out Current value of Datalink B2 being received from the host by this peripheral.19 Datalink C1 Out Current value of Datalink C1 being received from the host by this peripheral.20 Datalink C2 Out Current value of Datalink C2 being received from the host by this peripheral.21 Datalink D1 Out Current value of Datalink D1 being received from the host by this peripheral.22 Datalink D2 Out Current value of Datalink D2 being received from the host by this peripheral.23 Field Flash Cntr Current value of the Field Flash Counter.24 DPI Rx Errors Current value of the DPI CAN Transmit Error Counter register.25 DPI Tx Errors Maximum value of the DPI CAN Transmit Error Counter register.26 DNet Rx Errors Current value of the DNet CAN Receive Error Counter register.27 DNet Tx Errors Maximum value of the DNet CAN Receive Error Counter register.

Troubleshooting 7-5

The adapter maintains an event queue that reports the history of itsactions. You can view the event queue using an LCD PowerFlex HIM,DriveExplorer (2.01) software, or DriveTools 2000 (1.xx) software.

To view and clear events

Viewing and Clearing Events

Step Keys Example ScreenViewing Events1. Access parameters in the adapter.

Refer to Using the PowerFlex HIM inChapter 3.

2. Press the Up Arrow or Down Arrow toscroll to Diagnostics.

3. Press Enter to display theDiagnostics menu in the adapter.

4. Repeat steps 2 and 3 to enter theEvents option and then View EventQueue option.

5. Press the Up Arrow or Down Arrow toscroll through the events. The mostrecent event is Event 1.

Clearing Events1. Access parameters in the Adapter.

Refer to Using the PowerFlex HIM inChapter 3.

2. Press the Up Arrow or Down Arrow toscroll to Diagnostics.

3. Press Enter to display theDiagnostics menu in the adapter.

4. Repeat steps 2 and 3 to enter theEvents option and then the ClrEvent option or Clear Event Queueoption. A message will pop up toconfirm that you want to clear themessage or queue.

5. Press Enter to clear all events out ofthe event queue. All event queueentries will then display “No Event.”

OR

OR

OR


Event Q: 1 E3Ping Time Flt

Dgn: EventsView Event QueueClear EventClear Event Queue

7-6 Troubleshooting

Events

Many events in the Event queue occur under normal operation. If youencounter unexpected communications problems, the events may helpyou or Allen-Bradley personnel troubleshoot the problem. The followingevents may appear in the event queue:

Code Event Description0 No Event Empty event queue entry.1 DPI Bus Off Flt A bus-off condition was detected on DPI. This event may be

caused by loose or broken cables or by noise.2 Ping Time Flt A ping message was not received on DPI within the specified

time.3 Port ID Flt The adapter is not connected to a correct port on a DPI

product.4 Port Change

FltThe DPI port changed.

5 Host SentReset

The DPI product issued this because it was reset.

6 EEPROM SumFlt

The EEPROM in the adapter is corrupt.

7 Online @125kbps

The adapter and DPI product are communicating at 125kbps.

8 Online @500kBps

The adapter and DPI product are communicating at 500kbps.

9 Bad Host Flt The adapter was connected to an incompatible product.10 Dup. Port Flt Another peripheral with the same port number is already in

use.11 Type 0 Login The adapter has logged in for type 0 control.12 Type 0 Time

FltThe adapter has not received a type 0 status message withinthe specified time.

13 DL Login The adapter has logged into a Datalink.14 DL Reject Flt The host rejected an attempt to log in to a Datalink because the

Datalink is not supported or is used by another peripheral.15 DL Time Flt The adapter has not received a Datalink message within the

specified time.16 Control

DisabledThe adapter has sent a “Soft Control Disable” command to theDPI product.

17 ControlEnabled

The adapter has sent a “Soft Control Enable” command to theDPI product.

18 PCCC IO TimeFlt

The adapter has not received a PCCC control message withinthe specified time-out interval.

19 NormalStartup

The adapter successfully started up.

20 MessageTimeout

A Client-Server message sent by the peripheral was notcompleted.

21 DPI Fault Msg The DPI Host has faulted.22 DN Poll

TimeoutA Polled I/O connection has timed out.

23 DN I/O TooLong

Reconfigure the I/O length in the scanner.

Troubleshooting 7-7

24 Bad I/OFragment

A DeviceNet I/O fragment was received out of sequence.Possible line noise problem.

25 Idle I/OMessage

The DeviceNet scanner was placed in program mode.

26 Peer I/OTimeout

The adapter has not received Peer I/O from another device onthe network within the specified time-out interval.

27 DPI FaultClear

The DPI product issued this because a fault was cleared.

28 DN COSTimeout

A Change of State (COS) connection has timed out.

29 DN PollAllocate

A Polled connection has been allocated.

30 DN COSAllocate

A Change of State (COS) I/O connection has been allocated.

31 DN PollClosed

A Polled I/O connection was explicitly closed.

32 DN COSClosed

A Change of State (COS) connection was explicitly closed.

33 Safe StateError

At least one of the Fault Configuration parameters contains avalue greater than 65535 and the DPI product expects a 16-bitvalue.

34 LanguageCRC Bad

The language text memory segment is corrupt.

Code Event Description

7-8 Troubleshooting

Notes:

Appendix A

Specifications

This chapter present the specifications for the adapter.

Topic Page Topic PageCommunications A-1 Environmental A-2Electrical A-1 Regulatory Compliance A-2Mechanical A-1

Communications

NetworkProtocolData Rates

DeviceNet125K, 250K, 500K, Autobaud, PGMThe PGM (Program) setting on the switch is used to setthe data rate using the adapter parameter. Autobaud canbe set only if another device on the network is setting adata rate.

DriveProtocolData Rates

DPI125K or 500K

Electrical

ConsumptionDriveNetwork

150 mA at 5 V supplied through the drive60 mA at 24 V supplied through DeviceNetUse the 60 mA value to size the network current drawfrom the power supply.

Mechanical

DimensionsHeightLengthWidth

19 mm (0.75 inches)86 mm (3.39 inches)78.5 mm (3.09 inches)

Weight 85g (3 oz.)

A-2 Specifications

Environmental

TemperatureOperatingStorage

-10 to 50°C (14 to 149°F)-40 to +85°C (-40 to 185°F)

Relative Humidity -5 to 95% non-condensing

Regulatory Compliance

UL 508C and CULCE EN61800-3

Appendix B

Adapter Parameters

Appendix B provides information about the DeviceNet adapterparameters.

The parameters in the adapter are numbered consecutively. However,depending on which configuration tool you use, they may have differentnumbers.

Topic PageAbout Parameter Numbers B-1Parameter List B-1

About Parameter Numbers

Configuration Tool Numbering Scheme• DriveExplorer• DriveTools 2000• HIM

The adapter parameters begin with parameter 1. Forexample, Parameter 01 - [DPI Port] is parameter 1 asindicated by this manual.

• Explicit Messaging• RSNetWorx for

DeviceNet

The adapter parameters are appended to the list of driveparameters. For example, with a drive with 300parameters, Parameter 01- [DPI Port] is parameter 301.

Parameter List

ParameterNo. Name and Description Details01 [DPI Port]

Port to which the adapter is connected. This willusually be port 5.

Default: 0Minimum: 0Maximum: 7Type: Read Only

02 [DPI Data Rate]Data rate used by the drive. This data rate is set inthe drive, and the adapter detects it.

Default: 0 = 125 kbpsValues: 0 = 125 kbps

1 = 500 kbpsType: Read Only

03 [DN Addr Cfg]Node address if the Data Rate switch is set to“PGM” (Program).

Default: 63Minimum: 0Maximum: 63Type: Read/WriteReset Required: Yes

B-2 Adapter Parameters

04 [DN Addr Actual]DeviceNet node address actually used by theadapter.

Default: 63Minimum: 0Maximum: 63Type: Read Only

05 [DN Rate Cfg]DeviceNet data rate if the data rate switch is set to“PGM” (Program).

Default: 3 = AutobaudValues: 0 = 125 kbps

1 = 250 kbps2 = 500 kbps3 = Autobaud

Type: Read/WriteReset Required: Yes

06 [DN Rate Actual]DeviceNet data rate actually used by the adapter.

Default: 0 = 125 kbpsValues: 0 = 125 kbps

1 = 250 kbps2 = 500 kbps

Type: Read Only07 [Ref/Fdbk Size]

Size of the Reference/Feedback. The drivedetermines the size of the Reference/Feedback.

Default: 0 = 16-bitValue: 0 = 16-bit

1 = 32-bitType: Read Only

08 [Datalink Size]Size of each Datalink word. The drive determinesthe size of Datalinks.

Default: 0 = 16-bitValues: 0 = 16-bit

1 = 32-bitType: Read Only

09 [Reset Module]No action if set to “Ready.” Resets the adapter ifset to “Reset Module.” Restores the adapter to itsfactory default settings if set to “Set Defaults.” Thisparameter is a command. It will be reset to “0 =Ready” after the command has been performed.

Default: 0 = ReadyValues 0 = Ready

1 = Reset Module2 = Set Defaults

Type: Read/WriteReset Required: No

10 [Comm Flt Action]Action that the adapter and drive take if theadapter detects that DeviceNet communicationshave been disrupted. This setting is effective onlyif I/O that controls the drive is transmitted throughthe adapter.

Default: 0 = FaultValues: 0 = Fault

1 = Stop2 = Zero Data3 = Hold Last4 = Send Flt Cfg


ParameterNo. Name and Description Details

!ATTENTION: Risk of injury or equipment damage exists. If the adapter istransmitting I/O that controls the drive, the drive may fault when you reset theadapter. Determine how your drive will respond before resetting a connectedadapter.

!ATTENTION: Risk of injury or equipment damage exists. Parameter 10 - [CommFlt Action] lets you determine the action of the adapter and connected drive ifcommunications are disrupted. By default, this parameter faults the drive. You canset this parameter so that the drive continues to run. Precautions should be takento ensure that the setting of this parameter does not create a hazard of injury orequipment damage.

Adapter Parameters B-3

11 [Idle Flt Action]Sets the action that the adapter and drive take ifthe adapter detects that scanner is idle becausethe controller was switched to program mode. Thissetting is effective only if I/O that controls the driveis transmitted through the adapter.


1 = Stop2 = Zero Data3 = Hold Last4 = Send Flt Cfg


12 [DN Active Cfg]Source from which the adapter node address anddata rate are taken. This will either be switches orparameters in EEPROM. It is determined by thesettings of the switches on the adapter.

Default: 1 = SwitchesValues: 0 = EEPROM

1 = SwitchesType: Read Only

13 [DPI I/O Config]I/O that is transferred through the adapter.

Default: xxx0 0001Bit Values: 0 = I/O disabled

1 = I/O enabledType: Read/WriteReset Required: YesBit Definitions0 = Cmd/Ref1 = Datalink A2 = Datalink B3 = Datalink C4 = Datalink D5 = Not Used6 = Not Used7 = Not Used

14 [DPI I/O Active]I/O that the adapter is actively transmitting. Thevalue of this parameter will usually be equal to thevalue of Parameter 13 - DPI I/O Config.


1 = I/O enabledType: Read OnlyBit Definitions0 = Cmd/Ref1 = Datalink A2 = Datalink B3 = Datalink C4 = Datalink D5 = Not Used6 = Not Used7 = Not Used


!ATTENTION: Risk of injury or equipment damage exists. Parameter 11 - [Idle FltAction] lets you determine the action of the adapter and connected drive if thescanner is idle. By default, this parameter faults the drive. You can set thisparameter so that the drive continues to run. Precautions should be taken toensure that the setting of this parameter does not create a hazard of injury orequipment damage.


0123457 6


0123457 6


15 [Flt Cfg Logic]Sets the Logic Command data that is sent to thedrive if any of the following is true:• Parameter 10 - [Comm Flt Action] is set to

Send Flt Cfg and communications aredisrupted.

• Parameter 11 - [Idle Flt Action] is set to SendFlt Cfg and the scanner is put into Program orTest mode.

• Parameter 34 - [Peer Flt Action] is set to FaultCfg and communications are disrupted.

The bit definitions will depend on the product towhich the adapter is connected.

Default: 0000 0000 0000 0000Minimum: 0000 0000 0000 0000Maximum: 1111 1111 1111 1111Type: Read/WriteReset Required: No

16 [Flt Cfg Ref]Sets the Reference data that is sent to the drive ifany of the following is true:• Parameter 10 - [Comm Flt Action] is set to

Send Flt Cfg and communications aredisrupted.

• Parameter 11 - [Idle Flt Action] is set to SendFlt Cfg and the scanner is put into Programmode.

• Parameter 34 - [Peer Flt Action] is set to SendFlt Cfg and communications are disrupted.

Default: 0Minimum: 0Maximum: 4294967295Type: Read/WriteReset Required: No

Important: If the drive uses a 16-bitReference, the most significant word of thisvalue must be set to zero (0) or a fault willoccur.

1718192021222324

[Flt Cfg A1][Flt Cfg A2][Flt Cfg B1][Flt Cfg B2][Flt Cfg C1][Flt Cfg C2][Flt Cfg D1][Flt Cfg D2]Sets the data that is sent to the Datalink in thedrive if any of the following is true:• Parameter 11 - [Idle Flt Action] is set to Send

Flt Cfg and the scanner is put into Programmode.

• Parameter 10 - [Comm Flt Action] is set toSend Flt Cfg and communications aredisrupted.

• Parameter 34 - [Peer Flt Action] is set to SendFlt Cfg and communications are disrupted.

Default: 0Default: 0Default: 0Default: 0Default: 0Default: 0Default: 0Default: 0Minimum: 0Maximum: 4294967295Type: Read/WriteReset Required: No

Important: If the drive uses 16-bitDatalinks, the most significant word of thisvalue must be set to zero (0) or a fault willoccur.

25 [M-S Input]Master-Slave input data. This data is produced bythe scanner and consumed by the adapter.


1 = I/O enabledType: Read/WriteReset Required: YesBit Definitions0 = Cmd/Ref1 = DL A Input2 = DL B Input3 = DL C Input4 = DL D Input5 = Not Used6 = Not Used7 = Not Used



0123457 6


26 [M-S Output]Master-Slave output data. This data is producedby the adapter and consumed by the scanner.


1 = I/O enabledType: Read/WriteReset Required: YesBit Definitions0 = Status/Fdbk1 = DL A Output2 = DL B Output3 = DL C Output4 = DL D Output5 = Not Used6 = Not Used7 = Not Used

27 [COS Status Mask]Mask of the 16-bit Logic Status word. Unless theyare masked out, the bits in the Logic Status wordare checked for changes when the adapter isallocated using COS (Change of State). If a bitchanges, it is reported as a change in the Changeof State operation.If the mask bit is 0 (Off), the bit is ignored. If themask bit is 1 (On), the bit is checked.

Important: The bit definitions in the Logic Statusword depend on the drive.

Default: 0000 0000 0000 0000Values: 0 = Off

1 = OnType: Read/WriteReset Required: No

28 [COS Fdbk Change]Hysteresis band to determine how much theFeedback word can change before it is reportedas a change in the COS (Change of State)operation.


29 [COS/Cyc Interval]Amount of time that a scanner will wait to check fordata in the adapter. When COS (Change of State)data exchange has been set up, this is themaximum amount of time between scans. Scanswill happen sooner if data changes. When Cyclicdata exchange has been set up, this interval is thefixed time between scans. This interval isconfigured in the scanner.

Default: 0 SecondsMinimum: 0 SecondsMaximum: 655.35 SecondsType: Read Only

3031

[Peer A Input][Peer B Input]Destination in the drive of the Peer Input. Theadapter receives this data from the network andsends it to the drive.

Important: These parameters can be changedonly when the Parameter 37 - [Peer Inp Enable] isOff.

Important: If a 32-bit Datalink or Reference isused in Parameter 30 - [Peer A Input], Parameter31 - [Peer B Input] cannot be used.

Default: 0 = OffDefault: 0 = OffValues: 0 = Off

1 = Cmd/Ref2 = DL A Input3 = DL B Input4 = DL C Input5 = DL D Input




0123457 6


32 [Peer Cmd Mask]Mask that is used for the Logic Command wordwhen it is received through peer input. If the maskbit is 0 (Off), the command bit is ignored and notused. If the mask bit is 1 (On), the command bit ischecked and used.

Important: If the adapter receives a LogicCommand from both a Master device and a Peerdevice, each command bit must have only onesource. The source of command bits set to “0” willbe the Master device. The source of command bitsset to “1” will be the Peer device.

Default: 0000 0000 0000 0000Minimum: 0 = Ignore bit

1 = Use bitType: Read/WriteReset Required: No

33 [Peer Ref Adjust]Scale of the Reference received from a peer.

Important: Changes to this parameter take effectimmediately. A drive receiving its Reference frompeer I/O will receive the newly scaled Reference,resulting in a change of speed.

Default: 0.00Minimum: 0.00%Maximum: 199.99%Type: Read/WriteReset Required: No

34 [Peer Flt Action]Action that the adapter and drive take if theadapter detects that DeviceNet communicationswith a peer have been disrupted. This setting iseffective only if I/O is transmitted through theadapter.


1 = Stop2 = Zero Data3 = Hold Last4 = Fault Cfg


35 [Peer Node to Inp]Node address of the node producing the peer I/O.

Important: This parameter can be changed onlywhen the Parameter 37 - [Peer Inp Enable] is Off.


36 [Peer Inp Timeout]Time-out for a Change of State peer-to-peerconnection. If the time is reached without theadapter receiving a message, the adapter willrespond with the action specified in Parameter 34- [Peer Flt Action].On the Slave drive, this parameter should be set tothe value calculated from the following formula:Master Parameter 42 - [Peer Out Time] x MasterParameter 43 - [Peer Out Skip].

Default: 10.00 SecondsMinimum: 0.01 SecondsMaximum: 180.00 SecondsType: Read/WriteReset Required: No

37 [Peer Inp Enable]Determines if peer input is on or off.

Default: 0 = OffValues: 0 = Off



!ATTENTION: Risk of injury or equipment damage exists. Parameter 34 - [PeerFlt Action] lets you determine the action of the adapter and connected drive if theadapter is unable to communicate with the designated peer. By default, thisparameter faults the drive. You can set this parameter so that the drive continuesto run. Precautions should be taken to ensure that the setting of this parameterdoes not create a hazard of injury or equipment damage.


38 [Peer Inp Status]Status of the consumed peer input connection.


1 = Waiting2 = Running3 = Faulted

Type: Read Only3940

[Peer A Output][Peer B Output]Source of Peer output data.The adapter transmitsthis data to the network.

Important: These parameters can be changedonly when the Parameter 41 - [Peer Out Enable] isOff.

Important: If a 32-bit Datalink or Reference isused in Parameter 39 - [Peer A Output],Parameter 40 - [Peer B Output] cannot be used.

Default: 0 = OffDefault: 0 = OffValues: 0 = Off

1 = Cmd/Ref2 = DL A Input3 = DL B Input4 = DL C Input5 = DL D Input6 = DL A Output7 = DL B Output8 = DL C Output9 = DL D Output


41 [Peer Out Enable]Determines if peer output is on or off.



42 [Peer Out Time]Minimum time that an adapter will wait whentransmitting data to a peer.

Default: 10.00 SecondsMinimum: 0.01 SecondsMaximum: 10.00 SecondsType: Read/WriteReset Required: No

43 [Peer Out Skip]Maximum time that an adapter will wait whentransmitting data to a peer. The value ofParameter 42 - [Min Peer Tx Time] is multiplied bythe value of this parameter to set the time.




Notes:

Appendix C

DeviceNet Objects

Appendix C presents information about the DeviceNet objects that can

be accessed using Explicit Messages. For information on the format ofExplicit Messages and example ladder logic programs, refer toChapter 6, Using Explicit Messaging.

Object Class Code PageHex. Dec.

Identity Object 0x01 1 C-2Connection Object 0x05 5 C-4Register Object 0x07 7 C-6Parameter Object 0x0F 15 C-8Parameter Group Object 0x10 16 C-11PCCC Object 0x67 103 C-13DPI Device Object 0x92 146 C-15DPI Parameter Object 0x93 147 C-18DPI Fault Object 0x97 151 C-26DPI Alarm Object 0x98 152 C-28DPI Time Object 0x9B 155 C-30

TIP: Refer to the DeviceNet specification for more information aboutDeviceNet objects. Information about the DeviceNet specification isavailable on the ODVA web site (http://www.odva.org).

C-2 DeviceNet Objects

Class Code

Instances

The number of instances depends on the number of components in thedevice connected to the adapter. This number of components can be readin Instance 0, Attribute 2.

Class Attributes

Instance Attributes

Identity Object

Hexadecimal Decimal0x01 1

Instance Description0 Class1 Entire device (host and adapter)2 … (n - 1) Host componentsn DeviceNet adapter

AttributeID

AccessRule

Name Data Type Description

2 Get Max Instance UINT Total number of instances

AttributeID

AccessRule


1 Get Vendor ID UINT 1 = Allen-Bradley2 Get Device Type UINT 1213 Get Product Code UINT Number identifying product name

and rating4 Get Revision:

MajorMinor

STRUCT ofUSINTUSINT

Value variesValue varies

5 Get Status WORD Bit 0 = OwnedBit 2 = ConfiguredBit 10 = Recoverable faultBit 11 = Unrecoverable fault

6 Get Serial Number UDINT Unique 32-bit number7 Get Product Name SHORT_

STRING Product name and rating

DeviceNet Objects C-3

Services

Identity Object (Continued)

Service Code Implemented for: Service NameClass Instance

0x05 Yes No Reset0x0E Yes Yes Get_Attribute_Single0x11 Yes N/A Find_Next_Obj_Instance


Class Code

Instances

Instance Attributes

Refer to the DeviceNet Specification for more information.

Connection Object


Instance Description1 Master-Slave Explicit Message Connection2 Polled I/O Connection4 Change of State/Cyclic Connection6 – 10 Explicit Message Connection

AttributeID

AccessRule

Name DataType

Description

1 Get State USINT 0 = Nonexistent1 = Configuring2 = Waiting for connection ID3 = Established4 = Timed out

2 Get Instance Type USINT 0 = Explicit Message1 = I/O Message

3 Get TransportClass Trigger

USINT The Transport Class Trigger for this instance

4 Get ProducedCnxn ID

USINT CAN Identifier to transmit on

5 Get ConsumedCnxn ID

USINT CAN Identifier to receive on

6 Get Initial CommChar

USINT Defines the DeviceNet message groups thatthe tx/rx Cnxn’s apply

7 Get ProducedCnxn Size

UINT Max bytes to transmit across this connection

8 Get ConsumedCnxn Size

UINT Max bytes to receive across this connection

9 Get/Set EPR UINT Expected Packet Rate(timer resolution = 2 msec.)


Instance Attributes (Continued)

Refer to the DeviceNet Specification for more information.

Services

Connection Object (Continued)

AttributeID

AccessRule

Name DataType

Description

12 Get/Set WatchdogAction

USINT 0 = Transition to timed out1 = Auto delete2 = Auto reset

13 Get Produced PathLength

UINT Number of bytes of data in the producedconnection path

14 Get ProducedConnectionPath

ARRAYofUINT

Byte stream which defines Application objectswhose data is to be produced by thisConnection object

15 Get ConsumedPath Length

UINT Number of bytes of data in the consumedconnection path

16 Get ConsumedConnectionPath

ARRAYofUSINT

Byte stream which defines Application objectswhose data is to be consumed by thisConnection object


0x0E Yes Yes Get_Attribute_Single


Class Code

Instances

Class Attributes

Not supported.

Register Object


Instance Description1 All polled data being read from the DPI device (read-only)2 All polled data written to the DPI device (read/write)3 Logic Status and Feedback data (read-only)4 Logic Command and Reference data (read/write)5 Datalink A (input data from device to scanner) (read only)6 Datalink A (output data from scanner to device) (read/write)7 Datalink B (input data from device to scanner) (read only)8 Datalink B (output data from scanner to device) (read/write)9 Datalink C (input data from device to scanner) (read only)10 Datalink C (output data from scanner to device) (read/write)11 Datalink D (input data from device to scanner) (read only)12 Datalink D (output data from scanner to device) (read/write)13 Logic Status and Feedback Data (read-only)14 Mask(1) (read/write)

(1) The mask command word is set to the value of the first word of the data wherethere are ones in the second word of the data. Command = (word 1 and notword 2) or (word 1 and word 2). This only controls specified bits in the LogicCommand data to the DPI product and does not change the Reference value.


Instance Attributes

Important: Setting a register object attribute can only be accomplishedthrough a connection with a non-zero expected packet rate(EPR). This feature is to prevent accidental control of a DPIdevice.

Services

Register Object (Continued)

AttributeID

Access Rule Name Data Type Description

1 Get Bad Flag BOOL If set to 1, then attribute 4 may containinvalid, bad or otherwise corrupt data.0 = good1 = bad

2 Get Direction BOOL Direction of data transfer0 = Producer Register1 = Consumer Register

3 Get Size UINT Size of register data in bits4 Conditional(1) Data ARRAY of

BITSData to be transferred

(1) The access rule of Set is optional if attribute 2, Direction = 1. If Direction = 0, the access ruleis Get.


0x0E Yes Yes Get_Attribute_Single0x10 No Yes Set_Attribute_Single


Class Code

Instances

The number of instances depends on the number of parameters in theDPI drive. The adapter parameters are appended to the list of driveparameters. The total number of parameters can be read in Instance 0,Attribute 2

Class Attributes

Parameter Object

Hexadecimal Decimal0x0F 15

Instance Description0 Class Attributes1 Drive Parameter 1 Attributes

… …

n Last Drive Parameter Attributesn + 1 Adapter Parameter 1 Attributes

… …

n + 43 Last Adapter Parameter Attributes

AttributeID

AccessRule


1 Get Revision UINT 12 Get Max Instance UINT Number of parameters8 Get Parameter

ClassDescriptor

WORD Bits that describe parameters.

9 Get ConfigurationAssemblyInstance

UINT 0

10 Get NativeLanguage

USINT 0 = English1 = French2 = Spanish3 = Italian4 = German5 = Japanese6 = Portuguese7 = Mandarin Chinese8 = Russian9 = Dutch


Instance Attributes

Parameter Object (Continued)

AttributeID

AccessRule


1 (1) Parameter Value (2) (3)

2 Get Link Path Size USINT 0 = No link specifiedn = Link specified

3 Get Link Path (4)

4 Get Descriptor WORD 0 = False, 1 = TrueBit 1 = Supports ENUMsBit 2 = Supports scalingBit 3 = Supports scaling linksBit 4 = Read onlyBit 5 = MonitorBit 6 = Extended precision scaling

5 Get Data Type USINT 1 = WORD (16-bit)2 = UINT (16-bit)3 = INT (16-bit)4 = BOOL5 = SINT6 = DINT7 = LINT8 = USINT

6 Get Data Size USINT (3)

7 Get Parameter NameString

SHORT_STRING

(3)

8 Get Units String SHORT_STRING

(3)

9 Get Help String SHORT_STRING

0

10 Get Minimum Value (1) (3)

11 Get Maximum Value (1) (3)

12 Get Default Value (1) (3)

13 Get Scaling Multiplier UINT (3)

14 Get Scaling Divisor UINT (3)

15 Get Scaling Base UINT (3)

16 Get Scaling Offset UINT (3)

17 Get Multiplier Link UINT (3)

18 Get Divisor Link UINT (3)

19 Get Base Link UINT (3)

20 Get Offset Link UINT (3)

21 Get DecimalPrecision

USINT (3)

(1) Access rule is defined in bit 4 of instance attribute 4. 0 = Get/Set, 1 = Get.(2) Specified in descriptor, data type, and data size.(3) Value varies based on parameter instance.(4) Refer to the DeviceNet specification for a description of the connection path.


Services

Parameter Object (Continued)


0x01 No Yes Get_Attribute_All0x05 Yes No Reset0x0E Yes Yes Get_Attribute_Single0x10 No Yes Set_Attribute_Single0x15 Yes No Restore_Request0x16 Yes No Save_Request0x4B No Yes Get_Enum_String


Class Code

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 thedevice. The total number of groups can be read in Instance 0, Attribute 2.

Class Attributes

Parameter Group Object


Number Description0 Class Attributes1 Drive Group 1 Attributes

… …

n Last Drive Group Attributesn + 1 Adapter Group Attributes

AttributeID

AccessRule

Name DataType

Description

1 Get Parametergroupversion

UINT 1

2 Get Max Instance UINT Total number of groups8 Get Native

LanguageUSINT 0 = English

1 = French2 = Spanish (Mexican)3 = Italian4 = German5 = Japanese6 = Portuguese7 = Mandarin Chinese8 = Russian9 = Dutch


Instance Attributes

Services

Parameter Group Object (Continued)

AttributeID

AccessRule

Name DataType

Description

1 Get Group Name String SHORT_STRING

Group name

2 Get Number of Membersin Group

UINT Number of parameters in group.

3 Get 1st Parameter Numberin Group

UINT (1)

4 Get 2nd ParameterNumber in Group

UINT (1)

n Get … UINT (1)

(1) Value varies based on group instance.


0x0E Yes Yes Get_Attribute_Single


Class Code

Instances

Not supported

Class Attributes

Not supported.

Instance Attributes

Not supported.

Services

PCCC Object



0x4B No Yes Execute_PCCC0x4D No Yes Execute_Local_PCCC


Message Structure for Execute_PCCC

Message Structure for Execute_Local_PCCC

PCCC Object (Continued)

Request ResponseName Data

TypeDescription Name Data

TypeDescription

Length USINT Length ofrequestor ID

Length USINT Length of requestor ID

Vendor UINT Vendor numberof requestor

Vendor UINT Vendor number of requestor

SerialNumber

UDINT ASA serialnumber ofrequestor

SerialNumber

UDINT ASA serial number ofrequestor

Other ProductSpecific

Identifier of user,task, etc. on therequestor

Other ProductSpecific

Identifier of user, task, etc.on the requestor

CMD USINT Command byte CMD USINT Command byteSTS USINT 0 STS USINT Status byteTNSW UINT Transport word TNSW UINT Transport word. Same value

as the request.FNC USINT Function code.

Not used for allCMD’s.

EXT_STS USINT Extended status. Not usedfor all CMD’s.

PCCC_params

ARRAYofUSINT

CMD/FNCspecificparameters

PCCC_results

ARRAYofUSINT

CMD/FNC specific resultdata

Request ResponseName Data

TypeDescription Name Data

TypeDescription

CMD USINT Command byte CMD USINT Command byteSTS USINT 0 STS USINT Status byteTNSW UINT Transport word TNSW UINT Transport word. Same value

as the request.FNC USINT Function code.

Not used for allCMD’s.

EXT_STS USINT Extended status. Not usedfor all CMD’s.

PCCC_params

ARRAYofUSINT

CMD/FNCspecificparameters

PCCC_results

ARRAY ofUSINT

CMD/FNC specific resultdata


Class Code

Instances

The number of instances depends on the number of components in thedevice. The total number of components can be read in Instance 0,Attribute 4.

Class Attributes

DPI Device Object


Number Description0 Class Attributes (Drive)1 Drive Component 12 Drive Component 2

… …

16384 Class Attributes (Adapter)16385 Adapter Component 1

… …

AttributeID

AccessRule


0 Get Family Code BYTE 0x00 = Communications Adapter0x30 = PowerFlex 700x38 = PowerFlex 7000x40 = PowerFlex 70000xFF = HIM

1 Get Family Text STRING[16] Text identifying the device.2 Get/Set Language Code BYTE 0 = English

1 = French2 = Spanish3 = Italian4 = German5 = Japanese6 = Portuguese7 = Mandarin Chinese8 = Russian9 = Dutch

3 Get Product Series BYTE 1 = A2 = B…

4 Get Number ofComponents

BYTE Number of components (e.g., main controlboard, I/O boards) in the device.

5 Get/Set User DefinableText

STRING[16] Text identifying the device with auser-supplied name

6 Get Status Text STRING[12] Text describing the status of the drive.


Class Attributes (Continued)

DPI Device Object (Continued)

AttributeID

AccessRule


7 Get ConfigurationCode

BYTE Identification of variations.

8 Get Configuration Text STRING[16] Text identifying a variation of a familydevice.

9 Get Brand Code WORD 0x0001 = Allen-Bradley11 Get NVS Checksum WORD Checksum of the Non-Volatile Storage in

a device.12 Get Class Revision WORD 2 = DPI13 Get Character Set

CodeBYTE 0 = SCANport HIM

1 = ISO 8859-1 (Latin 1)2 = ISO 8859-2 (Latin 2)3 = ISO 8859-3 (Latin 3)4 = ISO 8859-4 (Latin 4)5 = ISO 8859-5 (Cyrillic)6 = ISO 8859-6 (Arabic)7 = ISO 8859-7 (Greek)8 = ISO 8859-8 (Hebrew)9 = ISO 8859-9 (Turkish)10 = ISO 8859-10 (Nordic)255 = ISO 10646 (Unicode)

15 Get LanguagesSupported

STRUCT ofBYTEBYTE[n]

Number of LanguagesLanguage Codes (See Class Attribute 2)

16 Get Date ofManufacture

STRUCT ofWORDBYTEBYTE

YearMonthDay

17 Get Product Revision STRUCT ofBYTEBYTE

Major Firmware ReleaseMinor Firmware Release

18 Get Serial Number DWORD Value between 0x00 and 0xFFFFFFFF19 Get/Set Language

SelectedBYTE 0 = Default (HIM will prompt at start up)

1 = Language was selected (no prompt)20 Get/Set Customer-

GeneratedFirmware

STRING[36] GUID (Globally Unique Identifier)identifying customer firmware flashed intothe device.

128 Get CustomizationCode

WORD Code identifying the customized device.

129 Get CustomizationRevision Number

WORD Revision of the customized device.

130 Get CustomizationDevice Text

STRING[32] Text identifying the customized device.


Instance Attributes

Services

DPI Device Object (Continued)

AttributeID

AccessRule


3 Get ComponentName

STRING[32] Name of the component

4 Get ComponentFirmwareRevision

STRUCT ofBYTEBYTE

Major RevisionMinor Revision

5 Get ComponentHardwareChange Number

BYTE 0 = Not Available

6 Get First Flash ObjectInstance

WORD Instance in the Flash Object used for thefirmware in the component

7 Get Number of FlashObject Instances

BYTE Number of segments in memory that canbe flashed.

8 Get ComponentSerial Number

DWORD Value between 0x00 and 0xFFFFFFFF


0x0E Yes Yes Get_Attribute_Single0x10 Yes Yes Set_Attribute_Single


Class Code

Instances

The number of instances depends on the number of parameters in thedevice. The total number of parameters can be read in Instance 0,Attribute 0.

Class Attributes

DPI Parameter Object


Number Description0 Class Attributes (Drive)1 Drive Parameter 1 Attributes2 Drive Parameter 2 Attributes

… …

16384 Class Attributes (Adapter)16385 Adapter Parameter 1 Attributes

… …

AttributeID

AccessRule


0 Get Number ofInstances

WORD Number of parameters in the device

1 Get/Set Write ProtectPassword

WORD 0 = Password disabledn = Password

2 Set NVS CommandWrite

BYTE 0 = No Operation1 = Store values in active memory to NVS2 = Load values in NVS to active memory3 = Load default values to active memory

3 Get NVS ParameterValue Checksum

WORD Checksum of all parameter values in auser set in NVS

4 Get NVS Link ValueChecksum

WORD Checksum of parameter links in a user setin NVS

5 Get First AccessibleParameter

WORD First parameter available if parametersare protected by passwords. A “0”indicates all parameters are protected.

7 Get Class Revision WORD 2 = DPI8 Get First Parameter

Processing ErrorWORD The first parameter that has been written

with a value outside of its range. A “0”indicates no errors.

9 Set Link Command BYTE 0 = No Operation1 = Clear All Parameter Links (This does

not clear links to function blocks.)


Instance Attributes

DPI Parameter Object (Continued)

AttributeID

AccessRule


7 Get DPI Online ReadFull

STRUCT ofBOOL[32]CONTAINER(1)

CONTAINERCONTAINERCONTAINERWORDWORDSTRING[4]UINTUINTUINTINTBYTE[3]BYTESTRING[16]

Descriptor (Refer to pages C-20 – C-21)Parameter valueMinimum valueMaximum valueDefault valueNext parameterPrevious parameterUnits (e.g., Amp, Hz)Multiplier(2)

Divisor (2)

Base(2)

Offset(2)

Link (source of the value) (0 = no link)Always zero (0)Parameter name

8 Get DPI Descriptor BOOL[32] Descriptor (Refer to pages C-20 – C-21)9 Get/Set DPI Parameter

ValueVarious Parameter value in NVS.(3)

10 Get/Set DPI RAMParameter Value

Various Parameter value in temporary memory.

11 Get/Set DPI Link BYTE[3] Link (parameter or function block that isthe source of the value) (0 = no link)

12 Get Help ObjectInstance

WORD ID for help text for this parameter

13 Get DPI Read Basic STRUCT ofBOOL[32]CONTAINERCONTAINERCONTAINERCONTAINERSTRING[16]STRING[4]

Descriptor (Refer to pages C-20 – C-21)Parameter valueMinimum valueMaximum valueDefault valueParameter nameUnits (e.g., Amp, Hz)

14 Get DPI ParameterName

STRING[16] Parameter name

15 Get DPI ParameterAlias

STRING[16] Customer supplied parameter name. Onlysupported by PowerFlex 700S at time ofpublication.

16 Get ParameterProcessing Error

BYTE 0 = No error1 = Value is less than the minimum2 = Value is greater than the maximum

(1) A CONTAINER is a 32-bit block of data that contains the data type used by a parameter value. Ifsigned, the value is sign extended. Padding is used in the CONTAINER to ensure that it is always32-bits.

(2) This value is used in the formulas used to convert the parameter value between display units andinternal units. Refer to Formulas for Converting on page C-21.

(3) Do NOT continually write parameter data to NVS. Refer to the attention on page 6-1.


Descriptor Attributes


Bit Name Description0 Data Type (Bit 1) Right bit is least significant bit (0).

000 = BYTE used as an array of Boolean001 = WORD used as an array of Boolean010 = BYTE (8-bit integer)011 = WORD (16-bit integer)100 = DWORD (32-bit integer)101 = TCHAR (8-bit (not unicode) or 16-bits (unicode))110 = REAL (32-bit floating point value)111 = Use bits 16, 17, 18

1 Data Type (Bit 2)

2 Data Type (Bit 3)

3 Sign Type 0 = unsigned1 = signed

4 Hidden 0 = visible1 = hidden

5 Not a Link Sink 0 = Parameter can sink a link1 = Parameter cannot sink a link

6 Not Recallable 0 = Recallable from NVS1 = Not Recallable from NVS

7 ENUM 0 = No ENUM text1 = ENUM text

8 Writable 0 = Read only1 = Read/write

9 Not Writable WhenEnabled

0 = Writable when enabled (e.g., drive running)1 = Not writable when enabled

10 Instance 0 = Parameter value is not a Reference to anotherparameter

1 = Parameter value refers to another parameter11 Reserved Must be zero12 Decimal Place (Bit 0) Number of digits to the right of the decimal point.

0000 = 01111 = 15

13 Decimal Place (Bit 1)14 Decimal Place (Bit 2)15 Decimal Place (Bit 3)16 Extended

Data Type (Bit 1)Right bit is least significant bit (16).000 = Reserved001 = DWORD used as an array of Boolean010 = Reserved011 = Reserved100 = Reserved101 = Reserved110 = Reserved111 = Reserved

17 ExtendedData Type (Bit 2)

18 ExtendedData Type (Bit 2)


Descriptor Attributes

Formulas for ConvertingDisplay Value = ((Internal Value + Offset) x Multiplier x Base) / (Divisor x 10Decimal Places)

Internal Value = ((Display Value x Divisor x 10Decimal Places) / (Multiplier x Base)) - Offset

Common Services

Object Specific Services


Bit Name Description19 Parameter Exists Reserved20 Not Used Reserved21 Formula Links Reserved22 Access Level (Bit 1) Reserved23 Access Level (BIt 2) Reserved24 Access Level (Bit 3) Reserved25 Writable ENUM Reserved26 Not a Link Source 0 = Parameter can be a source for a link

1 = Parameter cannot be a source for a link27 Enhanced Bit ENUM Reserved28 Enhanced ENUM Reserved29 Not Used Reserved30 Not Used Reserved31 Not Used Reserved




0x4B Yes Yes Get_Attributes_Scattered0x4C Yes Yes Set_Attributes_Scattered


Format for Get_Attributes_Scattered Service

The structure shown below can get up to eight parameters in a singlemessage. In the Response Message, a parameter number with the highbit set indicates that the associated parameter value field actuallycontains an error code.


Request ResponseWord 0 TXID Command TXID Status

1 Port Size Port Size2 Service Address Service Address3 Class Parameter Number4 Instance Parameter Value LSW5 Attribute Parameter Value MSW6 Parameter Number Parameter Number7 Pad Word Parameter Value LSW8 Pad Word Parameter Value MSW9 Parameter Number Parameter Number

10 Pad Word Parameter Value LSW11 Pad Word Parameter Value MSW12 Parameter Number Parameter Number13 Pad Word Parameter Value LSW14 Pad Word Parameter Value MSW15 Parameter Number Parameter Number16 Pad Word Parameter Value LSW17 Pad Word Parameter Value MSW18 Parameter Number Parameter Number19 Pad Word Parameter Value LSW20 Pad Word Parameter Value MSW21 Parameter Number Parameter Number22 Pad Word Parameter Value LSW23 Pad Word Parameter Value MSW24 Parameter Number Parameter Number25 Pad Word Parameter Value LSW26 Pad Word Parameter Value MSW27 Parameter Number Not Used28 Pad Word Not Used29 Pad Word Not Used30 Not Used Not Used

Word 31 Not Used Not Used


The PLC data in this example is for a Get_Attributes_Scattered ofPowerFlex 70 parameters; 1 - [Output Freq], 3 - [Output Current] and6 - [Output Voltage] from a device at node address 1.

Request Data for Get_Attributes_Scattered

Response Data for Get_Attributes_Scattered


Address Value (hex) Description Refer to . . .N30:0 0101 TXID = 01, Command = 01 (execute) 6-5N30:1 0018 Port = 00, Size = 24 bytes (18 hex) 6-5N30:2 4B01 Service = 4B (Get_Attributes_Scattered) C-21

Address = 01 (Node Address) 6-5N30:3 0093 Class = 93 (DPI Parameter Object) C-18N30:4 0000 Instance = Class Attributes (drive) C-18N30:5 0000 Attribute (not used for this service) C-18N30:6 0001 Parameter Number 1N30:7 0000 Pad WordN30:8 0000 Pad WordN30:9 0003 Parameter Number 3N30:10 0000 Pad WordN30:11 0000 Pad WordN30:12 0006 Parameter Number 6N30:13 0000 Pad WordN30:14 0000 Pad Word

Address Value (hex) Description Refer to . . .N30:70 0101 TXID = 01, Status = 01 (successful transaction) 6-6N30:71 0012 Port = 00, Size = 18 bytes (12 hex) 6-6N30:72 CB01 Service = CB (successful) 6-6

Address = 01 (Node Address) 6-6N30:73 0001 Parameter Number 1N30:74 0258 Value = 600 (258 hex) = 60.0 HzN30:75 0000N30:76 0003 Parameter Number 3N30:77 0001 Value = 1 (1 hex) = 0.1AN30:78 0000N30:79 0006 Parameter Number 6N30:80 0864 Value = 2148 (864 hex) = 214.8V ACN30:81 0000


Format for Set_Attributes_Scattered Service

The structure shown below can get up to eight parameters in a singlemessage. In the Response Message, a parameter number with the highbit set indicates that the associated pad word field contains an error code.


Request ResponseWord 0 TXID Command TXID Status

1 Port Size Port Size2 Service Address Service Address3 Class Parameter Number4 Instance Pad Word or Error Code5 Attribute Pad Word6 Parameter Number Parameter Number7 Parameter Value LSW Pad Word or Error Code8 Parameter Value MSW Pad Word9 Parameter Number Parameter Number

10 Parameter Value LSW Pad Word or Error Code11 Parameter Value MSW Pad Word12 Parameter Number Parameter Number13 Parameter Value LSW Pad Word or Error Code14 Parameter Value MSW Pad Word15 Parameter Number Parameter Number16 Parameter Value LSW Pad Word or Error Code17 Parameter Value MSW Pad Word18 Parameter Number Parameter Number19 Parameter Value LSW Pad Word or Error Code20 Parameter Value MSW Pad Word21 Parameter Number Parameter Number22 Parameter Value LSW Pad Word or Error Code23 Parameter Value MSW Pad Word24 Parameter Number Parameter Number25 Parameter Value LSW Pad Word or Error Code26 Parameter Value MSW Pad Word27 Parameter Number Not Used28 Parameter Value LSW Not Used29 Parameter Value MSW Not Used30 Not Used Not Used

Word 31 Not Used Not Used


The PLC data in this example is for a Set_Attributes_Scattered ofPowerFlex 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

Response Data for Set_Attributes_Scattered


Address Value (hex) Description Refer to . . .N30:0 0101 TXID = 01, Command = 01 (execute) 6-5N30:1 0018 Port = 00, Size = 24 bytes (18 hex) 6-5N30:2 4C01 Service = 4C (Set_Attributes_Scattered) C-21

Address = 01 (Node Address) 6-5N30:3 0093 Class = 93 (DPI Parameter Object) C-18N30:4 0000 Instance = Class Attributes (drive) C-18N30:5 0000 Attribute (not used for this service)N30:6 008C Parameter Number 140 (8C hex)N30:7 0032 Value = 50 (32 hex) = 5.0 secondsN30:8 0000N30:9 008E Parameter Number 142 (8E hex)N30:10 0032 Value = 50 (32 hex) = 5.0 secondsN30:11 0000N30:12 0064 Parameter Number 100 (64 hex)N30:13 0064 Value = 100 (64 hex) = 10.0 HzN30:14 0000

Address Value (hex) Description Refer to . . .N30:70 0101 TXID = 01, Status = 01 (successful transaction) 6-6N30:71 0012 Port = 00, Size = 18 bytes (12 hex) 6-6N30:72 CC01 Service = CC (successful) 6-6

Address = 01 (Node Address) 6-6N30:73 008C Parameter Number 140 (8C hex)N30:74 0000N30:75 0000N30:76 008E Parameter Number 142 (8E hex)N30:77 0000N30:78 0000N30:79 0064 Parameter Number 100 (64 hex)N30:80 0000N30:81 0000


Class Code

Products such as PowerFlex drives use this object for faults. Adaptersuse this object for events.

Instances

The number of instances depends on the maximum number of faults orevents supported in the queue. The maximum number of faults/eventscan be read in Instance 0, Attribute 2.

Class Attributes

DPI Fault Object


Number Description0 Class Attributes (Drive)1 Most Recent Drive Fault/Event2 Second Most Recent Drive Fault/Event

… …

16384 Class Attributes (Adapter)16385 Most Recent Adapter Fault/Event

… …

AttributeID

AccessRule


1 Get Class Revision WORD Revision of object2 Get Number of

InstancesWORD Maximum number of faults/events that the

device can record in its queue3 Set Fault Command

WriteBYTE 0 = No Operation

1 = Clear Fault/Event2 = Clear Fault/Event Queue3 = Reset Device

4 Get Fault TripInstance Read

WORD Fault that tripped the device. For adapters,this value is always 1 when faulted.

5 Get Fault Data List STRUCT ofBYTEBYTEWORD[n]

Reserved

6 Get Number ofRecorded Faults

WORD Number of faults/events in the queue. A“0” indicates the fault queue is empty.

7 Get Fault ParameterReference

WORD Reserved


Instance Attributes

Services

DPI Fault Object (Continued)

AttributeID

AccessRule


0 Get Full/AllInformation

STRUCT ofWORDSTRUCT ofBYTEBYTESTRING[16]STRUCT ofLWORDBOOL[16]

WORDCONTAINER[n]

Fault codeFault sourceDPI portDPI Device ObjectFault textFault time stampTimer value (0 = Timer not supported)BOOL[0]: (0 = invalid data, 1 = valid data)BOOL[1]: (0 = elapsed time, 1 = real time)BOOL[2 - 15]: Not usedReservedReserved

1 Get BasicInformation

STRUCT ofWORDSTRUCT ofBYTEBYTESTRUCT ofLWORDBOOL[16]

Fault codeFault sourceDPI portDPI Device ObjectFault time stampTimer value (0 = Timer not supported)BOOL[0]: (0 = invalid data, 1 = valid data)BOOL[1]: (0 = elapsed time, 1 = real time)BOOL[2 - 15]: Not used




Class Code

Products such as PowerFlex drives use this object for alarms orwarnings. Adapters do not support this object.

Instances

The number of instances depends on the maximum number of alarmssupported by the queue. The maximum number of alarms can be read inInstance 0, Attribute 2.

Class Attributes

DPI Alarm Object


Number Description0 Class Attributes1 Most Recent Alarm2 Second Most Recent Alarm

… …

AttributeID

AccessRule



InstancesWORD Maximum number of alarms that the

device can record in its queue3 Set Alarm Command


1 = Clear Alarm2 = Clear Alarm Queue3 = Reset Device

4 Get Fault Data List STRUCT ofBYTEBYTEWORD[n]

Reserved

5 Get Number ofRecorded Alarms

WORD Number of alarms in the queue. A “0”indicates the alarm queue is empty.


Instance Attributes

Services

DPI Alarm Object (Continued)

AttributeID

AccessRule


0 Get Full/AllInformation

STRUCT ofWORDSTRUCT ofBYTEBYTESTRING[16]STRUCT ofLWORDBOOL[16]

WORDCONTAINER[n]

Alarm codeAlarm sourceDPI portDPI Device ObjectAlarm textAlarm time stampTimer value (0 = Timer not supported)BOOL[0]: (0 = invalid data, 1 = valid data)BOOL[1]: (0 = elapsed time, 1 = real time)BOOL[2 - 15] ReservedReservedReserved

1 Get BasicInformation

STRUCT ofWORDSTRUCT ofBYTEBYTESTRUCT ofLWORDBOOL[16]

Alarm codeAlarm sourceDPI portDPI Device ObjectAlarm time stampTimer value (0 = Timer not supported)BOOL[0]: (0 = invalid data, 1 = valid data)BOOL[1]: (0 = elapsed time, 1 = real time)BOOL[2 - 15] Reserved




Class Code

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 maynot support it. The total number of timers can be read in Instance 0,Attribute 2.

Class Attributes

DPI Time Object

Hexadecimal Decimal0x9B 155

Number Description0 Class Attributes1 Real Time Clock (Predefined)

(Not always supported)2 Timer 13 Timer 2

… …

AttributeID

AccessRule



InstancesWORD Number of timers in the object, excluding

the real time clock that is predefined.3 Get First Device

Specific TimerWORD Instance of the first timer that is not

predefined.4 Set Time Command


1 = Clear all timers (Does not clear thereal time clock or read only timers)


Instance Attributes

Services

DPI Time Object (Continued)

AttributeID

AccessRule


0 Get Read Full STRUCT ofSTRING[16]LWORD orSTRUCTBOOL[16]

Name of the timerElapsed time in milliseconds unless timeris a real time clock (See attribute 2)See Attribute 3

1 Get Timer Text STRING[16] Name of the timer2 Get/Set Timer Value LWORD

-OR-STRUCT ofWORDBYTEBYTEBYTEBYTEBYTEBYTE

Elapsed time in milliseconds unless thetimer is a real time clock.Real Time Clock Data:Milliseconds (0 – 999)Seconds (0 – 59)Minutes (0 – 59)Hours (0 – 23)Days (1 – 31)Months (1 = January, 12 = December)Years (since 1972)

3 Get TimerDescriptor

BOOL[16] BOOL[0]: (0 = invalid data, 1 = valid data)BOOL[1]: (0 = elapsed time, 1 = real time)BOOL[2 - 15]: Not used




Notes:

Appendix D

Logic Command/Status Words

Appendix D provides the definitions of the Logic Command/LogicStatus words that are used for some products that can be connected to theDeviceNet adapter. If you do not see the Logic Command/Logic Statusfor the product that you are using, refer to your product’s documentation.

Logic Command Word

* A 0 = Not Stop condition (logic 0) must first be present before a 1 = Start condition will start the drive.

PowerFlex 70 and PowerFlex 700 Drives

Logic Bits15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command Description

x Stop 0 = Not Stop1 = Stop

x Start* 0 = Not Start1 = Start

x Jog 0 = Not Jog1 = Jog

x ClearFaults

0 = Not Clear Faults1 = Clear Faults

x x Direction 00 = No Command01 = Forward Command10 = Reverse Command11 = Hold Direction Control

x LocalControl

0 = No Local Control1 = Local Control

x MOPIncrement

0 = Not Increment1 = Increment

x x Accel Rate 00 = No Command01 = Accel Rate 1 Command10 = Accel Rate 2 Command11 = Hold Accel Rate

x x Decel Rate 00 = No Command01 = Decel Rate 1 Command10 = Decel Rate 2 Command11 = Hold Decel Rate

x x x ReferenceSelect

000 = No Command001 = Ref. 1 (Ref A Select)010 = Ref. 2 (Ref B Select)011 = Ref. 3 (Preset 3)100 = Ref. 4 (Preset 4)101 = Ref. 5 (Preset 5)110 = Ref. 6 (Preset 6)111 = Ref. 7 (Preset 7)

x MOPDecrement

0 = Not Decrement1 = Decrement

D-2 Logic Command/Status Words

Logic Status Word

PowerFlex 70 and PowerFlex 700 Drives

Logic Bits15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Status Description

x Ready 0 = Not Ready1 = Ready

x Active 0 = Not Active1 = Active

x CommandDirection

0 = Reverse1 = Forward

x ActualDirection

0 = Reverse1 = Forward

x Accel 0 = Not Accelerating1 = Accelerating

x Decel 0 = Not Decelerating1 = Decelerating

x Alarm 0 = No Alarm1 = Alarm

x Fault 0 = No Fault1 = Fault

x At Speed 0 = Not At Reference1 = At Reference

x x x LocalControl

000 = Port 0 (TB)001 = Port 1010 = Port 2011 = Port 3100 = Port 4101 = Port 5110 = Port 6111 = No Local

x x x x Reference 0000 = Ref A Auto0001 = Ref B Auto0010 = Preset 2 Auto0011 = Preset 3 Auto0100 = Preset 4 Auto0101 = Preset 5 Auto0110 = Preset 6 Auto0111 = Preset 7 Auto1000 = Term Blk Manual1001 = DPI 1 Manual1010 = DPI 2 Manual1011 = DPI 3 Manual1100 = DPI 4 Manual1101 = DPI 5 Manual1110 = DPI 6 Manual1111 = Jog Ref

Appendix E

Master-Slave I/O Configuration

Appendix E lists possible configurations for the M-S Input/Outputparameters and the possible data size allocation associated with eachvalue depending on the method of data transfer.

Parameter 25 - [M-S Input] has the following five configurable bits.

Figure E.1 Bits and Corresponding I/O

When you enable Cmd/Ref or Datalink in the adapter, you must set thecorresponding bit in Parameter 25 - [M-S Input] if you want the inputdata to come from the scanner or master device.

Tables E.A and E.B list possible configurations for Parameter 25 -[M-S Input] and the possible data size allocation associated with eachvalue depending on the method of data transfer.

Topic PageM-S Input Parameter Configurations E-1M-S Output Parameter Configurations E-5

M-S Input Parameter Configurations

xxx0, 0000

Datalink D

Datalink CDatalink B

Datalink A

Cmd/Ref

0 = Peer or other input1 = Master-Slave input

E-2 Master-Slave I/O Configuration

Table E.A Host Products using 16-bit Reference/Feedback & Datalinks

M-SInput

M-SOutput

Allocation (Number of Bytes)Data Size sent from the Controller to the AdapterPoll Only COS Only Cyclic Only Poll & COS Poll & Cyclic

00000 xxxx0 0 NA NA NA NA00001 xxxx0 4 NA NA NA NA00010 xxxx0 4 NA NA NA NA00011 xxxx0 8 NA NA NA NA00100 xxxx0 4 NA NA NA NA00101 xxxx0 8 NA NA NA NA00110 xxxx0 8 NA NA NA NA00111 xxxx0 12 NA NA NA NA01000 xxxx0 4 NA NA NA NA01001 xxxx0 8 NA NA NA NA01010 xxxx0 8 NA NA NA NA01011 xxxx0 12 NA NA NA NA01100 xxxx0 8 NA NA NA NA01101 xxxx0 12 NA NA NA NA01110 xxxx0 12 NA NA NA NA01111 xxxx0 16 NA NA NA NA10000 xxxx0 4 NA NA NA NA10001 xxxx0 8 NA NA NA NA10010 xxxx0 8 NA NA NA NA10011 xxxx0 12 NA NA NA NA10100 xxxx0 8 NA NA NA NA10101 xxxx0 12 NA NA NA NA10110 xxxx0 12 NA NA NA NA10111 xxxx0 16 NA NA NA NA11000 xxxx0 8 NA NA NA NA11001 xxxx0 12 NA NA NA NA11011 xxxx0 16 NA NA NA NA11100 xxxx0 12 NA NA NA NA11101 xxxx0 16 NA NA NA NA11110 xxxx0 16 NA NA NA NA11111 xxxx0 20 NA NA NA NA00000 xxxx1 0 0 0 0 & 0 0 & 000001 xxxx1 4 4 4 4 & 0 4 & 000010 xxxx1 4 4 4 4 & 0 4 & 000011 xxxx1 8 8 8 8 & 0 8 & 000100 xxxx1 4 4 4 4 & 0 4 & 000101 xxxx1 8 8 8 8 & 0 8 & 000110 xxxx1 8 8 8 8 & 0 8 & 000111 xxxx1 12 12 12 12 & 0 12 & 001000 xxxx1 4 4 4 4 & 0 4 & 001001 xxxx1 8 8 8 8 & 0 8 & 001010 xxxx1 8 8 8 8 & 0 8 & 0

Master-Slave I/O Configuration E-3

01011 xxxx1 12 12 12 12 & 0 12 & 001100 xxxx1 8 8 8 8 & 0 8 & 001101 xxxx1 12 12 12 12 & 0 12 & 001110 xxxx1 12 12 12 12 & 0 12 & 001111 xxxx1 16 16 16 16 & 0 16 & 010000 xxxx1 4 4 4 4 & 0 4 & 010001 xxxx1 8 8 8 8 & 0 8 & 010010 xxxx1 8 8 8 8 & 0 8 & 010011 xxxx1 12 12 12 12 & 0 12 & 010100 xxxx1 8 8 8 8 & 0 8 & 010101 xxxx1 12 12 12 12 & 0 12 & 010110 xxxx1 12 12 12 12 & 0 12 & 010111 xxxx1 16 16 16 16 & 0 16 & 011000 xxxx1 8 8 8 8 & 0 8 & 011001 xxxx1 12 12 12 12 & 0 12 & 011011 xxxx1 16 16 16 16 & 0 16 & 011100 xxxx1 12 12 12 12 & 0 12 & 011101 xxxx1 16 16 16 16 & 0 16 & 011110 xxxx1 16 16 16 16 & 0 16 & 011111 xxxx1 20 20 20 20 & 0 20 & 0

M-SInput

M-SOutput



Table E.B Host Products using 32-bit Reference/Feedback & Datalinks

M-SInput

M-SOutput


00000 xxxx0 0 NA NA NA NA00001 xxxx0 8 NA NA NA NA00010 xxxx0 8 NA NA NA NA00011 xxxx0 16 NA NA NA NA00100 xxxx0 8 NA NA NA NA00101 xxxx0 16 NA NA NA NA00110 xxxx0 16 NA NA NA NA00111 xxxx0 24 NA NA NA NA01000 xxxx0 8 NA NA NA NA01001 xxxx0 16 NA NA NA NA01010 xxxx0 16 NA NA NA NA01011 xxxx0 24 NA NA NA NA01100 xxxx0 16 NA NA NA NA01101 xxxx0 24 NA NA NA NA01110 xxxx0 24 NA NA NA NA01111 xxxx0 32 NA NA NA NA10000 xxxx0 8 NA NA NA NA10001 xxxx0 16 NA NA NA NA10010 xxxx0 16 NA NA NA NA10011 xxxx0 24 NA NA NA NA10100 xxxx0 16 NA NA NA NA10101 xxxx0 24 NA NA NA NA10110 xxxx0 24 NA NA NA NA10111 xxxx0 32 NA NA NA NA11000 xxxx0 16 NA NA NA NA11001 xxxx0 24 NA NA NA NA11011 xxxx0 32 NA NA NA NA11100 xxxx0 24 NA NA NA NA11101 xxxx0 32 NA NA NA NA11110 xxxx0 32 NA NA NA NA11111 xxxx0 40 NA NA NA NA00000 xxxx1 0 0 0 0 & 0 0 & 000001 xxxx1 8 8 8 8 & 0 8 & 000010 xxxx1 8 8 8 8 & 0 8 & 000011 xxxx1 16 16 16 16 & 0 16 & 000100 xxxx1 8 8 8 8 & 0 8 & 000101 xxxx1 16 16 16 16 & 0 16 & 000110 xxxx1 16 16 16 16 & 0 16 & 000111 xxxx1 24 24 24 24 & 0 24 & 001000 xxxx1 8 8 8 8 & 0 8 & 001001 xxxx1 16 16 16 16 & 0 16 & 001010 xxxx1 16 16 16 16 & 0 16 & 0


Parameter 26 - [M-S Output] has the following five configurable bits.

Figure E.2 Bits and Corresponding I/O

When you enable Cmd/Ref or Datalink in the adapter, you must set thecorresponding bit in Parameter 26 - [M-S Output] if you want theoutput data to be sent to the scanner or master device.

Tables E.C and E.D list possible configurations for Parameter 26 -[M-S Output] and the possible data size allocation associated with eachvalue depending on the method of data transfer.

01011 xxxx1 24 24 24 24 & 0 24 & 001100 xxxx1 16 16 16 16 & 0 16 & 001101 xxxx1 24 24 24 24 & 0 24 & 001110 xxxx1 24 24 24 24 & 0 24 & 001111 xxxx1 32 32 32 32 & 0 32 & 010000 xxxx1 8 8 8 8 & 0 8 & 010001 xxxx1 16 16 16 16 & 0 16 & 010010 xxxx1 16 16 16 16 & 0 16 & 010011 xxxx1 24 24 24 24 & 0 24 & 010100 xxxx1 16 16 16 16 & 0 16 & 010101 xxxx1 24 24 24 24 & 0 24 & 010110 xxxx1 24 24 24 24 & 0 24 & 010111 xxxx1 32 32 32 32 & 0 32 & 011000 xxxx1 16 16 16 16 & 0 16 & 011001 xxxx1 24 24 24 24 & 0 24 & 011011 xxxx1 32 32 32 32 & 0 32 & 011100 xxxx1 24 24 24 24 & 0 24 & 011101 xxxx1 32 32 32 32 & 0 32 & 011110 xxxx1 32 32 32 32 & 0 32 & 011111 xxxx1 40 40 40 40 & 0 40 & 0

M-SInput

M-SOutput


M-S Output Parameter Configurations

xxx0, 0000

Datalink D

Datalink CDatalink B

Datalink A

Cmd/Ref

0 = Peer or other output1 = Master-Slave output


Table E.C Host Products using 16-bit Reference/Feedback & Datalinks

M-SInput

M-SOutput

Allocation (Number of Bytes)Data Size sent from the Adapter to the ControllerPoll Only COS Only Cyclic Only Poll & COS Poll & Cyclic

xxxxx 00000 0 NA NA NA NAxxxxx 00010 4 NA NA NA NAxxxxx 00100 4 NA NA NA NAxxxxx 00110 8 NA NA NA NAxxxxx 01000 4 NA NA NA NAxxxxx 01010 8 NA NA NA NAxxxxx 01100 8 NA NA NA NAxxxxx 11100 12 NA NA NA NAxxxxx 10000 4 NA NA NA NAxxxxx 10010 8 NA NA NA NAxxxxx 10100 8 NA NA NA NAxxxxx 10110 12 NA NA NA NAxxxxx 11000 8 NA NA NA NAxxxxx 11010 12 NA NA NA NAxxxxx 11100 12 NA NA NA NAxxxxx 11110 16 NA NA NA NAxxxxx 00001 4 4 4 4 & 4 4 & 4xxxxx 00011 8 4 4 8 & 4 8 & 4xxxxx 00101 8 4 4 8 & 4 8 & 4xxxxx 00111 12 4 4 12 & 4 12 & 4xxxxx 01011 12 4 4 12 & 4 12 & 4xxxxx 01101 12 4 4 12 & 4 12 & 4xxxxx 01111 16 4 4 16 & 4 16 & 4xxxxx 10001 8 4 4 8 & 4 8 & 4xxxxx 10011 12 4 4 12 & 4 12 & 4xxxxx 10101 12 4 4 12 & 4 12 & 4xxxxx 10111 16 4 4 16 & 4 16 & 4xxxxx 11001 12 4 4 12 & 4 12 & 4xxxxx 11011 16 4 4 16 & 4 16 & 4xxxxx 11101 16 4 4 16 & 4 16 & 4xxxxx 11111 20 4 4 20 & 4 20 & 4


Table E.D Host Products using 32-bit Reference/Feedback & Datalinks

M-SInput

M-SOutput

Allocation (Number of Bytes)Data Size sent from the Adapter to the ControllerPoll Only COS Only Cyclic Only Poll & COS Poll & Cyclic

xxxxx 00000 0 NA NA NA NAxxxxx 00010 8 NA NA NA NAxxxxx 00100 8 NA NA NA NAxxxxx 00110 16 NA NA NA NAxxxxx 01000 8 NA NA NA NAxxxxx 01010 16 NA NA NA NAxxxxx 01100 16 NA NA NA NAxxxxx 11100 24 NA NA NA NAxxxxx 10000 8 NA NA NA NAxxxxx 10010 16 NA NA NA NAxxxxx 10100 16 NA NA NA NAxxxxx 10110 24 NA NA NA NAxxxxx 11000 16 NA NA NA NAxxxxx 11010 24 NA NA NA NAxxxxx 11100 24 NA NA NA NAxxxxx 11110 32 NA NA NA NAxxxxx 00001 8 8 8 8 & 8 8 & 8xxxxx 00011 16 8 8 16 & 8 16 & 8xxxxx 00101 16 8 8 16 & 8 16 & 8xxxxx 00111 24 8 8 24 & 8 24 & 8xxxxx 01011 24 8 8 24 & 8 24 & 8xxxxx 01101 24 8 8 24 & 8 24 & 8xxxxx 01111 32 8 8 32 & 8 32 & 8xxxxx 10001 16 8 8 16 & 8 16 & 8xxxxx 10011 24 8 8 24 & 8 24 & 8xxxxx 10101 24 8 8 24 & 8 24 & 8xxxxx 10111 32 8 8 32 & 8 32 & 8xxxxx 11001 24 8 8 24 & 8 24 & 8xxxxx 11011 32 8 8 32 & 8 32 & 8xxxxx 11101 32 8 8 32 & 8 32 & 8xxxxx 11111 40 8 8 40 & 8 40 & 8


Notes:

Glossary

A Adapter

Devices such as drives, controllers, and computers usually require anadapter to provide a communication interface between them and anetwork such as DeviceNet. An adapter reads data on the network andtransmits it to the connected device. It also reads data in the device andtransmits it to the network.

The 20-COMM-D DeviceNet adapter is an adapter that connects,PowerFlex drives to a DeviceNet network. Adapters are sometimes alsocalled “cards,” “embedded communication options,” “gateways,”“modules,” and “peripherals.”

Automatic Device Replacement (ADR)

A means for replacing a malfunctioning device with a new unit, andhaving the device configuration data set automatically. The DeviceNetscanner is set up for ADR using RSNetWorx. The scanner uploads andstores a devices configuration. Upon replacing a malfunctioning devicewith a new unit (node 63), the scanner automatically downloads theconfiguration data and sets the node address.

B Bus Off

A bus off condition occurs when an abnormal rate of errors is detectedon the Control Area Network (CAN) bus in a device. The bus-off devicecannot receive or transmit messages on the network. This condition isoften caused by corruption of the network data signals due to noise ordata rate mismatch.

C Change of State (COS) I/O Data Exchange

A device that is configured for Change of State I/O data exchangetransmits data at a specified interval if its data remains unchanged. If itsdata changes, the device immediately transmits the change. This type ofexchange can reduce network traffic and save resources since unchangeddata does not need to be transmitted or processed.

CIP (Control and Information Protocol)

CIP is the transport and application layer protocol used for messagingover DeviceNet. The Control protocol is for implicit messaging (realtime I/O). The Information protocol is for explicit messaging(configuration, data collection, and diagnostics).

Glossary-2

Classes

A class is defined by the DeviceNet specification as “a set of objects thatall represent the same kind of system component. A class is ageneralization of an object. All objects in a class are identical in formand behavior, but may contain different attribute values.”

Controller

A controller, also called programmable logic controller, is a solid-statecontrol system that has a user-programmable memory for storage ofinstructions to implement specific functions such as I/O control, logic,timing, counting, report generation, communication, arithmetic, and datafile manipulation. A controller consists of a central processor, input/output interface, and memory. See also Scanner.

Cyclic I/O Data Exchange

A device configured for Cyclic I/O data exchange transmits data at auser-configured interval. This type of exchange ensures that data isupdated at an appropriate rate for the application, preserves bandwidthfor rapidly-changing devices, and allows data to be sampled at preciseintervals for better determinism.

D Data Rate

The data rate is the speed at which data is transferred on the DeviceNetnetwork. The available data rates depend on the type of cable and totalcable length used on the network:

Each device on a DeviceNet network must be set for the same data rate.You can set the DeviceNet adapter to 125 K, 250 K, or 500 K. You canset it to Autobaud if another device on the network has set the data rate.

Datalinks

A Datalink is a type of pointer used by some PowerFlex drives totransfer data to and from the controller. Datalinks allow specifiedparameter value(s) to be accessed or changed without using explicitmessages. When enabled, each Datalink consumes either four bytes oreight bytes in both the input and output image table of the controller. Thedrive determines the size of Datalinks.

Maximum Cable LengthCable 125 K 250 K 500 KThick Trunk Line 500 m (1,640 ft.) 250 m (820 ft.) 100 m (328 ft.)Thin Trunk Line 100 m (328 ft.) 100 m (328 ft.) 100 m (328 ft.)Maximum Drop Length 6 m (20 ft.) 6 m (20 ft.) 6 m (20 ft.)Cumulative Drop Length 156 m (512 ft.) 78 m (256 ft.) 39 m (128 ft.)

Glossary-3

DeviceNet Network

A DeviceNet network uses a producer/consumer Controller AreaNetwork (CAN) to connect devices (for example, controllers, drives, andmotor starters). Both I/O and explicit messages can be transmitted overthe network. A DeviceNet network can support a maximum of 64devices. Each device is assigned a unique node address and transmitsdata on the network at the same data rate.

A cable is used to connect devices on the network. It contains both thesignal and power wires. Devices can be connected to the network withdrop lines, in a daisy chain connection, or a combination of the two.

General information about DeviceNet and the DeviceNet specificationare maintained by the Open DeviceNet Vendor’s Association (ODVA).ODVA is online at http://www.odva.org.

DPI

DPI is a second generation peripheral communication interface used byvarious Allen-Bradley drives and power products. It is a functionalenhancement to SCANport.

DPI Peripheral

A device that provides an interface between DPI and a network or user.Peripheral devices are also referred to as “adapters” and “modules.” Theserial converter and PowerFlex HIM are examples of DPI peripherals.

DPI Product

A device that uses the DPI communications interface to communicatewith one or more peripheral devices. For example, a motor drive such asa PowerFlex drive is a DPI product. In this manual, a DPI product is alsoreferred to as “product” or “host.”

DriveExplorer Software

DriveExplorer software is a tool for monitoring and configuringAllen-Bradley products and adapters. It can be run on computers runningMicrosoft Windows 95, Windows 98, Windows NT (version 4.0 orgreater), and Windows CE (version 2.0 or greater) operating systems.DriveExplorer (version 2.xx) can be used to configure this adapter andPowerFlex drives. Information about DriveExplorer software and a freelite version can be accessed at http://www.ab.com/drives/driveexplorer.

Glossary-4

DriveTools Software

A software suite designed for Microsoft Windows 95, Windows 98, andWindows NT (4.0 or greater) operating systems. This software suiteprovides a family of tools that you can use to program, monitor, control,troubleshoot, and maintain Allen Bradley products. DriveTools 2000(version 1.xx) can be used with PowerFlex drives. Information aboutDriveTools can be accessed at http://www.ab.com/drives.

E Electronic Data Sheet (EDS) Files

EDS files are simple text files that are used by network configurationtools such as RSNetWorx for DeviceNet to describe products so that youcan easily commission them on a network. EDS files describe a productdevice type, revision, and configurable parameters. EDS files for manyAllen-Bradley products can be found at http://www.ab.com/networks/eds.

Explicit Messaging

Explicit Messages are used to configure, monitor, and diagnose devicesover DeviceNet.

F Fault Action

A fault action determines how the adapter and connected product actwhen a communications fault (for example, a cable is disconnected)occurs or when the scanner is switched out of run mode. The former usesa communications fault action, and the latter uses an idle fault action.

Fault Configuration

When communications are disrupted (for example, a cable isdisconnected), the adapter and PowerFlex drive can respond with auser-defined fault configuration. The user sets the data that is sent to thedrive in the fault configuration parameters (Parameters 15 - [Flt CfgLogic] through 24 - [Flt Cfg D2]). When a fault action parameter is setto use the fault configuration and a fault occurs, the data from theseparameters is sent as the Command Logic, Reference, and/orDatalink(s).

Faulted Node Recovery

This DeviceNet feature lets you change a configuration of a device thatis faulted on the network. For example, if you add a device to a networkand it does not have a unique address, it will fault. If you have aconfiguration tool that supports faulted node recovery and your adapteris using parameters to set its node address and data rate, you can changethe node address.

Glossary-5

Flash Update

The process of updating firmware in the adapter. The adapter can beflash updated using the X-Modem protocol and a 1203-SSS SmartSelf-powered Serial converter (firmware 3.xx).

H Heartbeat Rate

The heartbeat rate is used in Change of State (COS) data exchange. It isassociated with producing data once every EPR (Expected Packet Rate)duration. There may be four heartbeats before a time-out happens.

HIM (Human Interface Module)

A device that can be used to configure and control a PowerFlex drive.New HIMs (20-HIM-x) can be used to configure connected peripherals.

Hold Last

When communications are disrupted (for example, a cable isdisconnected), the adapter and PowerFlex drive can respond by holdinglast. Hold last results in the drive receiving the last data received via theDeviceNet connection before the disruption. If the drive was running andusing the Reference from the adapter, it will continue to run at the sameReference.

I I/O Data

I/O data, sometimes called “implicit messages” or “input/output,”transmit time-critical data such as a Logic Command and Reference. Theterms “input” and “output” are defined from the scanner’s point of view.Output is transmitted by the scanner and consumed by the adapter. Inputis transmitted by the adapter and consumed by the scanner.

L Logic Command/Logic Status

The Logic Command is used to control the PowerFlex drive (e.g., start,stop, direction). It consists of one 16-bit word of input to the adapterfrom the network. The definitions of the bits in this word depend on thedrive.

The Logic Status is used to monitor the PowerFlex drive (for example,operating state, motor direction). It consists of one 16-bit word of outputfrom the adapter to the network. The definitions of the bits in this worddepend on the drive.

Glossary-6

M Master-Slave Hierarchy

An adapter configured for a master-slave hierarchy exchanges data withthe master device. Usually, a network has one scanner which is themaster device, and all other devices (for example, drives connected toDeviceNet 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.

N Node Address

A DeviceNet network can have as many as 64 devices connected to it.Each device on the network must have a unique node address between 0and 63. Node address 63 is the default used by uncommissioned devices.Node addresses are sometimes called “MAC IDs.”

NVS (Non-Volatile Storage)

NVS is the permanent memory of a device. Devices such as the adapterand drive store parameters and other information in NVS so that they arenot lost when the device loses power. NVS is sometimes called“EEPROM.”

O Objects

The DeviceNet specification defines an object as “an abstractrepresentation of a particular component within a product.”

P PCCC (Programmable Controller Communications Command)

PCCC is the protocol used by some controllers to communicate withdevices on a network. Some software products (for example,DriveExplorer and DriveTools 2000) also use PCCC to communicate.

Peer-to-Peer Hierarchy

An adapter that is configured for a peer-to-peer hierarchy can exchangedata with a device on the network that is not a scanner. This type ofhierarchy can be set up so that a scanner configures or transmits data toone PowerFlex drive which then sends the same configuration or data toother PowerFlex drives on the network. To use a peer-to-peer hierarchy,you configure one adapter to transmit data (2 – 4 words) and one or moreadapters to receive the data.

Ping

A ping is a message that is sent by a DPI product to its peripheraldevices. They use the ping to gather data about the product, includingwhether it can receive messages and whether they can log in for control.

Glossary-7

Polled I/O Data Exchange

A device that is configured for polling I/O data exchange sends dataimmediately after it receives a request for the data. For example, anadapter receives a Logic Status Command from the scanner and thensends the Logic Status of the connected PowerFlex drive.

PowerFlex Drives

The Allen-Bradley PowerFlex family of drives include the PowerFlex 70and PowerFlex 700. These drives can be used for applications rangingfrom 0.37 kW (0.5 HP) to 3,000 kW (4,000 HP). All PowerFlex drivesimplement DPI, allowing them to use the 20COMM-D DeviceNetadapter. This manual focuses on using the adapter with PowerFlexdrives. Other products that implement DPI can also use the adapter.

Producer/Consumer Network

On producer/consumer networks, packets are identified by content ratherthan an explicit destination. If a node needs the packet, it will accept theidentifier and consume the packet. The source therefore sends a packetonce and all the nodes consume the same packet if they need it. Data isproduced once, regardless of the number of consumers. Also, bettersynchronization than Master-Slave networks is possible because dataarrives at each node at the same time

R Reference/Feedback

The Reference is used to send a Reference (for example, speed,frequency, torque) to the product. It consists of one word of input to theadapter from the network. The size of the word (either a 16-bit word or32-bit word) is determined by the drive.

Feedback is used to monitor the speed of a product. It consists of oneword of output from the adapter to the network. The size of the word(either a 16-bit word or 32-bit word) is determined by the drive.

RSNetWorx for DeviceNet

RSNetWorx for DeviceNet software is a tool for configuring andmonitoring DeviceNet networks and connected devices. It is a 32-bitWindows application that runs on Windows 95, Windows 98, andWindows NT. Information about RSNetWorx for DeviceNet softwarecan be found at http://www.software.rockwell.com/rsnetworx.

S Scanner

A scanner is a separate module (of a multi-module controller) or abuilt-in component (of a single-module controller) that providescommunication with adapters connected to a network. See alsoController.

Glossary-8

Status Indicators

Status indicators are LEDs that are used to report the status of theadapter, network, and drive. They are on the adapter and can be viewedon the front cover of the drive when the drive is powered.

T Type 0/Type 1/Type 2 Control

When transmitting I/O, the adapter can use different types of messagesfor control. The Type 0, Type 1, and Type 2 events help Allen-Bradleypersonnel identify the type of messages that an adapter is using.

U UCMM (UnConnected Message Manager)

UCMM provides a method to create connections between DeviceNetdevices.

Z Zero Data

When communications are disrupted (for example, a cable isdisconnected), the adapter and drive can respond with zero data. Zerodata results in the drive receiving zero as values for command data. If thedrive was running and using the Reference from the adapter, it will stayrunning but at zero Reference.

Index

Numerics10-pin linear plug, 2-3

5-pin linear plug, 2-3

Aadapter

adding to the scan list, 4-2applying power, 2-6commissioning, 2-1compatible products, 1-3components, 1-1definition, G-1features, 1-2grounding, 2-5illustration, 1-1installing, 2-1 to 2-6mapping I/O in the scanner, 4-5mounting, 2-5parameters, B-1 to B-7resetting, 3-17specifications, A-1tools to configure, 3-1troubleshooting, 7-1viewing the active configuration,

3-18

applying power to the adapter, 2-6

attentions, 1-4

Automatic Device Replacement(ADR)

definition, G-1

Bbaud rate, refer to data rate

bit definitions for logic command/status word, D-1

bus off, G-1

Ccables

DeviceNet, 2-3DPI Internal Interface, 2-4

catalog number, 1-1

Change of State (COS)configuring a scanner for, 4-4configuring an adapter for, 3-14definition, G-1

CIP, G-1

classes, G-2

Comm Flt Action parameter, B-2

commissioning the adapter, 2-1

communications module, refer toadapter

compatible products, 1-3

components, 1-1

configuration tools, 3-1

connecting the adapter to thenetwork, 2-3

Connection object, C-4

controllerControlLogix, 5-7, 6-8definition, G-2PLC, 5-9, 6-10running Explicit Messages, 6-7SLC, 5-11, 6-12

ControlLogixexample program for Explicit

Messages, 6-8example program for I/O, 5-7formatting Explicit Messages, 6-2

COS Fdbk Change parameter, B-5

COS Status Mask parameter, B-5

COS, refer to Change of State

COS/Cyc Interval parameter, B-5

Index-2

Cyclicconfiguring a scanner for, 4-4configuring an adapter for, 3-14definition, G-2

Ddata exchange

Change of State (COS), G-1Cyclic, G-2Polled, G-7

data ratedefinition, G-2setting with a parameter, 3-7setting with the switch, 2-2

Datalink Size parameter, B-2

datalinksdefinition, G-2in I/O image, 5-2using, 5-4

DeviceNet10-pin linear plug, 2-35-pin linear plug, 2-3cables, 2-3connector on adapter, 1-1definition, G-3example network, 4-1objects, C-1specification, G-3

DeviceNet adapter, refer to adapter

dimensions, A-1

DN Active Cfg parameter, B-3

DN Addr Actual parameter, B-2

DN Addr Cfg parameter, B-1

DN Rate Actual parameter, B-2

DN Rate Cfg parameter, B-2

DPIconnector on adapter, 1-1data rate, 3-18definition, G-3Internal Interface cable, 2-4peripheral, G-3products, G-3

DPI Alarm object, C-28

DPI Data Rate parameter, B-1

DPI Device object, C-15

DPI Fault object, C-26

DPI I/O Active parameter, B-3

DPI I/O Config parameter, B-3

DPI Parameter object, C-18

DPI Port parameter, B-1

DPI Time object, C-30

DriveExploreraccessing parameters with, 3-1definition, G-3free lite version, G-3supported feature, 1-2

drives, see PowerFlex drives

drives, see SCANport or DPIproducts

DriveToolsaccessing parameters with, 3-1definition, G-4supported feature, 1-2

EEDS (Electronic Data Sheet) files

creating with RSNetWorx, 3-5definition, G-4web site, G-4

EEPROM, refer to Non-VolatileStorage (NVS)

equipment required, 1-3

Index-3

eventsclearing, 7-4, 7-5list of, 7-6viewing, 7-4, 7-5

examplesabout I/O examples, 5-6datalinks, 5-5

Explicit Messagesabout, 6-1ControlLogix format, 6-2definition, G-4PLC format, 6-4running, 6-7SLC format, 6-4

Ffault action

configuring an adapter, 3-16definition, G-4

fault configurationconfiguring an adapter for, 3-16definition, G-4

faulted node recoverydefinition, G-4supported feature, 1-2

faults, refer to events

features, 1-2

firmware release, P-2

flash update, G-5

Flt Cfg A1 - D2 parameters, B-4

Flt Cfg Logic parameter, B-4

Flt Cfg Ref parameter, B-4

formatting Explicit Messages, 6-2

Ggoing online with RSNetWorx, 3-4

grounding the adapter, 2-5

Hheartbeat rate

definition, G-5setting in the scanner, 4-4

HIM (Human Interface Module)accessing parameters with, 3-1definition, G-5LCD model, 3-2LED model, 3-2

hold lastconfiguring an adapter for, 3-16definition, G-5

II/O

about, 5-1configuring an adapter for, 3-8configuring scanner for, 4-4definition, G-5examples, 5-6image, 5-2input, 4-6mapping in the scanner, 4-5output, 4-7

Identity object, C-2

Idle flt Action parameter, B-3

installationapplying power to the adapter, 2-6commissioning the adapter, 2-1connecting to the drive, 2-4connecting to the network, 2-3preparing for, 2-1

Internal Interface cable, 2-4

Internal Interface cablesconnecting to a drive, 2-4connecting to an adapter, 2-4illustration, 2-4

Index-4

LLCD HIM, 3-2

LED HIM, 3-2

LEDs, refer to status indicators

logic command/statusbit definitions, D-1definition, G-5in I/O image, 5-2using, 5-4

Logix5550, refer to ControlLogix

MMAC ID, refer to node address

manualconventions, P-2related documentation, P-1web site, P-1

master-slave communications, E-1,E-5

Master-Slave hierarchyconfiguring an adapter for, 3-9definition, G-6

mechanical dimensions, A-1

messages, refer to Explicit Messages

Min Peer Tx Time parameter, B-7

MOD status indicatorlocating, 7-1troubleshooting with, 7-2

modes of operation, 1-6

mounting the adapter, 2-5

M-S Input parameter, B-4

M-S Input Parameter Configurations,E-1

M-S Output parameter, B-5

M-S Output ParameterConfigurations, E-5

NNET A status indicator

locating, 7-1troubleshooting with, 7-3

NET B status indicatorlocating, 7-1not used, 7-1

node addressdefinition, G-6setting with a parameter, 3-7setting with switches, 2-2

Non-Volatile Storage (NVS)definition, G-6in adapter, 3-1in drive, 5-4, 6-1

Oobjects

definition, G-6list, C-1

ODVA, A-1, G-3

operating status, 1-6

PParameter object, C-8

parametersaccessing, 3-1active configuration, 3-18convention, P-2editing with RSNetWorx, 3-6list of, B-1 to B-7numbers, B-1

PCCCdefinition, G-6supported feature, 1-2

PCCC object, C-13

Peer A Input parameter, B-5

Peer A Output parameter, B-7

Peer B Input parameter, B-5

Index-5

Peer B Output parameter, B-7

Peer Cmd Mask parameter, B-6

Peer Flt Action parameter, B-6

Peer Inp Enable parameter, B-6

Peer Inp Status parameter, B-7

Peer Inp Timeout parameter, B-6

Peer Node to Inp parameter, B-6

Peer Out Enable parameter, B-7

Peer Out Skip parameter, B-7

Peer Ref Adjust parameter, B-6

Peer-to-Peer hierarchyconfiguring an adapter to receive

data, 3-11configuring an adapter to transmit

data, 3-10definition, G-6

ping, G-6

PLCexample program for Explicit


plug, 2-3

Polledconfiguring a scanner for, 4-4configuring an adapter for, 3-14definition, G-7

PORT status indicatorlocating, 7-1troubleshooting with, 7-2

power consumption, A-1

PowerFlex drives, G-770/700 logic command/status, D-1adding to the scan list, 4-2compatible with adapter, 1-3HIM, 3-2installing adapter on, 2-4mapping I/O in the scanner, 4-5

preparing for an installation, 2-1

processor, refer to controller

producer/consumer network, G-7

products, see SCANport or DPIproducts

programmable logic controller, referto controller

Qquick start, 1-5

RRef/Fdbk Size parameter, B-2

reference/feedbackdefinition, G-7in I/O image, 5-2using, 5-4

Register object, C-6

regulatory compliance, A-1

related documentation, P-1

Reset Module parameter, B-2

resetting an adapter, 3-17

ribbon cable, refer to InternalInterface cable

RSLinx, P-2, 3-3

RSNetWorx for DeviceNetcreating EDS files with, 3-5definition, G-7editing parameters with, 3-6going online, 3-4saving a network configuration,

4-8setting up RSLinx for, 3-3using to map I/O, 4-5using to set up a scan list, 4-2web site, G-7

Ssafety precautions, 1-4

scan list, 4-2

Index-6

scanneradding devices to a scan list, 4-2configuring for COS, Cyclic, or

Polled, 4-4definition, G-7in Master-Slave hierarchy, 3-8mapping I/O, 4-5

SLCexample program for Explicit


specificationsadapter, A-1DeviceNet, G-3

status indicatorsdefinition, G-8identifying, 1-6locating, 7-1

switcheslocating, 1-1setting, 2-2

Ttechnical support, P-2

tools required, 1-3

troubleshooting, 7-1

UUCMM, G-8

update, see flash update

Wweb site

for EDS files, G-4for manuals, P-1

wiring, refer to cables

Zzero data

configuring an adapter for, 3-16definition, G-8

Allen-Bradley, DPI, DriveExplorer, DriveTools 2000, DriveTools32,PLC-5, PowerFlex, SCANport, and SLC are trademarks of RockwellAutomation.

DeviceNet is a trademark of the Open DeviceNet Vendor Association.

RSLinx, RSLogix, and RSNetWorx are trademarks of RockwellSoftware.

Windows, Windows CE, Windows NT, and Microsoft are eitherregistered trademarks or trademarks of Microsoft Corporation.

Publication 20COMM-UM002A-EN-P – November, 2000 P/N 193664 (01)Copyright 2000 Rockwell International Corporation. All rights reserved. Printed in USA.

Reach us now at www.rockwellautomation.comWherever you need us, Rockwell Automation brings together leading brands in industrial automation including Allen-Bradley controls, Reliance Electric power transmission products, Dodge mechanical powertransmission components, and Rockwell Software. Rockwell Automation'sunique, flexible approach to helping customers achieve a competitiveadvantage is supported by thousands of authorized partners, distributors and system integrators around the world.

Americas Headquarters, 1201 South Second Street, Milwaukee, WI 53201-2496, USA, Tel: (1) 414 382-2000, Fax: (1) 414 382-4444European Headquarters SA/NV, Boulevard du Souverain 36, 1170 Brussels, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640Asia Pacific Headquarters, 27/F Citicorp Centre, 18 Whitfield Road, Causeway Bay, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846

devicenet adapter - rs componentsdocs-europe.electrocomponents.com/webdocs/0034/... · the examples...

Documents