Enhanced DeviceNet Communications Module

Transcription

1 Enhanced DeviceNet Communications Module Catalog Numbers: 1203-GU6 and 1336-GM6 Firmware: 2.xxx User Manual

2 Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards. The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication. Rockwell Automation publication SGI-1.1, Safety Guidelines for the Application, Installation, and Maintenance of Solid-State Control (available from your local Rockwell Automation office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication. Reproduction of the contents of this copyrighted publication, in whole or in part, without written permission of Rockwell Automation, is prohibited. Throughout this manual we use notes to make you aware of safety considerations:! ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage or economic loss. Attention statements help you to: Identify a hazard. Avoid the hazard. Recognize the consequences. Important: Identifies information that is critical for successful application and understanding of the product.

3 Summary of Changes Summary of Changes The information below summarizes the changes made to the company wide templates since the last release. Updated Information Changes to the adapter firmware include the following: Change Additions Corrections Description Added an Allen-Bradley proprietary object used by the PCP group. Corrected known bugs in the firmware. Changes to this manual include the following: Location Description P-3, 7-1, F-1 Attention regarding Explicit messaging was added. 1-4 Information was added in the footnotes. Chapter 4 Instructions for using DeviceNet Manager were replaced with instructions for using RSNetWorx for DeviceNet. Chapter 5 Instructions for using DeviceNet Manager were replaced with instructions for using RSNetWorx for DeviceNet. 6-2 Data in the I/O image was corrected. 6-4 Information was added about the Logic Command Bits 6-6 A change was made to the data in rung A change was made to the data in rung Appendix B Instructions for using DeviceNet Manager were removed. B-14 Value range for parameter 27 was added. Description for parameter 31 was corrected. C-20, C-22, C-23 Service Code for the Set_Attribute_Single was corrected.

4 Notes: Summary of Changes

5 Table of Contents Preface Chapter 1 Chapter 2 Chapter 3 Using this Manual Objectives P-1 Who Should Use this Manual? P-1 Purpose of this Manual P-1 Safety Precautions P-3 Terms and Abbreviations P-3 Conventions Used in this Manual P-4 Rockwell Automation Support P-4 Overview Chapter Objectives Overview of the Communications Adapter Features of the Communications Adapter SCANport Products Hardware and Parts Description Overview of Setting Up the Adapter Required Tools and Equipment Installation Chapter Objectives Installing a 1203-GU6 Module Installing a 1336-GM6 Board Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Chapter Objectives Factory Default Settings for the 1203-GU6 Module Required Tools and Equipment Establishing a Serial Connection to the Module Navigation Techniques Editing the Module s Parameters Displaying and Clearing the Module s Event Queue Viewing I/O Data Values Viewing DF-1 Statistics Viewing Your Module s Serial Number Performing a Flash Upgrade to the Module

6 ii Chapter 4 Table of Contents Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Chapter Objectives What is RSNetWorx for DeviceNet? Required Equipment and Software Going Online Creating an EDS File Accessing and Editing Parameters Chapter 5 Chapter 6 Chapter 7 Chapter 8 Appendix A Configuring a Scanner to Communicate with the Adapter Chapter Objectives Required Equipment and Software Example DeviceNet Network Setting Up the Scan List Mapping the Product s Data in the Scanner Saving the Configuration Ladder Logic Programming Chapter Objectives Required Equipment What is RSLogix? What are Ladder Logic Programs? Example Ladder Logic Programs Using DeviceNet Explicit Messaging Chapter Objectives Required Equipment Message Translations Messaging for the 1771-SDN Scanner Messaging for the 1747-SDN Scanner Examples Using Messages to Control SCANport Products Writing to Register Objects Troubleshooting Chapter Objectives LEDs on the Enhanced DeviceNet Adapter DeviceNet Network Status LED States Module Status LED States SCANport Status LED States Specifications Appendix Objectives A GU6 Specifications A GM6 Specifications A-2

7 Appendix B Table of Contents Enhanced DeviceNet Adapter s Parameters Appendix Objectives B-1 Setting the Node Address B-1 Setting the Data Rate B-2 Using Datalinks and Command I/O B-2 Using Master-Slave Communications B-4 Using Peer-to-Peer Communications B-6 Using Fault Configurable Inputs B-9 Enhanced DeviceNet Adapter Parameters B-10 iii Appendix C Appendix D Appendix E DeviceNet Objects Appendix Objectives C-1 Object Classes C-1 Class Code 0x01 Identity Object C-2 Class Code 0x02 Message Router Object C-4 Class Code 0x03 DeviceNet Object C-5 Class Code 0x05 Connection C-6 Class Code 0x07 Register Object C-8 Class Code 0x0F Parameter Object C-10 Class Code 0x10 Parameter Group Object C-16 Class Code 0x93 SCANport Pass-Through Parameter Object C-18 Class Code 0x97 SCANport Pass-Through Fault Object..... C-19 Class Code 0x98 SCANport Pass-Through Warning Object.. C-21 Class Code 0x99 SCANport Pass-Through Link Object..... C-23 Class Code 0x67 PCCC Object C-25 Supported PCCC Messages Appendix Objectives D-1 DF-1/PCCC Support (1203-GU6 Only) D-1 Supported PCCC Messages D-2 Related Documentation D-2 N-File Addresses Appendix Objectives E-1 N-File Addresses E-1

8 iv Appendix F Table of Contents Supported Emulated Block Transfer Commands Appendix Objectives F-1 What is Emulated Block Transfer? F-1 Supported Emulated Block Transfer Commands F-1 Emulated Block Transfer Status Word F-2 Parameter Value Read F-3 Parameter Value Write F-4 Parameter Read Full F-5 Product ID Number Read F-8 Scattered Parameter Value Read F-10 Scattered Parameter Value Write F-12 NVS Functions F-14 Fault Command Write F-15 Fault Queue Entry Read Full F-16 Fault Queue Size F-18 Trip Fault Queue Number F-19 Appendix G Event Queue Messages Appendix Objectives G-1 Event Queue Messages G-1

9 Preface Objectives Using this Manual Read this preface to become familiar with the organization of the manual. In this preface, you will read about the following: Who should use this manual. An overview of the Enhanced DeviceNet communications adapter. The purpose of this manual. Terms and abbreviations. Conventions used in this manual. Rockwell Automation support. Who Should Use this Manual? Use this manual if you are responsible for installing, wiring, programming, or troubleshooting control systems that use the Enhanced DeviceNet communications adapter. This manual is intended for qualified service personnel responsible for setting up and servicing the Enhanced DeviceNet communications adapter. You must have previous experience with and a basic understanding of electrical terminology, programming procedures, networking, required equipment and software, and safety precautions. Purpose of this Manual This manual is a learning and reference guide for the Enhanced DeviceNet communications adapter. It describes the procedures needed to install, configure, and troubleshoot the adapter.

10 P-2 Using this Manual Contents of this Manual This manual contains the following information: Chapter Title Contents Preface Using this Manual Describes the purpose, background, and scope of this manual. Also provides information on safety precautions and technical support. 1 Overview Provides an overview of the communications adapter, DeviceNet, and SCANport. 2 Installation Provides procedures for installing the 1203-GU6 module or 1336-GM6 board. 3 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 4 Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet 5 Configuring a Scanner to Communicate with the Adapter Provides procedures for configuring the 1203-GU6 using a serial connection. Topics include how to set up a serial connection to the 1203-GU6, how to navigate the module s software, edit parameters, perform a flash upgrade to its firmware, and view its event queue. Provides procedures for configuring the 1203-GU6 module or 1336-GM6 board over DeviceNet using RSNetWorx for DeviceNet. Provides procedures for using RSNetWorx for DeviceNet to configure scanners to communicate with devices such as the 1203-GU6 module and 1336-GM6 board. 6 Ladder Logic Programming Provides an example ladder logic program for a PLC and an example ladder logic program for an SLC. 7 Using DeviceNet Explicit Messaging Provides information about explicit messaging, including messaging with PLCs, messaging with SLCs, and using messages to control the SCANport product. 8 Troubleshooting Provides information on the various states of the adapter s LEDs, including Network Status, Module Status, and SCANport Status. A Specifications Provides the specifications for the 1203-GU6 module and 1336-GM6 board. B Enhanced DeviceNet Adapter s Parameters Provides information on the adapter s parameters and how to use them to configure the adapter. C DeviceNet Objects Defines the DeviceNet object classes, class services, and attributes that are supported by the Enhanced DeviceNet adapter. D Supported PCCC Messages Provides a reference list of PCCC messages supported by the Enhanced DeviceNet adapter. E N-File Addresses Lists the N-files to which messages can be written. F Supported Emulated Block Transfer Commands Provides a reference list of emulated block transfer commands. G Event Queue Messages Provides a list of messages you may see in the event queue. Related Publications Title RSNetWorx for DeviceNet Getting Results Manual Publication Number 9398-DNETGR 1771-SDN Scanner Configuration Manual SDN DeviceNet Scanner Configuration Manual DeviceNet Cable System Planning and Installation Manual DN-6.7.2

11 Safety Precautions Using this Manual P-3 Please read the following safety precautions carefully.!!! ATTENTION: Only personnel familiar with SCANport products and associated machinery should plan or implement the installation, start-up, configuration, and subsequent maintenance of the Enhanced DeviceNet communications adapter. Failure to comply may result in personal injury and/or equipment damage. ATTENTION: Remove all power from the SCANport product before installing the 1336-GM6 board. Failure to disconnect power may result in death or serious injury. Verify all power is removed before installing the 1336-GM6 board. ATTENTION: Hazard of equipment damage exists. If explicit messages are programmed to frequently write parameter data to certain drive products, the EEPROM (Non-Volatile Storage) will quickly exceed its life cycle and cause the product to malfunction. Do not create a program that frequently uses explicit messages to write parameter data to a product. Datalinks do not write to the EEPROM and should be used for frequently changed parameters. Terms and Abbreviations For a complete listing of Allen-Bradley terminology, refer to the Allen-Bradley Industrial Automation Glossary, Publication AG-7.1. Terms DeviceNet Enhanced DeviceNet adapter RSNetWorx for DeviceNet SCANport SCANport Peripheral SCANport Product Definition An open network that provides probabilistic I/O control through a managed bit-wise non-destructive multiplexing scheme. Both the 1203-GU6 module and the 1336-GM6 board are enhanced DeviceNet adapters. In this manual, the term adapter is used when both the module and the board are referred to. A Rockwell Software application that can be used to set up DeviceNet networks and configure connected devices. RSNetWorx for DeviceNet (version ) and RSLinx (version ) were used for examples in the manual. Different versions may differ in appearance and procedures. A standard peripheral communications interface for various Allen-Bradley drives and power products. A device that provides an interface between SCANport and a network. It is often referred to as an adapter. For example, the Enhanced DeviceNet adapter is a SCANport peripheral. A device that uses the SCANport communications interface to communicate with one or more peripheral devices. For example, a motor drive such as a 1336 PLUS is a SCANport product.

12 P-4 Using this Manual Conventions Used in this Manual The following conventions are used throughout this manual: Bulleted lists provide information, not procedural steps. Numbered lists provide sequential steps or hierarchical information. Italic type is used for chapter names and for parameter names. Bold type is used for names of menus, menu options, screens, and dialog boxes. Important: This type of paragraph contains tips or notes that have been added to call attention to useful information. Rockwell Automation Support Rockwell Automation offers support services worldwide, with more than 75 sales/support offices, more than 500 authorized distributors, and more than 250 authorized systems integrators located throughout the United States alone. In addition, Rockwell Automation representatives are in every major country in the world. Local Product Support Contact your local Rockwell Automation representative for: Sales and order support. Product technical training. Warranty support. Support service agreements. Technical Product Support If you need to contact Rockwell Automation for technical assistance, please call your local Rockwell Automation representative. Refer to for updates and supporting documentation.

13 Chapter 1 Overview Chapter Objectives Chapter 1 provides an overview of your Enhanced DeviceNet communications adapter. In this chapter, you will read about the following: Function of the 1203-GU6 module or 1336-GM6 board. Features of the 1203-GU6 module and 1336-GM6 board. SCANport products. Parts and hardware of the 1203-GU6 module and 1336-GM6 board. Steps for setting up the adapter. Required tools and equipment. Overview of the Communications Adapter There are two types of Enhanced DeviceNet adapters: the 1203-GU6 module and 1336-GM6 board GU6 Module Figure GU6 Module and 1336-GM6 Board 1336-GM6 Board The 1203-GU6 module mounts on a DIN rail and connects to the SCANport product via a SCANport cable. The 1336-GM6 board is mounted directly onto selected SCANport products so it connects to the SCANport product via an internal SCANport connector.

14 1-2 Overview Both types of Enhanced DeviceNet communications adapter provide an electronic communications interface between a DeviceNet network and any single SCANport product. Figure Example DeviceNet NetWork SMC 1336 PLUS DeviceNet In Figure 1.2, a SCANport cable connects a 1203-GU6 module to a SCANport product through a port on the SCANport product. A DeviceNet cable connects the module to the DeviceNet network. The module then translates the DeviceNet messages into SCANport messages that can be understood by the connected product. Features of the Communications Adapter The DeviceNet network is an open, global industry-standard communication network designed to provide an interface through a single cable from a programmable controller directly to smart devices such as sensors, push buttons, motor starters, simple operator interfaces and drives. The 1203-GU6 module and 1336-GM6 board let you connect your SCANport products to a DeviceNet network. These adapters feature the following: Flash upgradeability allows for field updates in the event of changes to the adapter s firmware. COS (Change of State) capability lets you customize this device s activity on the network by configuring the adapter to report only new data. Cyclic operation lets you customize the devices s activity on the network by configuring the adapter to report its data at specific intervals.

15 Overview 1-3 Peer I/O capabilities let the drive s I/O (logic command, reference, logic status, feedback and datalinks) be broadcast to or received from other drives connected via 1203-GU6 or 1336-GM6 adapters. Software configuration lets you configure the adapter using RSNetWorx for DeviceNet or HyperTerminal (a standard Windows 95 program). Faulted Node Recovery lets you change items, such as a node address, of a device even when it is faulted on the network. (This feature requires the support of proper PC software tools.) User-configurable fault response provides the ability to customize the adapter s actions to communication errors. A miniature RS-232 port on the front of the 1203-GU6 (not available on the 1336-GM6) provides access for your PC to change parameters in the module using HyperTerminal. It also provides a DF1 connection for DriveTools32. (You must configure DriveTools32 and RSLinx for DF1 communications and then connect to the module using a 1203-SFC cable [sold separately].) A new Module Status LED helps to diagnose network, module, and SCANport product health. Re-designed power supply receives its operating power from the connected drive product. Only minimal DeviceNet-side transceiver power is consumed by the user-supplied 24V DC power source.

16 1-4 Overview SCANport Products Some SCANport products support one peripheral; others support up to six peripherals. The table below lists SCANport products, the number of peripherals each supports, the minimum and maximum I/O words, and the type of adapter that can be used. Product Number of Peripherals Supported I/O Words Adapter Use Minimum Maximum 1203-GU GM AC MICRO Drive ➃ Yes No 1336 IMPACT Drive 6 ➀ 0 10 Yes Yes ➁ 1336 PLUS AC Drive 6 ➀ 0 10 Yes Yes ➁ 1336 PLUS II Drive 6 ➀ 0 10 Yes Yes 1336 FORCE Drive 6 ➀ 0 10 Yes Yes ➁➂ 1394 AC Mult-Axis Motion Control System Yes No SMC Dialog Plus Yes No SMP-3 Smart Motor Protector Yes No 1397 Digital DC Drive Yes No 1557 Medium Voltage Drive Yes No ➀ ➁ ➂ ➃ Lower horsepower products may not support a sixth peripheral. Refer to your user manual to verify that your product supports a sixth peripheral. B frame or larger is required. A standard adapter board is required. Early versions of the 1305 drive may not support some communications. Important: To connect multiple peripherals to a SCANport product, a port expander may be required. Refer to your product s documentation for more information. Important: If you intend to use datalinks to communicate with and control your SCANport product, verify that your SCANport product supports datalinks before enabling them in the adapter.

17 Hardware and Parts Description Overview 1-5 The hardware included with the adapter depends on the adapter that you have GU6 Module Hardware Figure 1.3 illustrates and the following table lists the main parts of the 1203-GU6 Enhanced DeviceNet communications module: Figure 1.3 Parts of the 1203-GU6 Module Number Part Description 1 DIN Rail Mount Securely attaches and electronically grounds the module to the DIN rail. 2 SCANport Connection Provides a standard SCANport 8-pin circular mini-din connector for the SCANport cable. 3 RS-232 Serial Port Provides a connection for terminals capable of RS-232 serial communications. This port can be used to edit the module s parameters, download a file needed to perform a flash to the module s operating code, and support devices that monitor and test the module. A 1203-SFC serial cable and a PC running a terminal emulation program or a VT100-compatible terminal are required to use this port. 4 Bi-Color LEDs Indicate the status of the DeviceNet media channel, of the SCANport connection, and of the module. For more information, refer to Chapter 8, Troubleshooting. 5 DeviceNet Connection Provides a 5-pin Phoenix connector to attach the module to the network. Not shown Not shown 5-Pin Plug-In Connector 10-Pin Plug-In Connector This part is supplied with the module. The 5-pin plug-in connector (P/N ) is a connector to attach to the cable. This part is supplied with the module. The 10-pin plug-in connector (P/N ) is a connector to attach to the cable.

18 1-6 Overview 1336-GM6 Board Hardware Figure 1.4 illustrates and the following table lists the main parts of the 1336-GM6 Enhanced DeviceNet communications board: Figure 1.4 Parts of the 1336-GM6 Board 1336-GM6 Board Number Part Description 1 DeviceNet Connection Provides a 5-pin Phoenix connector to attach the module to the DeviceNet network. 2 Bi-Color LEDs Indicate the status of the DeviceNet media channel, of the SCANport connection, and of the module. For more information, refer to Chapter 8, Troubleshooting. 3 SCANport Connection Provides a 14-pin connector containing power and SCANport communication circuitry. Not Shown Kit Provides the necessary materials for mounting the board to the SCANport product. These materials include one grounding wrist strap (P/N ), four Phillips mounting screws (P/N ), four stand-off nylon headers (P/N ), one 5-pin connector (P/N ), and one snap-in comm housing (P/N ) with mounting instructions (P/N ).

19 Overview of Setting Up the Adapter Overview 1-7 To set up the Enhanced DeviceNet adapter, you must perform the following tasks: 1. Install the module or mount the board. Refer to Chapter 2, Installation. 2. Set the adapter s node address and configure the adapter s parameters. Refer to the following table: If using: 1203-GU6 module s serial connection 1203-GU6 module s DeviceNet connection 1336-GM board Then refer to: Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet 3. Configure a scanner (either PLC or SLC) to communicate with the Adapter. Refer to Chapter 5, Configuring a Scanner to Communicate with the Adapter. 4. If necessary, create a ladder logic program to control the SCANport product. Refer to Chapter 6, Ladder Logic Programming. Required Tools and Equipment The tools and equipment required, depend on if you are using a 1203-GU6 module or 1336-GM6 board GU6 Module To install and configure a 1203-GU6 module, you need the following: Enhanced DeviceNet communications module (1203-GU6). 5-pin or 10-pin plug-in connector (supplied with module). 35 x 7.5 mm DIN rail A (Allen-Bradley part number 199-DR1; ; EN 50022). 1/8" flathead screwdriver. Appropriate cables for SCANport and DeviceNet connections. Refer to the Selecting Cables section in Chapter 2, Installation. A 1203-SFC serial cable. A PC running either a Windows terminal emulation program (e.g., HyperTerminal) or a VT100-compatible terminal.

20 1-8 Overview A PC that is: Running RSNetWorx for DeviceNet. Connected to and communicating with the DeviceNet network using a 1784-PCD card or a 1770-KFD adapter. Running RS Linx. Running RSLogix5 (if using PLC) or RSLogix500 (if using SLC). Important: Refer to for more information on these software products GM6 Board To install and configure a 1336-GM6 board, you need the following: Enhanced DeviceNet communications board (1336-GM6). A kit that includes one grounding wrist strap, four Phillips mounting screws, four stand-off nylon headers, one 5-pin connector and one snap-in comm housing with mounting instructions (supplied with board). #1 Phillips screwdriver. Appropriate cable for the DeviceNet connection. Refer to the Selecting Cables section in Chapter 2, Installation. A PC that is: Running RSNetWorx for DeviceNet. Connected to and communicating with the DeviceNet network using a 1784-PCD card or a 1770-KFD adapter. Running RS Linx. Running RSLogix5 (if using PLC) or RSLogix500 (if using SLC). Important: Refer to for more information on these software products.

21 Chapter 2 Installation Chapter Objectives Chapter 2 provides the information that you need to install the 1203-GU6 module or 1336-GM6 board. In this chapter, you will read about the following: Required tools and equipment. Selecting cables. Installing the adapter. Removing the adapter. How you install the adapter depends on whether you are installing a 1203-GU6 module or 1336-GM6 board. Refer to the following table for information: If installing: Then refer to: 1203-GU6 module Installing a 1203-GU6 Module on page GM6 board Installing a 1336-GM6 Board on page 6 Installing a 1203-GU6 Module Follow these procedures to install a 1203-GU6 module. Required Tools and Equipment To install your 1203-GU6 module, you will need the following tools and equipment: Enhanced DeviceNet communications module (1203-GU6). Either a 5-pin or 10-pin plug-in connector (supplied with module). 35 x 7.5 mm DIN rail A (Allen-Bradley part number 199-DR1; ; EN 50022). 1/8" flathead screwdriver. Appropriate cables for SCANport and DeviceNet connections. Refer to the Selecting Cables section in this chapter. Selecting Cables To connect the 1203-GU6 to the SCANport product and the DeviceNet network, you must select an appropriate DeviceNet cable and Allen-Bradley SCANport cable. Use the following information to select appropriate cables for each connection.

22 2-2 Installation SCANport Cables When selecting the SCANport cable to connect the 1203-GU6 module to the SCANport product, you need to: Use an Allen-Bradley SCANport cable. Refer to the table below. Male to Male Connection Male to Female Connection Length Catalog Number Length Catalog Number 1/3 m 1202-C03 1/3 m 1202-H03 1 m 1202-C10 1 m 1202-H10 3 m 1202-C30 3 m 1202-H30 9 m 1202-C90 9 m 1202-H90 Use less than 10 meters (33 feet) of cable between the SCANport product and adapter. Keep SCANport cables away from high power cables to guard against introducing noise into your system. DeviceNet Cables The 1203-GU6 module comes with either one 5-pin connector or a 5-pin and 10-pin connector. A drop line connects a node, such as an adapter, on the DeviceNet cable system to the DeviceNet trunk. When selecting a drop line, you need to: Select either a 5-pin connector or a 10-pin connector for the cable. (Both are included with the 1203-GU6 module). Use the 5-pin connector if you are using a DeviceNet drop cable configuration. Use the 10-pin connector if you are using a daisy-chaining configuration. Determine limitations of the trunk and drop cables. Refer to the following table. Data Rates 125 Kbps 250 Kbps 500 Kbps Thick Trunk Line 500 m (1,640 ft) 250 m (820 ft) 100 m (328 ft) Thin Trunk Lengths 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 Budget 156 m (512 ft) 78 m (256 ft) 39 m (128 ft) For more information on DeviceNet cables and cable systems, refer to the DeviceNet Cable System Planning and Installation Manual, Publication DN

23 Installing the 1203-GU6 Communications Module Installation 2-3 The following instructions explain how to physically install your Enhanced DeviceNet 1203-GU6 communications module. 1. Hook the top lip of the module s DIN rail mount onto the top of the DIN rail and then rotate the module onto the DIN rail. You will hear the module snap into a locked position. Figure 2.1 Mounting the Module onto the DIN Rail 2. Remove power from the network. 3. Insert the DeviceNet cable wires into the desired connector. Make sure you follow the color key next to the connector receptacle on the module.! ATTENTION: If you wire the 5-pin or 10-pin header after you ve connected it to the module, static control precautions are required. Device malfunction may occur if you do not follow ESD control procedures. If you are not familiar with static control procedures, refer to Allen-Bradley Publication , Guarding Against Electrostatic Damage, or other applicable ESD protection handbook. Figure 2.2 Inserting DeviceNet Cable Wires into the Connector SP Mod Net SCANport Color Key Serial 1-Red- V+ 2-White-CAN_H 3-Shield 4-Blue-CAN_L 5-Black- V- DeviceNet Allen-Bradley

24 2-4 Installation 4. Plug the connector into the module. Figure 2.3 Inserting a 5-pin or 10-pin Phoenix Connector 5. Use a 1/8" flathead screwdriver to screw the connector firmly into place. 6. Connect the SCANport cable to the communications adapter and then to the SCANport product. Important: Because the adapter s power comes from the SCANport product, the adapter will not function if the SCANport product is not powered. Figure 2.4 Inserting the SCANport Cable 7. Reapply power to the network. 8. If necessary, apply power to the connected SCANport product. Your 1203-GU6 module is now installed. The SCANport LED is green. The network and module LEDs are blinking green. If your module s LEDs are different, refer to Chapter 8, Troubleshooting, for more information.

25 Installation 2-5 You must now edit the adapter s node address, and you may want to edit some of its other parameters. Refer to the following table for information: If using: 1203-GU6 module s serial connection 1203-GU6 module s DeviceNet connection Then refer to: Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Removing the 1203-GU6 Communications Module To remove the 1203-GU6 communications module, you need to: 1. If necessary, remove any serial connections from the DF-1 serial port. 2. Remove the SCANport cable from the SCANport product and then from the module. This will power down the module if the SCANport product is powered. 3. Unscrew (using a 1/8" flathead screwdriver) and then unplug the 5-pin or 10-pin connector from the module. 4. Insert a flathead screwdriver into the module s DIN rail tab release and gently push the handle toward the module to release the connection tab. Then pull the module up and off the DIN rail. Figure 2.5 Removing the Module from the DIN Rail

26 2-6 Installation Installing a 1336-GM6 Board Follow these procedures to install a 1336-GM6 board. Required Tools and Equipment To install your 1336-GM6 board, you will need the following tools and equipment: Enhanced DeviceNet communications board (1336-GM6). A kit that includes one grounding wrist strap, four Phillips mounting screws, four stand-off nylon headers, one 5-pin connector and one snap-in comm housing with mounting instructions (supplied with board). #1 Phillips screwdriver. Appropriate cable for the DeviceNet connection. Refer to the Selecting Cables section below. Selecting Cables To connect the Enhanced DeviceNet adapter to the SCANport product and the DeviceNet network, you must select an appropriate DeviceNet cable. Use the following information to select appropriate cables for each connection. DeviceNet Cables The 1336-GM6 board comes with one 5-pin connector. A drop line connects a node, such as an adapter, on the DeviceNet cable system to the DeviceNet trunk. When selecting a drop line, you need to: Use the 5-pin connector for the cable if you are using a DeviceNet drop cable configuration. Determine limitations of the trunk and drop cables. Refer to the following table. Data Rates 125 Kbps 250 Kbps 500 Kbps Thick Trunk Line 500 m (1,640 ft) 250 m (820 ft) 100 m (328 ft) Thin Trunk Lengths 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 Budget 156 m (512 ft) 78 m (256 ft) 39 m (128 ft) For more information on DeviceNet cables and cable systems, refer to the DeviceNet Cable System Planning and Installation Manual, Publication DN

27 Electrostatic Discharge Precautions Installation 2-7 Please read the following safety precaution carefully before installing the 1336-GM6 communications board.! ATTENTION: The 1336-GM6 communications board contains ESD (Electrostatic Discharge) sensitive parts. Static control precautions are required when installing, testing, or servicing this board. Device malfunction may occur if you do not follow ESD control procedures. If you are not familiar with static control procedures, refer to Allen-Bradley Publication , Guarding Against Electrostatic Damage,or other applicable ESD protection handbook. Installing the 1336-GM6 Communications Board The following instructions explain how to physically install an Enhanced DeviceNet 1336-GM6 communications board. Important: If you are attaching the communications board to a 1336 PLUS II, refer to the one-page insert included with the kit for mounting instructions. Important: To prevent damage to the board, you must wear a grounding wrist strap when handling the 1336-GM6 communications board.! ATTENTION: Remove all power from the SCANport product before installing the 1336-GM6 board. Failure to disconnect power may result in death or serious injury. Verify all power is removed before installing the 1336-GM6 board. 1. Make sure you ve turned off the power supply to the SCANport product and DeviceNet network and verified the drive is not receiving power.

28 2-8 Installation 2. Screw the four stand-off nylon headers into the appropriate spaces on the drive s main control board. Figure 2.6 Mounting the Open Style Communications Board DeviceNet Connector Black - V - Blue - CAN_L Bare - Shield White - CAN_H Red - V+ DeviceNet Status Module Status SCANport Status Internal SCANport Connector 3. Insert the pins located on the 1336-GM6 into the 14-pin SCANport header on the drive. The board should sit squarely on the stand-offs. 4. Using a #1 Phillips screwdriver and the four supplied mounting screws, screw the board securely into place, being careful not to overtighten. 5. Attach the wires to the supplied DeviceNet connector. Important: Refer to Figure 2.6 to verify you ve wired the connector correctly to the board. Failure to wire the board correctly may damage the circuitry or cause the device to not function.! ATTENTION: Static control precautions are required if you wire the connector when it is already connected to the adapter. It is not recommended that you do this. Device malfunction may occur if you do not follow ESD control procedures. If you are not familiar with static control procedures, refer to Allen-Bradley Publication , Guarding Against Electrostatic Damage,or other applicable ESD protection handbooks. 6. Plug the connector into the board receptacle and screw the two screws into place using a 1/8" flathead screwdriver.

29 7. Reapply power to the SCANport product. 8. Reapply power to the DeviceNet network. Installation 2-9 Your 1336-GM6 board is now installed. The SCANport LED is green. The network and module LEDs are blinking green. If your module s LEDs are different, refer to Chapter 8, Troubleshooting, for more information. You must now edit the adapter s node address, and you may want to edit some of its other parameters. Refer to Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet. Removing the 1336-GM6 Communications Board To remove the 1336-GM6 communications board, you need to: Important: To prevent damage to the board, you must wear a grounding wrist strap when handling the 1336-GM6 communications board. Important: If you are removing the communications board from a 1336 PLUS II, refer to the one-page insert included with the kit for special mounting instructions.! ATTENTION: Remove all power from the SCANport product before removing the 1336-GM6 board. Failure to disconnect power may result in death or serious injury. Verify all power is removed before installing the 1336-GM6 board. 1. Turn off the power supply to the drive and DeviceNet network. 2. Unscrew (using a 1/8" flathead screwdriver) and then unplug the DeviceNet connector from the communications board. 3. Unscrew and remove the board s four mounting screws with a #1 Phillips screwdriver. 4. Making sure not to bend the pins as they slide out of the 14-pin SCANport header, gently pull the communications board away from the main control board. 5. Unscrew and remove the four stand-offs from the main control board.

30 2-10 Installation Notes:

31 Chapter 3 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Chapter Objectives Chapter 3 provides information that you need to configure the 1203-GU6 module using a serial connection. In this chapter, you will read about the following: Factory-default settings for the module. Equipment necessary to make a serial connection to the 1203-GU6 module. Connecting either a PC running terminal emulation software or VT100-compatible terminal to the 1203-GU6 module. Using HyperTerminal to configure or edit the module s parameters, display its event queue, view its I/O data, view DF-1 statistics or serial number, and perform a flash upgrade. Important: DriveExplorer can also be used to configure the adapter via its serial port. Refer to the DriveExplorer documentation from more information. To configure a 1203-GU6 module over the DeviceNet network or to configure a 1336-GM6 board, refer to Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet. Factory Default Settings for the 1203-GU6 Module The factory-default settings of the Enhanced DeviceNet adapter include the following: 16-bit Logic Command/Status enabled for polling. 16-bit Reference/Feedback enabled for polling. If the scanner is put into program mode or the network fails, the SCANport product will be faulted by the module. A node address of 63. DeviceNet autobaud detection enabled. Serial baud rate of 9600.

32 3-2 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection You should change the node address by editing the DN Node Address (2) parameter. You must change the autobaud detection if no other devices on your DeviceNet network have a fixed data rate by editing DN Data Rate (3) parameter in the module. Important: Refer to Appendix B, Enhanced DeviceNet Adapter s Parameters, for more information on changing the node address or data rate. If you wish to change other functions (e.g., Fault Configurable inputs) or add more functions (e.g., datalinks), you must edit the adapter s parameters. To do so, refer to: Appendix B, Enhanced DeviceNet Adapter s Parameters, for detailed information about the adapter s parameters. Instructions in this chapter on establishing a serial connection. Instructions in this chapter on editing parameters. Required Tools and Equipment To make a serial connection to the module, you need the following: A 1203-SFC serial cable. Either PC running a terminal emulation program (e.g., HyperTerminal) or a VT100-compatible terminal. Establishing a Serial Connection to the Module The 1203-GU6 module s software lets you do the following: Edit its parameters. View its event queue. View its I/O data values. View DF1 statistics. View its serial number. Perform a flash upgrade. To access this software, you must make a serial connection to the module from a PC running terminal emulation software or from a VT100-compatible terminal. Refer to the following table: If using: Refer to page: PC running terminal emulation software 3-3 VT100-compatible terminal 3-8

33 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3-3 Using a PC Running Terminal Emulation Software A variety of terminal emulation programs can be used to establish a serial connection to the module. The following instructions describe how to establish the initial serial connection to the module using a PC running HyperTerminal software. Future connections to the module can use this same configuration by clicking the icon added to the initial screen when the configuration is saved. Important: The following procedures use HyperTerminal on a computer running Windows 95. If you are not using HyperTerminal or if you are using HyperTerminal on Windows NT, steps to establish a serial connection and screens may differ from the following steps and screens. 1. Connect a 1203-SFC serial cable to your PC s RS-232 serial port and then to the serial port on the module. Figure 3.1 Connecting the 1203-SFC Serial Cable to the Serial Port

34 3-4 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 2. In Windows 95, click the Start button and then select Programs, Accessories, and HyperTerminal. Important: A HyperTerminal dialog box appears in either List or Icon mode. Figure 3.2 shows the dialog box in List mode. To change from Icon mode to List mode, select View, then List. Figure 3.2 Example HyperTerminal Dialog Box 3. Double-click HyperTrm.exe. The Connection Description dialog box appears. Figure 3.3 Example Connection Dialog Box 4. Enter a name in the Name field and select any icon from the Icon field.

35 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Click OK. The Phone Number dialog box appears. Figure 3.4 Example Phone Number Dialog Box 6. In the Connect Using field, select the appropriate communications port (usually COM1 or COM2). 7. Click OK. The Comm Properties dialog box appears. Figure 3.5 Example Comm Properties Dialog Box

36 3-6 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 8. Select the following settings: 9600 in the Bits per second field. If you have previously set the module s Serial Port Rate parameter to enable bps, set the bps to in this field. 8 in the Data bits field. None in the Parity field. 1 in the Stop bits field. None in the Flow control field. 9. Click OK. The HyperTerminal screen appears. 10. From the File menu, select Properties. The Properties dialog box appears. Figure 3.6 Properties Dialog Box 11. Click the Settings tab. 12. In the Function, arrow, and ctrl keys act as field, verify Terminal keys is selected. 13. In the Emulation field, verify VT100 is selected. 14. Click OK.

37 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection From the File menu, select Save. The configuration is saved and the icon you selected will appear in the HyperTerminal window the next time you make a connection to the module. 16. Press the Enter key. The main menu of the Enhanced DeviceNet application appears. Figure 3.7 Main Menu

38 3-8 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Using a VT100-Compatible Terminal The following instructions describe how to establish a serial connection to the module using a VT100-compatible terminal. 1. Connect a 1203-SFC serial cable to your terminal and then to the serial port on the module. See Figure Start your terminal. 3. Select the following settings: 9600 in the Bits per second field. If you ve already set the module s Serial Port Rate parameter to enable bps, set the bps to in this field. 8 in the Data bits field. None in the Parity field. 1 in the Stop bits field. None in the Flow Control field. 4. Press the Enter key. The main menu of the Enhanced DeviceNet application appears. Figure 3.8 Main Menu

39 Navigation Techniques Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3-9 To perform any of the functions of the module s software (e.g., editing parameters), you need to know the following navigation techniques: Press: To 1, 2, 3, 4, 5, 6, 7, 8, 9, 0 Select an option in the Main Menu (1 6) or enter a value for a parameter in the parameter screen (0 9). Escape Down Arrow Up Arrow Right Arrow Left Arrow Enter Return to Main Menu or abort changes to a parameter. View the next parameter. View the previous parameter. View the next value for a parameter. ➀ View the previous value for a parameter. ➀ Save a value for a parameter. ➀ In some parameters the right and left arrow keys let you navigate through the bits. Editing the Module s Parameters If you do not want to use the module s default settings, you must edit its parameters. Refer to Appendix B, Enhanced DeviceNet Adapter s Parameters, for a detailed list of parameters and how to configure them. 1. Establish a serial connection to access the module s software. Refer to the Establishing a Serial Connection to the Module section earlier in this chapter.

40 3-10 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 2. Press 1 to select 1> Edit Setup Parameters. The first parameter appears on the bottom of the screen. Figure 3.9 Edit Parameters 3. If necessary, scroll through the list of parameters by pressing the Up arrow key or Down arrow key. 4. Edit parameters as necessary using the left arrow and right arrow keys. Refer to the Navigation Techniques section earlier in this chapter for information on changing parameter values. Refer to Appendix B, Enhanced DeviceNet Adapter s Parameters, for acceptable values for each parameter. 5. If necessary, reset the module by enabling the Reset Adapter parameter (22). Refer to Appendix B, Enhanced DeviceNet Adapter s Parameters, to see if the parameter you changed requires the module to be reset in order to take effect. Displaying and Clearing the Module s Event Queue If an unexpected problem occurs with the module, you may need to check the event queue to view events that have happened in the module. Follow these instructions: 1. Establish a serial connection to access the module s software. Refer to the Establishing a Serial Connection to the Module section earlier in this chapter.

41 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Press 2 to select 2> Display Event Queue. The event queue appears. Figure 3.10 The Event Queue 3. Scroll through the list of Event Queue parameters by pressing the Up Arrow or Down Arrow key. Refer to Appendix G, Event Queue Messages, for a list of faults. Number Name Description 1 Clr Event Queue Enable = Clears the event queue. Ready = Leaves the event queue as is. 2 7 Event Queue 1 Event Queue 6 Event in the event queue. Most recent event is listed in Event Queue 1. 8 Flash Upgrades Number of times the adapter has been flash upgraded. 4. If desired, clear the current fault in the adapter by setting Clr Event Queue (1) to Enable and pressing the Enter key. Important: The Fault is cleared in the module and a Clear Fault event is added to the Event Queue. 5. Press the Escape key to return to the main menu.

42 3-12 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Viewing I/O Data Values If you need to verify that a command you ve sent to a drive is actually passing through the module or to diagnose similar I/O concerns, you can view the I/O data values. To view I/O data values, follow these instructions: Important: You must understand the configuration of the SCANport product to interpret the I/O data values. 1. Establish a serial connection to access the module s software. Refer to the Establishing a Serial Connection to the Module section earlier in this chapter. 2. Press 3 to select 3> Display I/O Data Values. The I/O Data Screen appears. Figure 3.11 I/O Data Values 3. Scroll through the list of I/O Data parameters by pressing the Up Arrow or Down Arrow key. Number Name Description 1 Logic Command Buffer for Logic Command data 2 Logic Status Buffer for Logic Status data 3 Reference Data Buffer for Reference data 4 Feedback Data Buffer for Feedback data 5 20 Data A1 In Val Data D2 Out Val Data going to (Input) or coming from (Output) the SCANport device 4. Press Escape to return to the Main Menu.

43 Viewing DF-1 Statistics Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3-13 If you want to check for bad packets or perform other serial port debugging procedures, you can view DF-1 statistics. You may also want to use the DF-1 statistics if you are developing your own DF-1 driver. To view DF-1 statistics, follow these instructions: 1. Establish a serial connection to access the module s software. Refer to the Establishing a Serial Connection to the Module section earlier in this chapter. 2. Press 4 to select 4> Display DF1 Statistics. The first parameter appears. Figure 3.12 DF1 Statistics

44 3-14 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3. Scroll through the list of DF1 Statistics by pressing the Up Arrow or Down Arrow key. Number Name Description 1 Clear DF1 Counts Ready = Leaves status parameters as they are Enable = Reset all status parameters 2 DF1 Packets Sent Total number of DF1 packets sent by the module 3 DF1 Packets Rcvd Total number of DF1 packets received by the module 4 Undelivered Msgs Total number of messages sent that were not acknowledged 5 ENQ Sent Total number of inquiries sent by the module 6 ENQ Rcvd Total number of inquiries received by the module 7 NAKs Received Total number of NAKs received by the module 8 NAK Bad Packet Total number of NAKs sent by the module because of corrupt data 9 NAK No Memory Total number of NAKs sent by the module because the previous command did not yet complete and there was no place to save the new command 10 Duplicate Msgs Total number of messages received by the module with the same TNS number as the previous message 4. If desired, reset the current DF1 protocol statistics by setting Clear DF1 Counts to Enable and pressing the Enter key. 5. Press Escape to return to the Main Menu. Viewing Your Module s Serial Number Each Enhanced DeviceNet module has a unique serial number. To view the serial number, follow these instructions: 1. Establish a serial connection to access the module s software. Refer to the Establishing a Serial Connection to the Module section earlier in this chapter. 2. Press 5 to select 5> Display Serial Number. The serial number for your communications module appears. 3. Press Escape to return to the Main Menu.

45 Performing a Flash Upgrade to the Module Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3-15 You can upgrade the Enhanced DeviceNet adapter s firmware using the module s serial port. To ensure a successful flash, we recommend the following: If using a laptop, turn off the FIFO buffers in HyperTerminal. In Windows 95, select File and then Properties. In the Properties dialog box, click Configure and then click Advanced. Uncheck Use FIFO buffers. Flash the upgrade file from a local hard disk (not a network drive or floppy disk). Run only your terminal emulation software while performing the flash. Disable the screen saver. Important: To perform a flash upgrade to your module s firmware through the serial port, you must use a PC running terminal emulation software that supports an X-modem CRC binary transfer. Important: When you request a flash upgrade, the SCANport product may fault and stop. To exit the flash upgrade option before the download has completed, simultaneously press the Control and X keys. To perform a flash upgrade, you need to: 1. Establish a serial connection to access the module s software. Refer to the Establishing a Serial Connection to the Module section earlier in this chapter. 2. Obtain the software file that contains the upgrade and record its location. Note the firmware/revision number above the Main Menu options in order to verify the upgrade later.

46 3-16 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3. Press 6 to select 6> Update Flash Program. The following screen appears in terminal mode.! ATTENTION: Hazard of personal injury or death exists when stopping a drive to perform a flash upgrade. When you perform a flash upgrade, the drive will fault and stop the motor if the drive is receiving control data from the 1203-GU6 module. Make sure the motor will stop safely or the drive will receive control data from an alternate source before beginning a flash upgrade. Figure 3.13 Initial Update Flash Program Screen

47 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Press Y to verify that you want to perform a flash upgrade when prompted. 5. From the Transfer menu, select Send File. The Send File dialog box appears. Figure 3.14 Send File Dialog Box 6. In the Filename field, select the file that contains the flash upgrade. Important: You can click the Browse button to locate the file that contains the flash upgrade. 7. In the Protocol field, select Xmodem. 8. Click Send. A dialog box appears to report the flash is in progress. Figure 3.15 Flash In Progress Dialog Box

48 3-18 Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection When the flash is complete, a message appears to tell you the download is complete. Figure 3.16 Message Reporting the Flash is Complete 9. Press Enter to return to the main menu. 10. Verify that the new main menu displays the new revision data.

49 Chapter 4 Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Chapter Objectives Chapter 4 provides information that you need to configure the 1203-GU6 module or 1336-GM6 board over the DeviceNet network. In this chapter, you will read about the following: RSNetWorx for DeviceNet software. Equipment necessary to use RSNetWorx for DeviceNet software. Editing the 1203-GU6 or 1336-GM6 adapter s parameters using RSNetWorx for DeviceNet. Important: You must use RSNetWorx for DeviceNet to configure the 1336-GM6 board. The 1203-GU6 module can be configured using RSNetWorx for DeviceNet, DriveExplorer, or terminal emulation software (Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection). Important: Refer to Appendix B, Enhanced DeviceNet Adapter s Parameters, for information on changing the node address or data rate. What is RSNetWorx for DeviceNet? RSNetWorx for DeviceNet is a Rockwell Software application that can be used to set up DeviceNet networks and configure connected devices. RSNetWorx for DeviceNet (version ) and RSLinx (version ) were used for examples in the manual. Different versions may differ in appearance and procedures. After installing or mounting the adapter, you can use RSNetWorx for DeviceNet to configure or edit the adapter s parameters. Required Equipment and Software Before configuring or editing your adapter s parameters, your PC must be: Running RSNetWorx for DeviceNet. Refer to for more information on this product. Connected to and communicating with the DeviceNet network using a DeviceNet interface such as a 1784-PCD card or a 1770-KFD adapter.

50 4-2 Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Going Online To use RSNetWorx for DeviceNet, you must first set up a driver in RSLinx. The driver provides a communications link between the computer and DeviceNet network. Then, you can view the devices on a DeviceNet network by going online. A device may appear as an unrecognized device if RSNetWorx for DeviceNet does not have an EDS file for it. 1. Start RSLinx, and select Communications > Configure Drivers to display the Configure Drivers dialog box. Figure 4.1 Configure Drivers Dialog Box 2. In the Available Driver Types box, select DeviceNet Drivers, and then click Add New. The DeviceNet Driver Selection dialog box appears. Figure 4.2 DeviceNet Driver Selection Dialog Box 3. In the Available DeviceNet Drivers list, select the adapter connected to your computer, and then click Select. A Driver Configuration dialog box appears. 4. Configure the driver for your computer and network settings, and then click OK. The Configure Drivers dialog box reports the progress of the configuration. The Add New RSLinx Driver dialog box appears. Figure 4.3 Add New RSLinx Driver Dialog Box

51 Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Type a name (if desired), and then click OK. The Configure Drivers dialog box reappears, and the new driver is in the Configured Drivers List Figure 4.4 Configure Drivers Dialog Box with a DeviceNet Driver 6. Click Close to close the dialog box. Leave RSLinx running. 7. Start RSNetWorx for DeviceNet, and then select Network > Online. If the Browse for Network dialog box appears, RSLinx has drivers for multiple networks. Select your DeviceNet network, and click OK. A message appears. Figure 4.5 DeviceNet Configuration Services Message 8. Click OK to go online. The devices in the network appear in the Configuration view. Figure 4.6 Online in RSNetWorx for DeviceNet

52 4-4 Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Creating an EDS File If the adapter and SCANport product appear as an unrecognized device, create an EDS file. 1. Right-click the Unrecognized Device icon (for example, node 63 in Figure 4.6), and select Register Device in the menu. The EDS Installation wizard appears. Figure 4.7 EDS Wizard 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 and Output Size boxes, and then click Next. RSNetWorx will upload the EDS file from the product and adapter. 6. Click Next to select an icon for the node. We recommend that you use the icon for your product. You can change icons by clicking Change icon. 7. Click Next to view a summary, and then click Next again to accept it. 8. Click Finish to finish the EDS creation. A new icon represents the SCANport product and adapter in the Configuration View.

53 Accessing and Editing Parameters Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet 4-5 Parameters in the SCANport product and adapter can be edited with RSNetWorx. The adapter parameters are appended to the list of product parameters. In Figure 4.8, for example, the drive has 323 parameters, so parameter 324 is the first adapter parameter. 1. After creating an EDS file, right-click on the icon for the SCANport product and adapter and select Properties. The Device Edit dialog box appears. 2. Click the Device Parameters tab. If an EDS Editor message appears, click Upload to load the parameter values in the product to the computer. Figure 4.8 Device Parameters Page in the Edit Dialog Box Parameters are displayed in numerical order under Parameter. Parameters for the DeviceNet adapter are appended to the end of the parameter list for the SCANport product. You can either scroll through the list or select a specific group of parameters in the Groups box (for example, DeviceNet Module). The available groups and the numbers of the adapter parameters will vary based on the type of product that is connected to the adapter. 3. In the Current Value column, double-click a value to edit it.

54 4-6 Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Notes:

55 ESC SEL JOG Chapter 5 Configuring a Scanner to Communicate with the Adapter Chapter Objectives Chapter 5 provides instructions for configuring your scanner to communicate with either the 1203-GU6 module or 1336-GM6 board. This allows the product connected to the adapter to be an active node on the DeviceNet network. In this chapter, you will read about the following: Equipment and software needed for the configuration. Configuring a PLC or SLC scanner to communicate with the adapter. Required Equipment and Software Before configuring the scanner, your PC must be: Running RSNetWorx for DeviceNet. Refer to for more information. Connected to and communicating with the DeviceNet network using a DeviceNet interface such as a 1784-PCD card or a 1770-KFD adapter. Example DeviceNet Network After the adapter is configured, it and the connected product will be a single node on the network. This chapter provides the steps that are needed to configure a simple network like the network in Figure 5.1. Figure 5.1 Example DeviceNet Network Node 0 SLC 500 Controller with 1747-SDN Scanner Node 62 Computer with 1770-KFD and RSNetWorx for DeviceNet Node PLUS II Drive with 1203-GU6 DeviceNet Adapter

56 5-2 Configuring a Scanner to Communicate with the Adapter Setting Up the Scan List For the scanner to communicate with a product, the scanner must be configured and the product s node number must be added to its scan list. 1. Go online with RSNetWorx for DeviceNet. Refer to the Going Online section in Chapter Select Network > Single Browse Path. The devices on the network are displayed in the configuration view. Figure 5.2 Configuration View (Graph) 3. Right-click the DeviceNet scanner (node 00 in Figure 5.2) and select Properties. The Scanner Module dialog box appears. Important: If your scanner is an unrecognized device, you must create an EDS file for it and then configure it. Create an EDS file by following the instructions in the Creating an EDS File section in Chapter 4. Configure the scanner using the General and Module tabs. Click Help or refer to your scanner documentation if you need more information. 4. Click the Scanlist tab. A message box prompts you to upload. 5. Click Upload. Data is uploaded from the scanner, and then the Scanlist page appears.

57 Configuring a Scanner to Communicate with the Adapter 5-3 Figure 5.3 Scanlist Page in the Device Edit Dialog Box 6. Select the Automap on Add box (a check mark will appear). 7. Under Available Devices, select the SCANport product, and then click > (Right Arrow) to add it to the scanlist. Figure 5.4 Scanlist Page in the Scanner Module Dialog Box 8. Under Scanlist, select the SCANport product, and then click Edit I/O Parameters. The Edit I/O Parameters dialog box appears.

58 5-4 Configuring a Scanner to Communicate with the Adapter Figure 5.5 Edit I/O Parameters Dialog Box 9. Select the type(s) of data exchange (Polled, Change of State, and/or Cyclic). In our example, we selected Polled. 10. Type the number of bytes that will be required for your I/O in the Rx Size and Tx Size. The size will depend on the I/O that you enabled in the adapter. The I/O is set using the Cmd/Stat Config (Parameter 4) and the Datalink x Cfg (Parameters 5 8) in the adapter. In our example, we typed 4 in the Rx Size and Tx Size boxes because we have enabled only the Cmd/Stat Config (Parameter 4) for I/O in the adapter. In the Output image, our product uses one 16-bit word for the logic command and one 16-bit word for the reference. A 16-bit word is two bytes. In the Input image, our product uses one 16-bit word for logic status and one 16-bit word for feedback. Therefore, the logic command/status uses 2 bytes and the reference/feedback uses 2 bytes, totaling 4 bytes. 11. Set the scan rate: Data Exchange Polled Change of State Cyclic Rate to set Polled Rate Heartbeat Rate Send Rate Click Help for more information. 12. Click OK. If you changed any settings, a Scanner Applet appears and asks if it is OK to unmap the I/O. Click Yes to continue. The Edit I/O Parameters dialog box closes and then the Scanner Module dialog box (Figure 5.4) reappears. You will map the I/O in the next section in this chapter.

59 Configuring a Scanner to Communicate with the Adapter 5-5 Mapping the Product s Data in the Scanner Data from I/O messages must be mapped in the scanner. This mapping determines where a ladder logic program can find data transmitted on the network. You must map the following: For: Refer to: Mapping the Input I/O page 5-5 Mapping the Output I/O page 5-6 Mapping the Input I/O 1. In the Scanner Module dialog box, click the Input tab. (If you need to display this dialog box, right-click the scanner in the configuration view. See Figure 5.2.) Figure 5.6 Input Page on the Scanner Module Dialog Box If you selected the Automap on Add box (Figure 5.3) in the Scanlist page (Figure 5.4) and did not change any settings, RSNetWorx has already mapped the I/O. If I/O is not mapped, click AutoMap to map it. If you need to change the mapping, click Advanced and change the settings. Click Help for assistance. 2. In the Memory box, select a location in scanner memory. Scanner Memory Locations 1747-SDN Discrete or M-File 1771-SDN Block Xfer 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 data should start. In our example, it is 1.

60 5-6 Configuring a Scanner to Communicate with the Adapter Mapping the Output I/O 1. In the Scanner Module dialog box, click the Output tab. (To display this dialog box, right-click the scanner in the configuration view. See Figure 5.2.) Figure 5.7 Output Page on the Scanner Module Dialog Box If you selected the Automap on Add box (Figure 5.3) in the Scanlist page (Figure 5.4) and did not change any settings, RSNetWorx has already mapped the I/O. If I/O is not mapped, click AutoMap to map it. If you need to change the mapping, click Advanced and change the settings. Click Help for assistance. 2. In the Memory box, select a location in scanner memory. Scanner Memory Locations 1747-SDN Discrete or M-File 1771-SDN Block Xfer 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 data should start. In our example, we selected 1.

61 Saving the Configuration Configuring a Scanner to Communicate with the Adapter 5-7 After configuring a scanner, you must download it to the scanner. You should also save it to a file on your computer. 1. In the Scanner Module dialog box, click Apply to save the configuration to the scanner. A Scanner Configuration Applet appears and asks if it is OK to download the changes. 2. Click Yes to download the changes. The changes are downloaded and 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 file name, and click Save to save the configuration to a file.

62 5-8 Configuring a Scanner to Communicate with the Adapter Notes:

63 Chapter 6 Ladder Logic Programming Chapter Objectives Chapter 6 provides information needed to create the PLC or SLC Ladder Logic program that the controller will use to transmit control I/O and messages to and from the SCANport product. In this chapter, you will read about the following: Equipment and software needed to create either a PLC or SLC ladder logic program. PLC and SLC ladder logic programs. Creating a PLC or SLC ladder logic program. Example PLC and SLC ladder logic programs to control the drive. This chapter assumes you are familiar with the hardware components and programming procedures necessary to operate DeviceNet and SCANport devices, including the following: PLC-5 or SLC-5/ SDN or 1747-SDN scanner. Ladder programming. RSLogix5 or RSLogix500. You may need to refer to the documentation associated with these products to create a ladder logic program. Required Equipment Before creating a ladder logic program for the PLC or SLC, your PC must be: Running RSLogix5 and RSLinx if using a PLC. Refer to for more information on these products. Running RSLogix500 and RSLinx if using an SLC. Refer to for more information on these products. Connected to and communicating with the controller. What is RSLogix? RSLogix5 (for the PLC-5) and RSLogix500 (for the SLC-5/03) software let you create the ladder logic programs you need and download them to the PLC or SLC. They also let you monitor the program as the PLC or SLC is using it.

64 6-2 Ladder Logic Programming What are Ladder Logic Programs? For more information on RSLogix5 or RSLogix500, consult the respective software s documentation. A PLC or SLC ladder logic program lets you control the drive and the messaging from the PLC or SLC to the drive. Figure 6.1 shows how the I/O image table for a DeviceNet scanner relates to a drive, such as a 1336 PLUS drive, when an Enhanced DeviceNet communications adapter is used. Note that the location of the first word (n) depends on the I/O mapping. Figure 6.1 I/O Image Table DeviceNet SCANport PLC, SLC, PC Scanner 1203-Gx6/1336-GM6 Enhanced DeviceNet Drive Output Mapping (Write) Word 0 Logic Command Word 1 Reference Word 2 Datalink A1 Word 3 Datalink A2 Word 4 Datalink B1 Word 5 Datalink B2 Word 6 Datalink C1 Word 7 Datalink C2 Word 8 Datalink D1 Word 9 Datalink D2 Logic Command Reference Data In A1 Data In A2 Data In B1 Data In B2 Data In C1 Data In C2 Data In D1 Data In D2 Input Mapping (Read) Word 0 Logic Status Word 1 Feedback Word 2Datalink A1 Word 3 Datalink A2 Word 4 Datalink B1 Word 5 Datalink B2 Word 6 Datalink C1 Word 7 Datalink C2 Word 8 Datalink D1 Word 9 Datalink D2 Logic Status Feedback Data Out A1 Data Out A2 Data Out B1 Data Out B2 Data Out C1 Data Out C2 Data Out D1 Data Out D2 Message Handller Message Buffers Message Handler Important: Datalinks are optionally enabled in the adapter and configured in the product. Refer to Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection or Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet and your product s user manual for more information. Examples of reference/feedback include speed, torque, and frequency.

65 Ladder Logic Programming 6-3 Example Ladder Logic Programs The following are example ladder logic programs for a 1305, 1336 PLUS, or 1336 PLUS II drive.! ATTENTION: The example ladder logic program shown in this manual is intended solely for purpose of example. Because there are many variables and requirements associated with any particular installation, Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the example shown in this publication. Important: Refer to the user manual for your SCANport product for specific I/O definitions. Different SCANport products have different Logic Command, Logic Status, Reference and Feedback I/O interpretations.

66 6-4 Ladder Logic Programming The 1305, 1336 PLUS, or 1336 PLUS II drive in this example accepts the following Logic Command Data from the controller. Logic Command Bits Function Description X Stop 1=Stop, 0=No Operation X Start 1=Start, 0=No Operation X Jog 1=Jog, 0=No Operation X Clear Faults 1=Clear, 0=No Operation X X Direction 00=No Operation, 01=Forward 10=Reverse, 11=Hold Direction X Local 1=Local, 0=Multiplexed X MOP Increment 1=Increment MOP, 0=No Operation X X Accel Rate Select 00=No Operation, 01=Rate 1 10=Rate 2, 11=Hold Rate X X Decel Rate Select 00=No Operation, 01=Rate 1 10=Rate 2, 11=Hold Rate X X X Reference Selection 000=No Operation 001=External Reference 1 (Par 5) 010=External Reference 2 (Par 6) 011=Preset 3 100=Preset 4 101=Preset 5 110=Preset 6 111=Preset 7 X MOP Decrement 1=Decrement MOP, 0=No Operation The 1305, 1336 PLUS, or 1336 PLUS II drive in this example sends the following Logic Status Data to the PLC. Logic Status Bits Function Description X Enabled 1=Enabled, 0=Not Enabled X Running 1=Running, 0=Not Running X Command Direction 1=Forward, 0=Reverse X Rotating Direction 1=Forward, 0=Reverse X Acceleration 1=Accelerating, 0=Not X Deceleration 1=Decelerating, 0=Not X Warning 1=Warning Present, 0=Not X Fault 1=Faulted, 0=Not Faulted X At Reference 1=At Speed, 0=Not At Speed X X X Local 000=Terminal I/O has Local 001=Port 1 has Local 010=Port 2 has Local 011=Port 3 has Local 100=Port 4 has Local 101=Port 5 has Local 110=Port 6 has Local 111=Multiplexed Control X X X X Reference Source 0000=External Reference =Presets =External Reference =Port 1 6 Direction 1111=Jog

67 PLC Ladder Logic Example Ladder Logic Programming 6-5 The following example uses a PLC-5, a 1771-SDN DeviceNet scanner, and a 1203-GU6 to control a 1305, 1336 PLUS, or 1336 PLUS II drive. The example program shows how to obtain status information from the drive and how to control it (e.g., starting the drive, stopping the drive, jogging the drive, sending reference, and clearing faults). When you understand this example, you should be able to customize the program to fit you application needs. The example assumes that there is an operator s station wired to an I/O module in slot zero of module group zero of rack zero. Important: You may want to verify a device has not failed using word 0 of block transfer 62 before sending control data. If a device has failed, use block transfer 52 to find out which device failed. Refer to the 1771-SDN DeviceNet Scanner Module Manual, Publication , for more information Figure 6.2 Example PLC Ladder Logic Program The scanner gathers drive status information via DeviceNet. The Block Transfer Read in this rung then moves the drive status data from the scanner to the PLC s N9 data file. BT20:0 BTR Block Transfer Read EN Module Type Generic Block Transfer Rack 000 Group 0 Module 0 Control Block BT20:0 Data File N9:0 Length 62 Continuous No EN DN ER 0001 Rungs 0001 through 0003 move the drive status from the Block Transfer Read data file to an operator display Drive Operator Display RUNNING Drive Running Status Bit Status Bit N9:1 O: Drive FAULTED Status Bit N9:1 7 Operator Display Drive Faulted Status Bit O: Operator Display Drive Frequency Feedback MOV Move Source N9:2 0< Dest N21:1 0<

68 6-6 Ladder Logic Programming 0004 This rung enables the scanner. Figure 6.2 Example PLC Ladder Logic Program (Continued) 1771-SDN Scanner Port A Enable N10: Rungs 0005 through 0009 move the operator s inputs from the operator station to the Block Transfer Write data file where they will be sent to the scanner and out to the drive via DeviceNet. Operator Input 1305 Drive Drive Start START Command Bit Command Bit I:000 N10: Operator Input Drive Stop Command Bit I: Operator Input Drive Jog Command Bit I: Operator Input Drive Clear Faults Command Bit I: Drive STOP Command Bit N10: Drive JOG Command Bit N10: Drive CLEAR FAULT Command Bit N10: Drive REFERENCE Command Word MOV Move Source N21:0 0< Dest N10:2 0< The Block Transfer Write in this rung send the drive command data to the scanner and out to the drive via DeviceNet. BT20:1 BTW Block Transfer Write EN Module Type Generic Block Transfer Rack 000 Group 0 Module 0 Control Block BT20:1 Data File N10:0 Length 62 Continuous No EN DN ER 0011 END The following table represents the control file for the block transfers. Offset EN ST DN ER CO EW NR TO RW RLEN DLEN FILE ELEM R G S BT20: BT20:

69 SLC Ladder Logic Program Example Ladder Logic Programming 6-7 The following example uses a SLC-5/03, a 1747-SDN DeviceNet scanner, and a 1203-GU6 to control a 1336 PLUS, 1336 PLUS II or 1305 drive. The example assumes that there is an operator s station wired to an I/O module in slot one of module group zero of rack zero. Important: You may want to verify a device has not failed using word I:S.0. If a device has failed, read the appropriate M1 File to find out which device failed. Refer to the 1747-SDN DeviceNet Scanner Module Manual, Publication , for more information Figure 6.3 Example SLC Ladder Logic Program The scanner gathers drive status information via DeviceNet. The M-File is copied into the SLC s N9 data file to move the drive status information into a convenient location. COP Copy File Source #M1:1.0 Dest #N9:0 Length Rungs 0001 through 0003 move the drive status from the N9 data file to an operator display. 1336PLUS RUNNING Status Bit N9: PLUS FAULTED Status Bit N9:0 7 Operator Display Drive Running Status Bit O: O*8 Operator Display Drive Faulted Status Bit O: O*8 Operator Display Drive Frequency Feedback MOV Move Source N9:1 0< Dest N21:1 0<

70 6-8 Ladder Logic Programming Figure 6.3 Example SLC Ladder Logic Program (Continued) Rungs 0004 through 0008 move the operator s inputs from the operator station to the N9 data file where they will be sent to the scanner and out to the drive via DeviceNet. Operator Input 1336PLUS Drive Start START Command Bit Command Bit I:2.0 N10: I*16 Operator Input Drive Stop Command Bit I: I*16 Operator Input Drive Jog Command Bit I: I*16 Operator Input Drive Clear Faults Command Bit I: I* PLUS REFERENCE Command Word MOV Move Source N21:0 0< Dest N10:1 0< PLUS STOP Command Bit N10: PLUS JOG Command Bit N10: PLUS CLEAR FAULTS Command Bit N10: This rung enables the scanner. (Changes the scanner into RUN mode) This rung copies the drive command data to the scanner and out to the drive via DeviceNet SDN Scanner Enable Bit O: SDN COP Copy File Source #N10:0 Dest #M0:1.0 Length END

71 Chapter 7 Using DeviceNet Explicit Messaging Chapter Objectives Chapter 7 provides information you need to monitor and configure the SCANport device using explicit messaging on DeviceNet. In this chapter, you will read about the following: Required equipment. Message translations. Messaging guidelines for the 1771-SDN scanner. Messaging guidelines for the 1747-SDN scanner. Example messages. Using messages to control SCANport products. Writing to register objects. Refer to Appendix C, DeviceNet Objects, for information on object data support. Required Equipment Before using messaging, your PC must be: Running Logix5 and RSLinx if you are using a PLC. Refer to for more information on these products. Running RSLogix500 and RSLinx if you are using an SLC. Refer to for more information on these products. Connected to and communicating with the controller. Message Translations The communications adapter provides electronic translations of DeviceNet explicit messages into SCANport messages and back. The format of all explicit messages supported by the adapter is 8:16. The class field is 8 bits long, and the instance field is 16 bits long.! ATTENTION: Hazard of equipment damage exists. If explicit messages are programmed to frequently write parameter data to certain drive products, the EEPROM (Non-Volatile Storage) will quickly exceed its life cycle and cause the product to malfunction. Do not create a program that frequently uses explicit messages to write parameter data to a product. Datalinks do not write to the EEPROM and should be used for frequently changed parameters.

72 7-2 Using DeviceNet Explicit Messaging Messaging for the 1771-SDN Scanner The PLC uses a 64-word Block Transfer Write (BTW) to copy an Explicit Message into the 1771-SDN scanner. Ten explicit message buffers are available within the 1771-SDN scanner. When the BTW completes, the scanner executes the message. The PLC must then poll the scanner by performing a 64-word Block Transfer Read (BTR) to complete the message. (Note that the PLC can transfer two Explicit Messages per BTW or BTR and the scanner can have up to 10 Explicit Messages active at any time.) When the BTR completes, the data received by the PLC will contain information about the status of the current Explicit Message being processed by the scanner. If an Explicit Message has completed, the STATUS code in the Explicit Message Response is set to 1 and the response message contains the data requested. If the message status indicates that it is not completed, the BTR should be repeated until the message is complete. The format of Request and Response messages is in Figure 7.1Figure 7.1. Figure 7.1 Format of DeviceNet Messages Format of 64-word Block Transfer Write for Explicit Message Request Format of 64-word Block Transfer Read for Explicit Message Response Transaction #1 Header (3 words) TXID COMMAND TXID STATUS word 0 PORT SIZE PORT SIZE SERVICE MAC ID SERVICE MAC ID CLASS SERVICE RESPONSE DATA INSTANCE " ATTRIBUTE " SERVICE DATA " " " word 31 Transaction #2 Header (3 words) TXID COMMAND TXID STATUS word 32 PORT SIZE PORT SIZE SERVICE MAC ID SERVICE MAC ID CLASS SERVICE RESPONSE DATA INSTANCE " ATTRIBUTE " SERVICE DATA " " " word 63

73 Using DeviceNet Explicit Messaging 7-3 Transaction Blocks are divided into two parts: Transaction header contains information that identifies the transaction to the scanner and processor. Transaction body in a request, this contains the DeviceNet Class, Instance, Attribute and Service Data portion of the transaction. In a response, this contains the Service Data only. Each of the data attributes in the transaction header are one byte in length: Data Field TXID COMMAND STATUS Port Size SERVICE MAC ID Description Transaction ID when the processor creates and downloads a request to the scanner, the processor s ladder logic program assigns a TXID to the transaction. This is a one-byte integer in word 31 the range of 1 to 255. The scanner uses this value to track the transaction to completion, and returns the value with the response that matches the request downloaded by the processor. In each message request, a command code instructs the scanner how to administer the request: 0 = Ignore transaction block (block empty) 1 = Execute this transaction block 2 = Get status of transaction TXID 3 = Reset all client/server transactions = Reserved In each message response, the status code provides the processor with status on the device and its response: 0 = Ignore transaction block (block empty) 1 = Transaction completed successfully 2 = Transaction in progress (not ready) 3 = Error slave not in scan list 4 = Error slave off-line 5 = Error DeviceNet port disabled or off-line 6 = Error transaction TXID unknown 7 = Unused 8 = Error Invalid command code 9 = Error Scanner out of buffers 10 = Error Other client/server transaction in progress 11 = Error could not connect to slave device 12 = Error response data too large for block 13 = Error invalid port 14 = Error invalid size specified 15 = Error connection busy = Reserved The DeviceNet port where the transaction is routed. The port can be zero (Channel A) or one (Channel B) on a 1771-SDN scanner. The size of the transaction body in bytes. The transaction body can be up to 29 words (58 bytes) in length. If the size exceeds 29 words, an error code will be returned. The service attribute contains the DeviceNet service request and response codes that match the corresponding request for the TXID. The DeviceNet network address of the slave device where the transaction is sent. This value can range from 0 to 63. The port and MAC ID attributes coupled together identify the target slave device. The slave device must be listed in the scanner module s scan list and be on-line for the Explicit Message transaction to be completed.

74 7-4 Using DeviceNet Explicit Messaging Messaging for the 1747-SDN Scanner The SLC copies an Explicit Message into the scanner s M0-file. When the copy is completed the scanner moves the message into a queue for processing. Up to 10 Explicit Messages can be in this queue. When the scanner receives a response message it is placed into a queue. The first response in the queue is available from the M1-file. When the message delete command is copied into the scanner the message is complete and the next available response will appear in the M1-file. The format of Request and Response messages is in Figure 7.2Figure 7.2. Figure 7.2 Format of DeviceNet Messages Format of 32-word M0-file Write of Explicit Message Request Format of 32-word M1-file Read of Explicit Message Response Transaction Header (3 words) TXID COMMAND TXID STATUS word 0 PORT SIZE PORT SIZE SERVICE MAC ID SERVICE MAC ID CLASS SERVICE RESPONSE DATA Transaction Data (up to 29 words) INSTANCE " ATTRIBUTE " SERVICE DATA " " " word 31 For information on M-File locations, refer to the 1747-SDN DeviceNet Scanner Module Manual, Publication The message buffer is composed of two sections: Transaction header three words that contain information identifying the message transaction. Transaction body in a request, this contains the DeviceNet Class, Instance, Attribute and Service Data portions of the transaction. In a response, this contains the Service Data only.

75 Using DeviceNet Explicit Messaging 7-5 Each of the data fields in the transaction header are one byte in length: Data Field Description TXID COMMAND STATUS Transaction ID when the processor creates and downloads a request to the scanner, the processor s ladder logic program assigns a TXID to the transaction. This is a one-byte integer in word 31 the range of 1 to 255. The scanner uses this value to track the transaction to completion, and returns the value with the response that matches the request downloaded by the processor. For each download, a command code instructs the scanner how to administer the request: 0 = Ignore transaction block (block empty) 1 = Execute this transaction block 2 = Get status of transaction TXID 3 = Reset all client/server transactions 4 = Delete this transaction block = Reserved For each upload, the status code provides the processor with status on the device and its response: 0 = Ignore transaction block (block empty) 1 = Transaction completed successfully 2 = Transaction in progress (not ready) 3 = Error Slave not in scan list 4 = Error Slave off-line 5 = Error DeviceNet port disabled or off-line 6 = Error Transaction TXID unknown 7 = Unused 8 = Error Invalid command code 9 = Error Scanner out of buffers 10 = Error Other client/server transaction in progress 11 = Error Could not connect to slave device 12 = Error Response data too large for block 13 = Error Invalid port 14 = Error Invalid size specified 15 = Error Connection busy = Reserved PORT The DeviceNet port used by this message. The port must be zero (Channel A) on a SDN scanner. SIZE The size of the transaction body in bytes. The transaction body can be up to 29 words (58 bytes) in length. If the size exceeds 29 words, an error code will be returned. SERVICE MAC ID The service attribute contains the DeviceNet service request and response codes that match the corresponding request for the TXID. The DeviceNet network address of the slave device where the transaction is sent. This value can range from 0 to 63. The port and MAC ID uniquely identify the target slave device. The slave device must be listed in the scanner module s scan list and be on-line for the Explicit Message transaction to be completed.

76 7-6 Using DeviceNet Explicit Messaging Examples The following examples show messages used with the ladder logic programs begun in Chapter 6, Ladder Logic Programming.! ATTENTION: The example ladder logic program shown in this manual is intended solely for purpose of example. Because there are many variables and requirements associated with any particular installation, Rockwell Automation does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the example shown in this publication. PLC Messaging Figure 7.3, started in Chapter 6, Ladder Logic Programming, shows an example PLC ladder logic program that sends an explicit message. The message sent is contained in N30, beginning at word 0. The response data will appear in N30 starting at word I: B3:0 ONS 0 Figure 7.3 PLC Messaging Example BTW Block Transfer Write Module Type 1771-SDN DeviceNet Scanner Module Rack 000 Group 0 Module 0 Control Block BT20:2 Data File N30:0 Length 64 Continuous No EN DN ER MOV Move Source 0 0< Dest N30:70 257< 0001 BT20:2 DN CMP Comparison Expression N30:70 <> N30:0 BT20:3 EN BTR Block Transfer Read Module Type 1771-SDN DeviceNet Scanner Module Rack 000 Group 0 Module 0 Control Block BT20:3 Data File N30:70 Length 64 Continuous No EN DN ER 0002 END

77 Using DeviceNet Explicit Messaging 7-7 I:000/17: When you set this instruction to the true state, the next instruction, a one-shot block transfer write, sends data to the scanner. The Move instruction then initializes the first word of the data file that is used by the block transfer read instruction in the next rung. Instruction BT20:2.DN: This instruction will be true when the block transfer write has completed. The compare instruction that follows compares the first word of data sent from the scanner to the first word of data you send to the scanner. When the messaging function has completed, these two words will be equal. Instruction BT20:3.EN: Any time the block transfer read is not enabled, this instruction causes the block transfer read to be enabled if the two earlier conditions are true. BTR: Reads 64 words of data from the scanner. The following table displays data sent to and received from the scanner. Values are in hexadecimal. Offset N30: E N30: N30: N30: N30: N30: N30: N30: E N30: N30: N30: N30: N30: N30:

78 7-8 Using DeviceNet Explicit Messaging In this example, there were four entries in the fault queue. Notice the following about the data: Location Value Meaning N30:0 0x0201 TXID of 2. Command 1 (Execute) N30:1 0x0006 Port 0. Size = 6 bytes (N30:3 5) N30:2 0x0E03 Service E (Get Attribute Single) Node 3 N30:3 0x0097 SCANport Pass-Through Fault Object N30:4 0x0000 Instance 0 (Class Access) N30:5 0x0001 Attribute 1 (Number of Fault Queues) N30:70 0x0201 TXID of 2. Status 1 (Success) N30:71 0x0006 Port 0. Size = 6 bytes (N30:3 5) N30:72 0x8E03 Service 8E (Get Attribute Single Response) N30:73 0x fault queues Refer to Appendix C, DeviceNet Objects, for more information on object descriptions.

79 SLC Messaging Using DeviceNet Explicit Messaging 7-9 Figure 7.4 shows an example message in the SLC ladder logic program started in Chapter 6, Ladder Logic Programming. Figure 7.4 SLC Messaging Example When B3:0/0 is set true, this rung will copy the 32 words of the Explicit Message from the buffer at N20:10 to the M0-File Explicit Message buffer. The 1747-SDN will send the message out over DeviceNet Initiate Explicit Message B3:0 0 Explicit Message COP Copy File Source #N20:10 Dest #M0:1.224 Length 32 Initiate Explicit Message B3:0 U 0 When I:1.0/15 is true and the Explicit Message response has been received and is in the M1-File, this rung: 1) Copies the response message into N10:50 2) Copies a command byte of 4 into the M1-File (commands the 1747-SDN scanner to discard the response data so that the buffer can be used for the next available response message) 0001 Explicit Message Response Available I: SDN Explicit Message Response COP Copy File Source #M1:1.224 Dest #N20:50 Length 32 EQU Equal Source A N20: < Source B N20: < Explicit Message MVM Masked Move Source N20:0 4< Mask 00FFh 255 < Dest M0:1.224?< 0002 END Important: To originate a scanner transaction, you must use a copy operation to M0:[slot number]:224. Then, use a copy operation to read M1:1.224 for the results. If you have more than one message enabled, you will have to use the TXID to determine which message you are reading.

80 7-10 Using DeviceNet Explicit Messaging The following table display data sent to and received from the scanner. Values are in hexadecimal. Offset N20: N20: E N20: N20: N20: N20: E N20: N20: N20: In this example, there were four entries in the fault queue. Notice the following about the data: Location Value Meaning N20:10 0x0201 TXID of 2. Command 1 (Execute) N20:11 0x0006 Port 0. Size = 6 bytes (N30:3 5) N20:12 0x0E03 Service E (Get Attribute Single) Node 3 N20:13 0x0097 SCANport Pass-Through Fault Object N20:14 0x0000 Instance 0 (Class Access) N20:15 0x0001 Attribute 1 (Number of Fault Queues) N20:50 0x0201 TXID of 2. Status 1 (Success) N20:51 0x0006 Port 0. Size = 6 bytes (N30:3 5) N20:52 0x8E03 Service 8E (Get Attribute Single Response) N20:53 0x fault queues Refer to Appendix C, DeviceNet Objects, for more information on object descriptions. Using Messages to Control SCANport Products Explicit messages provide multi-purpose, point-to-point communication paths between two devices. It is possible to control SCANport devices through explicit messaging on DeviceNet by following particular guidelines and by writing to various register objects that are buffering the I/O data. The guidelines are as follows: The adapter cannot be allocated by a master/scanner in order to allow explicit writes to the register object.

81 Using DeviceNet Explicit Messaging 7-11 Write access to any register object within the adapter will not be allowed if the message is passed through a connection whose expected packet rate (EPR) is zero. The adapter is required to mark any explicit connection after allowing a write to a register object through it. If a marked explicit connection times out based on the EPR, then the I/O fault action will be that configured for Communication Loss over the I/O connection. If a marked explicit connection is deleted, then the I/O fault action will be that configured for Idle over the I/O connection. Multiple explicit connections can write/overwrite the control I/O if they meet the guidelines specified. Each connection will need to be marked individually within the adapter. If the adapter gets allocated/re-allocated by a controller such that valid I/O data is being sent to the adapter, or if an Idle condition from the allocating controller is transitioned back to valid data, then all marked explicit connections will be reset to unmarked and future writes blocked. If a marked connection has its EPR value reset to zero (0) after being marked, then the connection will become unmarked.

82 7-12 Using DeviceNet Explicit Messaging Writing to Register Objects Within the Enhanced DeviceNet adapter, various register objects buffer I/O in the following fashion (RO=Read Only, R/PW=Read/Write Protected): Instance Access Size Function 1 RO See M-S Output Poll Response I/O data to controller 2 R/PW See M-S Output Buffered Poll I/O data from controller 3 RO 32 bits Logic Status & Feedback 4 R/PW 32 bits Datalink A from SCANport Device (if enabled) 5 RO 32 bits Datalink A to SCANport Device (if enabled) 6 R/PW 32 bits Datalink A from SCANport Device (if enabled) 7 RO 32 bits Datalink B to SCANport Device (if enabled) 8 R/PW 32 bits Datalink B from SCANport Device (if enabled) 9 RO 32 bits Datalink C to SCANport Device (if enabled) 10 R/PW 32 bits Datalink C from SCANport Device (if enabled) 11 RO 32 bits Datalink D to SCANport Device (if enabled) 12 R/PW 32 bits Datalink D from SCANport Device (if enabled) 13 RO 32 bits Logic Status and Feedback 14 R/PW 32 bits Logic Command (Last Logic Command is ANDed with the first word in this command and ORed with the second word in the command. The reference is not modified. This command allows bit changes to the logic command without affecting the speed reference or other control bits.) Refer to the Class Code 0x07 Register Object section in Appendix C, DeviceNet Objects for more information on the Register Object.

83 Chapter 8 Troubleshooting Chapter Objectives Chapter 8 provides information about the adapter s LEDs and basic troubleshooting procedures. In this chapter, you will read about the following: Locating the LEDs. Using the LEDs to troubleshoot the adapter. LEDs on the Enhanced DeviceNet Adapter Your communications adapter has three LED status indicators. The LEDs provide status information about the DeviceNet network, SCANport connection, and the adapter itself. Refer to Figure 8.1. Figure 8.1 LED Status Indicators SCANport Status Module Status DeviceNet Status 1203-GU6 DeviceNet Status Module Status SCANport Status 1336-GM6

84 8-2 Troubleshooting DeviceNet Network Status LED States The LED closest to the DeviceNet connector is the DeviceNet Status LED, labeled NET. It functions as follows: LED Viewed: If: State: Indicates Action: LED is off Not powered/not online No power/duplicate ID not completed 1. Verify that the network supply is connected and that power is reaching the adapter through the connector. 2. Make sure one or more nodes are communicating on the network. 3. Make sure at least one other node on the network is operational at the same time and data rate as the adapter. Network Status LED LED is flashing green Online/Not connected Passed duplicate ID/No connection established No action needed. The LED is flashing to signify that there are no open communication connections between the adapter and any other device. Any connection (I/O or explicit message) made to the adapter over DeviceNet will cause the LED to stop flashing and remain steady on for the duration of any open connection. LED is steady green Online/Connected One or more connections established LED is flashing red Online/Time-out I/O connection timed out LED is steady red Network failure Failed Duplicate ID or Bus-off No action needed. 1. Bring controller back onto the network. 2. Reduce traffic or errors on the network so that messages can get through within the necessary time frame. 1. Ensure that all nodes have unique addresses. 2. If all node addresses are unique, examine network for correct media installation. Module Status LED States The middle LED, labeled MOD, is the Module Status LED. It indicates the operation of the Enhanced DeviceNet adapter and functions as follows: LED Viewed: If: State: Indicates: Action: LED is off Not powered No power Ensure that the connected SCANport product is powered and connected to the adapter. LED is flashing green Waiting for I/O data Normal operation No I/O, or PLC in program No action needed. Adapter has passed all operational tests and is waiting to pass I/O data between the DeviceNet and SCANport interfaces. Module Status LED LED is solid green Operational Normal operation I/O operational LED is flashing red Configuration problem Bad CRC of Adapter parameters or flash program LED is steady red Hardware failure Failed internal or external RAM test No action needed. 1. Power cycle the adapter to reset it. 2. Enable an adapter reset via the adapter s configuration parameter. 3. Re-flash the adapter. Replace unit.

85 SCANport Status LED States Troubleshooting 8-3 The LED furthest from the DeviceNet connector is the SCANport Status LED, and is labeled SP. It indicates the status of the SCANport connection, and functions as follows: LED Viewed: If: State: Indicates Action: LED is off Not powered No power Ensure that the connected SCANport device is powered and that the product is connected to the adapter. LED is flashing green Online/ I/O connecting Requesting I/O connections or no I/O is selected No action needed. Adapter is establishing one or more of the I/O connections with the SCANport device. SCANport Status LED LED is steady green I/O operational One or more connections established LED is flashing red Configuration fault SCANport problem: No communications seen from the SCANport device to request connections LED is steady red Link failure SCANport failure: Poor cable connection does not allow proper port identification or the SCANport device isn t allowing the configured I/O connections. No action needed. 1. Reseat cable properly. 2. Replace cable. 1. Check all SCANport cables and connections to the SCANport device. 2. Ensure datalinks are not enabled on a product that doesn t support datalinks. Or, ensure that a particular datalink is not already being used by another adapter on the same SCANport device. In either case, the adapter must be properly configured and power cycled after the problem is fixed. LED is steady orange Failed SCANport compatibility test Call Rockwell Automation support.

86 8-4 Troubleshooting Notes:

87 Appendix A Specifications Appendix Objectives 1203-GU6 Specifications Appendix A provides the specifications that you may need to install or use either the 1203-GU6 module or the 1336-GM6 board. These adapters are non-repairable units. If they are broken, you must replace them. The following table gives the specifications for the 1203-GU6 Enhanced DeviceNet communications module. Category Specifications Dimensions Weight Operating Temperature Storage Temperature Relative Humidity (Operating) Relative Humidity (Non-Operating) Shock (Operating) Shock (Non-Operating) Vibration (Operating) Vibration (Non-Operating) Power Consumption ESD Susceptibility (IEC ) Regulatory Agencies DIN Rail Mounting Standard 1.8" W x 3.0" H x 5.0" D (4.57 cm x 7.62 cm x 12.7 cm) 6.3 oz (179 g) 0 to +55 C (32 to 131 F) 40 to +85 C ( 40 to 185 F) 5 to 80% non-condensing 5 to 95% non-condensing 30g peak acceleration, 11(+/ 1)ms pulse width 50g peak acceleration, 11(+/ 1)ms pulse width 2.5g at 5Hz 2KHz 5g at 5Hz 2KHz 130mA at 12V supplied through SCANport, and 60mA at 24V supplied through DeviceNet 4KV contact, 8KV open air UL 508 and CUL European Union EMC and Low Voltage Directives 1.38 x 0.30 in. (35 x 7.5 mm)

88 A-2 Specifications 1336-GM6 Specifications The following table gives the specifications for the 1336-GM6 Enhanced DeviceNet communications board. Category Specifications Dimensions Weight Operating Temperature Storage Temperature Relative Humidity (Operating) Relative Humidity (Non-Operating) Shock (Operating) Shock (Non-Operating) Vibration (Operating) Vibration (Non-Operating) Power Consumption ESD Susceptibility (IEC ) Regulatory Agencies 4.5" W x 2.8" H x 0.5" D (11.43 cm x cm x 1.27 cm) 1.8 oz (51 g) 0 to +55 C (32 to 131 F) 40 to +85 C ( 40 to 185 F) 5 to 80% non-condensing 5 to 95% non-condensing 30g peak acceleration, 11(+/ 1)ms pulse width 50g peak acceleration, 11(+/ 1)ms pulse width 2.5g at 5Hz 2KHz 5g at 5Hz 2KHz 150mA at 5V (supplied from Drive Control Board) 60mA at 24V (supplied through DeviceNet) 4KV contact, 8KV open air UL 508 and CUL European Union EMC and Low Voltage Directives! ATTENTION: The 1336-GM6 communications board contains ESD (Electrostatic Discharge) sensitive parts. Static control precautions are required when installing, testing, or servicing this assembly. Device malfunction may occur if you do not follow ESD control procedures. If you are not familiar with static control procedures, refer to Allen-Bradley Publication , Guarding Against Electrostatic Damage,or other applicable ESD protection handbook.

89 Appendix B Appendix Objectives Enhanced DeviceNet Adapter s Parameters Appendix B provides information on the Enhanced DeviceNet adapter s parameters and how to configure them. In this appendix, you will read about the following: Setting the node address. Setting the data rate. Using datalinks and command I/O. Using Master-Slave communications. Using Peer-to-Peer communications. Using Fault Configurable inputs. Parameters in the Enhanced DeviceNet adapter. Important: The the number for parameters appears in parenthesis after the name. This is the number in the adapter. If you are using RSNetWorx for DeviceNet, the number for each adapter parameter varies depending on the type of drive you are using. Setting the Node Address The Enhanced DeviceNet adapter has a default node address of 63. This address should be changed to a unique address (between 0 and 62) on your DeviceNet network. Important: If you are installing multiple Enhanced DeviceNet adapters on the network at the same time or there is already a node 63 on the network, you need to do one of the following: Connect to each adapter using a serial point-to-point connection and give each a unique address. Power up only one adapter at a time on the network and give each a unique node address. If using software that supports the Fault Node Recovery feature of DeviceNet, power up all the adapters at the same time and give each a unique node address. To set the node address, you need to: 1. Access the adapter s parameters using either a serial connection (refer to Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection) or over the DeviceNet network (refer to Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet).

90 B-2 Enhanced DeviceNet Adapter s Parameters 2. Set the DN Node Address (2) parameter to the desired address. 3. Reset the adapter by setting the Reset Adapter (22) parameter to Enable. Setting the Data Rate The Enhanced DeviceNet adapter supports the following data rates: 125 Kbps 250 Kbps 500 Kbps Autobaud The adapter defaults to using autobaud data rate detection. Important: At least one continually transmitting device on the network (usually the scanner) must be set to a fixed data rate (not autobaud). This device sets the data rate for the network that the other nodes using autobaud detect. If you want to change your adapter s data rate, you need to: 1. Access the adapter s parameters using either a serial connection (refer to Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection) or the DeviceNet network (refer to Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet). 2. Set the DN Data Rate (3) parameter to the desired value. Refer to the following table for information on acceptable values. Data Rates 125 Kbps 250 Kbps 500 Kbps Thick Trunk Length 500 m (1 640 ft) 250 m (820 ft) 100 m (328 ft) Thin Trunk Length 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) 3. Reset the adapter by setting the Reset Adapter (22) parameter to Enable. Using Datalinks and Command I/O Command I/O provides two 16-bit words of input and two 16-bit words of output when enabled. Datalinks let you increase the size of I/O to and from a SCANport device (provided the SCANport device supports datalinks). By enabling datalinks, you can continuously change or monitor the value of a parameter without using the DeviceNet to SCANport messaging function. Datalinks consist of two 16-bit words of input and two 16-bit words of output when enabled. They provide up to eight words (in and out) of data if they are supported in the connected SCANport product.

91 Enhanced DeviceNet Adapter s Parameters B-3 SCANport devices that support this function have a group of parameters for datalink configuration. These parameters are Data In A1 D2 and Data Out A1 D2. If you intend to use command I/O and/or datalinks, you must do the following: 1. Access the adapter s parameters using either a serial connection (refer to Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection) or the DeviceNet network (refer to Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet). 2. Enable the Cmd/Stat Config (4) parameter and/or desired DataLink (5 8) parameters within the Enhanced DeviceNet adapter. Figure B.1 Module I/O Configuration Cmd/Stat Config Data from DeviceNet Data to DeviceNet Module Input Logic Command Reference DL A1 Inp DL A2 Inp DL B1 Inp DL B2 Inp DL C1 Inp DL C2 Inp DL D1 Inp DL D2 Inp Module Output Logic Status Feedback DL A1 Out DL A2 Out DL B1 Out DL B2 Out DL C1 Out DL C2 Out DL D1 Out DL D2 Out Datalink A Config Datalink B Config Datalink C Config Datalink D Config Data to the SCANport Device Data from the SCANport Device 3. Configure or link the Data In A1 D2 and Data Out A1 D2 parameters in the SCANport product. Refer to the documentation for your SCANport product. 4. Configure the M-S Input parameter and M-S Output parameter as desired. Refer to the M-S Input Parameter Configurations section or the M-S Output Parameter Configurations sections in this chapter. 5. Reset the adapter by setting the Reset Adapter (22) parameter to Enable.

92 B-4 Enhanced DeviceNet Adapter s Parameters Using Master-Slave Communications To have your Enhanced DeviceNet adapter receive its I/O from a scanner (PLC or SLC) on the DeviceNet network, you must configure it for Master-Slave communications. Figure B.2 Master-Slave Communications MSB X X X M-S Input (24) LSB MSB X X M-S Output (25) X LSB 1=Enable 0=Disable Master Data from DeviceNet Slave Data to DeviceNet Adapter Input Logic Command Reference DL A1 Inp DL A2 Inp DL B1 Inp DL B2 Inp DL C1 Inp DL C2 Inp DL D1 Inp DL D2 Inp Adapter Output Logic Status Feedback DL A1 Out DL A2 Out DL B1 Out DL B2 Out DL C1 Out DL C2 Out DL D1 Out DL D2 Out Data to the SCANport Device Data from the SCANport Device Master-Slave communications let you transmit 2 10 words of I/O data between the adapter and the scanner. How you configure your adapter and scanner depends on the type of allocation you are using. The adapter supports the following: Polled. COS (Change of State). Cyclic. Polled and COS. Polled and Cyclic. Polled Allocation In polling, the scanner sends control data to the adapter, and then the adapter responds with its status data. To use polling, you must enable polling in the adapter and in the scanner. 1. Enable the desired I/O and datalinks (parameters 4 8). 2. Set the M-S Input (24) parameter. Refer to the M-S Input Parameter Configurations section in this chapter. 3. Set the M-S Output (25) parameter. Refer to the M-S Output

93 Enhanced DeviceNet Adapter s Parameters B-5 Parameter Configurations section in this chapter. 4. Reset the adapter by setting the Reset Adapter (22) parameter to Enable. 5. When you configure the scanner, set up polled I/O. Refer to Setting Up the Scan List in Chapter 5. COS (Change of State) Allocation When you set up COS allocation, the scanner sends data to the adapter at a constant rate (called a heartbeat). If data in the adapter changes between messages from the scanner, your adapter sends its new status to the scanner. To use COS, you must enable COS in the adapter and in the scanner. 1. Enable the desired I/O and datalinks (parameters 4 8). 2. Set the M-S Input (24) parameter. Refer to the M-S Input Parameter Configurations section in this chapter. 3. Set the M-S Output (25) parameter. Refer to the M-S Output Parameter Configurations section in this chapter. 4. Ensure the Cmd/Stat Config (4) parameter is On. 5. Ensure the lowest bit in the M-S Output (25) parameter is set to 1. For example, xxx0, This enables status/feedback to be sent over the slave connection. 6. Set the COS Status Mask (26) parameter to specify which bits in the logic status word will trigger a message to the scanner when changed. (0 = do not check the corresponding bit.) 7. Set the COS Fdbk Change (27) parameter to specify the amount of change required in the reference word needed to trigger a message to the scanner. (0 = do not check the corresponding bit) 8. Reset the adapter by setting the Reset Adapter (22) parameter to Enable. 9. When you configure the scanner, set up Change of State. Refer to Setting Up the Scan List in Chapter 5. Important: After you have configured the scanner and adapter for COS, you can verify the desired heartbeat rate is used by viewing the COS/CYC Interval (28) parameter in the adapter. Cyclic Allocation When you set up cyclic allocation, your adapter sends or receives data based on a periodic time interval. To use Cyclic, you must enable Cyclic in the adapter and in the scanner. 1. Enable the desired command I/O and datalinks. Refer to the Using Datalinks and Command I/O section in this chapter.

94 B-6 Enhanced DeviceNet Adapter s Parameters 2. Set the M-S Input (24) parameter. Refer to the M-S Input Parameter Configurations section in this chapter. 3. Set the M-S Output (25) parameter. Refer to the M-S Output Parameter Configurations section in this chapter. 4. Ensure the Cmd/Stat Config (4) parameter is set to On. 5. Ensure the lowest bit in M-S Output (25) parameter is set to Reset the adapter by setting the Reset Adapter (22) parameter to Enable. 7. When you configure the scanner, set up polled I/O. Refer to Setting Up the Scan List in Chapter 5. Important: After you have configured the scanner and adapter for Cyclic, you can verify the desired send rate is used by viewing the COS/CYC Interval (28) parameter in the adapter. Polled and COS Allocation You can enable both polling and COS allocations. This lets the scanner poll the adapter at a fixed interval and the adapter report its status changes to the scanner after they occur. Refer to both the Polled Allocation and the COS (Change of State) Allocation sections in this chapter for information. Polled and Cyclic Allocation You can enable both polling and cyclic allocations. This allows the scanner to poll the adapter at fixed intervals and the adapter to send its status to the scanner at fixed intervals. Refer to both the Polled Allocation section and the Cyclic Allocation section in this chapter for information. Using Peer-to-Peer Communications To have your adapter receive data from or transmit data to another 1203-GU6 or 1336-GM6 on the DeviceNet network, you must configure it for peer-to-peer communications. Peer-to-peer communications are best used in the following instances: A PLC sends data to a drive. That drive re-transmits the data to other drives on the network. A drive is configured on a network. It sends data to other drives on the network. Important: After setting up peer-to-peer communications, you must make sure the configuration that you set up works as you intend it to work. To enable peer-to-peer communications, you must enable one adapter to transmit peer I/O and one or more adapters to receive peer I/O.

95 Enhanced DeviceNet Adapter s Parameters B-7 Enabling the Adapter to Receive Peer I/O To have your Enhanced DeviceNet adapter receive input data from another Enhanced DeviceNet adapter on the network, you must configure it for peer-to-peer communications. Figure B.3 Receiving I/O from a Peer Device Peer Input Data from DeviceNet Peer A Word 1 Peer A Word 2 Peer B Word 1 Peer B Word 2 Peer A Input Peer B Input Peer Cmd Mask Peer Ref Adjust Module Input Logic Command Reference DL A1 Inp DL A2 Inp DL B1 Inp DL B2 Inp DL C1 Inp DL C2 Inp DL D1 Inp DL D2 Inp Module Output Logic Status Feedback DL A1 Out DL A2 Out DL B1 Out DL B2 Out DL C1 Out DL C2 Out DL D1 Out DL D2 Out Data to the SCANport Device Data from the SCANport Device In Peer-to-Peer communications, you can receive 2 or 4 I/O words from another adapter. Follow these directions: 1. Enable the desired I/O and datalinks within the adapter and SCANport product. Refer to the Using Datalinks and Command I/O section in this chapter. 2. Ensure the Peer Inp Enable (36) parameter is Off. 3. Set the Peer Node to Inp (34) parameter to the number of the node from which you want to receive data. 4. Set the Peer A Input (29) parameter to a destination for the first 2 words of data. 5. If using 4 words of input, set the Peer B Input (30) parameter to a destination for the second two words of data. 6. If receiving Cmd/Ref input data, set the bits in the Peer Cmd Mask (31) parameter according to the following table. Important: If both Master-Slave data and Peer data are being used to control the adapter, make sure you know which one is transmitting which control bits. The adapter will receive each control bit from only one source. This includes the stop bit. If receiving I/O from: Then set bit to: Master device (PLC or SLC) 0 Peer device (another Enhanced DeviceNet adapter) 1

96 B-8 Enhanced DeviceNet Adapter s Parameters 7. If sending Cmd/Ref I/O data, set the percentage in the Peer Ref Adjust (23) parameter. The adapter multiplies this value with the speed reference value to determine the drive s speed. 8. Set the Peer Inp Time-out (35) parameter to the maximum amount of time the adapter will wait for a message before timing out. Important: This value must be greater than the product of Peer Out Time (41) parameter multiplied by the Peer Out Skip (42) parameter in the adapter from which you are receiving I/O. 9. Set the Peer Flt Action (33) parameter to determine what the adapter should do if it times out. 10. Set the Peer Inp Enable (36) parameter to On. 11. Check the Peer Inp Status (37) parameter to verify operation. It should either be Waiting (meaning it is waiting for the first Tx) or Running (meaning it is receiving input data). Your adapter is now configured to accept I/O data from another Enhanced DeviceNet adapter. Make sure another Enhanced DeviceNet adapter on the DeviceNet network is configured to transmit peer data. Refer to the Enabling the Adapter to Transmit Peer I/O section in this chapter. Enabling the Adapter to Transmit Peer I/O You can have your Enhanced DeviceNet adapter send I/O data to another Enhanced DeviceNet adapter on the network. Figure B.4 Transmitting I/O to Another Adapter Peer A Output Peer Input Data from DeviceNet M-S Input Data from DeviceNet Module Input Logic Command Reference DL A1 Inp Peer Output Data to DeviceNet Peer A Word 1 Peer A Word 2 Peer B Word 1 DL A2 Inp DL B1 Inp DL B2 Inp DL C1 Inp DL C2 Inp DL D1 Inp DL D2 Inp Data to the SCANport Device Peer B Word 2 Module Output Logic Status Feedback DL A1 Out DL A2 Out DL B1 Out DL B2 Out DL C1 Out Data from the SCANport Device DL C2 Out DL D1 Out DL D2 Out Peer B Output To have your adapter send output data to another adapter, you need to: 1. Ensure the Peer Output Enable (40) parameter is Off. 2. Set the Peer A Output (38) parameter to the source of the output data.

97 Enhanced DeviceNet Adapter s Parameters B-9 3. If transmitting 4 words, set the Peer B Output (39) parameter to a different source of output data. 4. Set the Peer Output Time (41) parameter to the minimum time interval between peer messages. 5. Set the Peer Output Skip (42) parameter to a value between 1 and 16. The product of this value and the value of the Peer Output Time (41) parameter determine the maximum time interval between peer messages if there is not a change in status. 6. Set the Peer Output Enable (40) parameter to On. Your adapter is now configured to transmit I/O data to another Enhanced DeviceNet adapter. Make sure another Enhanced DeviceNet adapter on the DeviceNet network is configured to receive peer data. Refer to the Enabling the Adapter to Receive Peer I/O section in this chapter. Using Fault Configurable Inputs You can select constant values that your adapter will maintain in the event of a controller mode change or error. These constant values are referred to as Fault Configurable inputs. When the controller is placed in program mode or a DeviceNet network fault occurs, the control outputs from the adapter to the SCANport product can be set to automatically switch to the constant values set in the Fault Cfg In parameters. This lets you define a safe operating state for controlled devices that depend on pre-programmed output from the adapter.! ATTENTION: Risk of severe bodily injury or equipment damage exists. The Idle Flt Action (9) and Comm Flt Action (10) parameters allow the user to change the default configuration that would allow the module and associated drive to continue to operate if communication is lost. Precautions should be taken to assure that your settings for these parameters and your application do not create a hazard of bodily injury or equipment damage. If you intend to use Fault Configurable inputs, you must do the following: 1. Set desired values for the Fault Cfg Logic (11), Fault Cfg Ref (12), and Fault Cft In (13 20) parameters. 2. Set the Idle Fault Config (9) parameter and/or the Comm Flt Action (10) parameter to Fault Cfg. Refer to Chapter 3, Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection, or Chapter 4, Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet, for instructions on editing parameters.

98 B-10 Enhanced DeviceNet Adapter s Parameters Enhanced DeviceNet Adapter Parameters The following table provides information on the Enhanced DeviceNet communications adapter s parameter set. Important: When accessing this parameter set through the DeviceNet Parameter Class, add the adapter s parameter number to the number of the last parameter of the SCANport device. When accessing this parameter set through the vendor-specific SCANport Variables-Linear Class, add the adapter s parameter number to 4000H. # Name Valid Values/ Settings Default Writable Reset or Power Cycle Description 1 SCANport Adapter 0-7 NA No No Identifies the port number to-which the adapter is connected on the SCANport product. 2 DN Node Address Yes Yes Identifies the DeviceNet Node Address for the adapter. 3 DN Data Rate 125K 250K 500K Auto Auto Yes Yes Identifies the data rate used on the DeviceNet network. Important: At least one node on your DeviceNet network must be configured to a data rate (125, 250, or 500 K), not autobaud. 4 Cmd/Stat Config Off, On On Yes Yes Determines whether to pass logic command and analog reference control data from a DeviceNet connection to a SCANport product. If you are using a Master (scanner), parameters 24 and 25 must also be set. 5 Datalink A Cfg Off, On Off Yes Yes Determines whether to pass control data contained in datalink A from a DeviceNet connection to the SCANport product. If you are using a Master (scanner), parameters 24 and 25 must also be set. 6 Datalink B Cfg Off, On Off Yes Yes Determines whether to pass control data contained in datalink B from a DeviceNet connection to the SCANport product. If you are using a Master (scanner), parameters 24 and 25 must also be set. 7 Datalink C Cfg Off, On Off Yes Yes Determines whether to pass control data contained in datalink C from a DeviceNet connection to the SCANport product. If you are using a Master (scanner), parameters 24 and 25 must also be set. 8 Datalink D Cfg Off, On Off Yes Yes Determines whether to pass control data contained in datalink D from a DeviceNet connection to the SCANport product. If you are using a Master (scanner), parameters 24 and 25 must also be set. Important: For information on accessing and editing parameters, refer to Chapter 3, Configuring the 1203-GU6 Using a Serial Connection, or Chapter 4, Configuring the 1203-GU6 or 1336-GM6 Adapter Using RSNetWorx for DeviceNet.

99 Enhanced DeviceNet Adapter s Parameters B-11 # Name Valid Values/ Settings Default Writable Reset or Power Cycle Description 9 Idle Flt Action Fault Zero Data Hold Last Fault Cfg Fault Yes No Determines the action the adapter should instruct the SCANport product to take if the adapter detects that the PLC is set to program mode. Important: If you change this parameter s value, the user application may not be able to control the product after a fault.! ATTENTION: Risk of severe bodily injury or equipment damage exists. The Idle Flt Action (9) parameter allows the user to change the default configuration that would allow the module and associated drive to continue to operate if communication is lost. Precautions should be taken to assure that your settings for these parameters and your application do not create a hazard of bodily injury or equipment damage. 10 Comm Flt Action Fault Zero Data Hold Last Fault Cfg Fault Yes No Determines the action the adapter should instruct the SCANport product to take if the adapter detects a network failure. Important: If you change this parameter s value, the user application may not be able to control the product after a fault.! ATTENTION: Risk of severe bodily injury or equipment damage exists. The Comm Flt Action (10) parameter allows the user to change the default configuration that would allow the module and associated drive to continue to operate if communication is lost. Precautions should be taken to assure that your settings for these parameters and your application do not create a hazard of bodily injury or equipment damage. 11 Fault Cfg Logic Yes No Provides the logic command data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 12 Fault Cfg Ref Yes No Provides the analog reference data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. Important: For information on accessing and editing parameters, refer to Chapter 3, Configuring the 1203-GU6 Using a Serial Connection, or Chapter 4, Configuring the 1203-GU6 or 1336-GM6 Adapter Using RSNetWorx for DeviceNet.

100 B-12 Enhanced DeviceNet Adapter s Parameters # Name Valid Values/ Settings Default Writable Reset or Power Cycle Description 13 Fault Cfg A1 In Yes No Provides the first word of datalink A data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 14 Fault Cfg A2 In Yes No Provides the second word of datalink A data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 15 Fault Cfg B1 In Yes No Provides the first word of datalink B data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 16 Fault Cfg B2 In Yes No Provides the second word of datalink B data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 17 Fault Cfg C1 In Yes No Provides the first word of datalink C data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 18 Fault Cfg C2 In No No Provides the second word of datalink C data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 19 Fault Cfg D1 In Yes No Provides the first word of datalink D data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 20 Fault Cfg D2 In Yes No Provides the second word of datalink D data to the SCANport product when the adapter is instructed to use the values for the Fault Cfg parameters. 21 Serial Port Rate Reset Adapter Ready Enable Set Defaults 9600 Yes Yes Sets the baud rate for the adapter s serial/df1 port. Important: If you change the baud rate in the adapter, you must also change it in your terminal emulation software or terminal. Ready Yes No Ready = No change or reset. Enable = Resets the module. Set Defaults = Sets all parameters to their factory-default values. Important: For information on accessing and editing parameters, refer to Chapter 3, Configuring the 1203-GU6 Using a Serial Connection, or Chapter 4, Configuring the 1203-GU6 or 1336-GM6 Adapter Using RSNetWorx for DeviceNet.

101 Enhanced DeviceNet Adapter s Parameters B-13 # Name Valid Values/ Settings Default Writable Reset or Power Cycle Description 23 Active I/O Cfg 0 or 1 for each bit N/A No No Displays what I/O is activated in the adapter. datalink C datalink D datalink B datalink A Cmd/Stat xxx0, = Off 1 = On 24 M-S Input 0 or 1 for each bit xxx0, 0001 Yes Yes Determines the source of the bits for input. datalink C datalink D datalink B datalink A Cmd/Ref xxx0, = Peer or other input 1 = Master-Slave input For more information, refer to the M-S Input Parameter Configurations section in this chapter. 25 M-S Output 0 or 1 for each bit xxx0, 0001 Yes Yes Determines the source of the bits for output. datalink C datalink D datalink B datalink A Stat/Fdbk xxx0, = Peer or other output 1 = Master-Slave output For more information, refer to the M-S Output Parameter Configurations section in this chapter. 26 COS Status Mask 0 or 1 for each bit 0 Yes No Provides a mask of the Logic Status word to define which bits are checked for changes during COS allocation. 0 = Off (not checked) 1 = On (checked) Important: Refer to your SCANport product s documentation for information on its Logic Status word. Important: For information on accessing and editing parameters, refer to Chapter 3, Configuring the 1203-GU6 Using a Serial Connection, or Chapter 4, Configuring the 1203-GU6 or 1336-GM6 Adapter Using RSNetWorx for DeviceNet.

102 B-14 Enhanced DeviceNet Adapter s Parameters # Name Valid Values/ Settings Default Writable Reset or Power Cycle Description 27 COS Feedback Change = disable Yes No Determines how much (+/-) the feedback word can change before a message is sent during COS operations. 28 COS/Cyc Interval N/A N/A No No Displays the interval used by the controller to check for data in the adapter during COS or Cyclic allocation. 29 Peer A Input Off, Cmd/Ref DL A Input DL B Input DL C Input DL D Input 30 Peer B Input Off Cmd/Ref DL A Input DL B Input DL C Input DL D Input Off Yes No Determines where the peer A input is sent in the SCANport product. Important: This parameter cannot be changed when the Peer Inp Enable (36) parameter is On. Off Yes No Determines where the peer B input is sent in the SCANport product. Important: This parameter cannot be changed when the Peer Inp Enable (36) parameter is On. 31 Peer Cmd Mask 0 or 1 for each bit 0 Yes Yes Provides a mask for the Logic Command word when it is received through peer input. 0 = Off (input received from Master) 1 = On (input received from Peer) 32 Peer Ref Adjust % 0 Yes No Provides the percentage of the Reference value received through peer input that will be applied to the SCANport reference value. 33 Peer Flt Action Fault Zero Data Hold Last Fault Cfg Fault Yes No Determines the action the adapter should instruct the SCANport product to take if the adapter does not receive peer input in the allowed time.! ATTENTION: Risk of severe bodily injury or equipment damage exists. The Peer Flt Action (33) parameter allows the user to change the default configuration that would allow the module and associated drive to continue to operate if communication is lost. Precautions should be taken to assure that your settings for these parameters and your application do not create a hazard of bodily injury or equipment damage. 34 Peer Node to Inp Yes No Determines the node address of the node producing I/O for the adapter to receive. Important: This parameter cannot be changed when the Peer Inp Enable (36) parameter is On. Important: For information on accessing and editing parameters, refer to Chapter 3, Configuring the 1203-GU6 Using a Serial Connection, or Chapter 4, Configuring the 1203-GU6 or 1336-GM6 Adapter Using RSNetWorx for DeviceNet.

103 Enhanced DeviceNet Adapter s Parameters B-15 # Name Valid Values/ Settings Default Writable Reset or Power Cycle Description 35 Peer Inp Time-out sec Yes No Determines the time out time. If the adapter does not receive input from the peer node in this amount of time, it will do what is selected in Peer Flt Action (33) parameter. 36 Peer Inp Enable Off, On Off Yes No Off = Disables peer input communications. On = Enables peer input communications. 37 Peer Inp Status Off Waiting Running Faulted 38 Peer A Output Off Cmd/Ref DL A Input DL B Input DL C Input DL D Input DL A Output DL B Output DL C Output DL D Output 39 Peer B Output Off Cmd/Ref DL A Input DL B Input DL C Input DL D Input DL A Output DL B Output DL C Output DL D Output NA No No Displays the status of the consumed peer input connection. Off Yes No Determines the source of peer A output data in the SCANport product. Important: This parameter cannot be changed when the Peer Out Enable (40) parameter is On. Off Yes No Determines the source of peer B output data in the SCANport product. Important: This parameter cannot be changed when the Peer Out Enable (40) parameter is On. 40 Peer Out Enable On, Off Off Yes No Off = Disables peer output communications. On = Enables peer output communications. 41 Peer Out Time Yes No Determines the minimum interval of time between peer transmissions. 42 Peer Out Skip Yes No Determines the maximum interval of time between peer transmissions by multiplying this value by the value in the Peer Out Time (41) parameter. Important: For information on accessing and editing parameters, refer to Chapter 3, Configuring the 1203-GU6 Using a Serial Connection, or Chapter 4, Configuring the 1203-GU6 or 1336-GM6 Adapter Using RSNetWorx for DeviceNet.

104 B-16 Enhanced DeviceNet Adapter s Parameters M-S Input Parameter Configurations The M-S Input (24) parameter has the following five configurable bits. Figure B.5 Bits and Corresponding I/O datalink C datalink D datalink B datalink A Cmd/Ref xxx0, = Peer or other input 1 = Master-Slave input When you enable Cmd/Stat (4) or datalink (5-8) parameter(s) in the adapter, you must set the corresponding bit in the M-S Input (24) parameter if you want the input data to come from the scanner or master device. The following table lists possible configurations for the M-S Input (24) parameter and the types of allocation associated with each. ADAPTER CONFIGURATION ALLOCATION (Number Of Words) Data Size Sent From The Controller To The Adapter M-S Input M-S Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic xxxx0 0 NA NA NA NA xxxx0 2 NA NA NA NA xxxx0 2 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 2 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 2 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 8 NA NA NA NA xxxx0 2 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 6 NA NA NA NA

105 Enhanced DeviceNet Adapter s Parameters B-17 ADAPTER CONFIGURATION ALLOCATION (Number Of Words) Data Size Sent From The Controller To The Adapter M-S Input M-S Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic xxxx0 4 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 8 NA NA NA NA xxxx0 4 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 8 NA NA NA NA xxxx0 6 NA NA NA NA xxxx0 8 NA NA NA NA xxxx0 8 NA NA NA NA xxxx0 10 NA NA NA NA xxxx /0 0/ xxxx /0 2/ xxxx /0 2/ xxxx /0 4/ xxxx /0 2/ xxxx /0 4/ xxxx /0 4/ xxxx /0 6/ xxxx /0 2/ xxxx /0 4/ xxxx /0 4/ xxxx /0 6/ xxxx /0 4/ xxxx /0 6/ xxxx /0 6/ xxxx /0 8/ xxxx /0 2/ xxxx /0 4/ xxxx /0 4/ xxxx /0 6/ xxxx /0 4/ xxxx /0 6/ xxxx /0 6/ xxxx /0 8/ xxxx /0 4/ xxxx /0 6/0

106 B-18 Enhanced DeviceNet Adapter s Parameters ADAPTER CONFIGURATION ALLOCATION (Number Of Words) Data Size Sent From The Controller To The Adapter M-S Input M-S Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic xxxx /0 8/ xxxx /0 6/ xxxx /0 8/ xxxx /0 8/ xxxx /0 10/0 M-S Output Parameter Configurations The M-S Output parameter has the following five configurable bits. Figure B.6 Bits and Corresponding I/O datalink C datalink D datalink B datalink A Stat/Fdbk xxx0, = Peer or other output When you enable Cmd/Stat (4) or datalink (5-8) parameter(s) in the adapter, you must set the corresponding bit in the M-S Output (25) parameter if you want the output data to be sent to the scanner or master device. The following table lists possible configurations for the M-S Output (25) parameter and the types of allocation associated with each. ALLOCATION (Number Of Words) M-S Output Data Size Sent From The Adapter To The Controller Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA

107 Enhanced DeviceNet Adapter s Parameters B-19 ALLOCATION (Number Of Words) M-S Output Data Size Sent From The Adapter To The Controller Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA /2 2/ /2 4/ /2 4/ /2 6/ /2 6/ /2 6/ /2 8/ /2 4/ /2 6/ /2 6/ /2 8/ /2 6/ /2 8/ /2 8/ /2 10/2

108 B-20 Enhanced DeviceNet Adapter s Parameters Notes:

109 Appendix C DeviceNet Objects Appendix Objectives Appendix C defines the DeviceNet object classes, class services, and attributes that are supported by the Enhanced DeviceNet adapter. These objects can be used to develop programs for the module. This appendix assumes that you have experience in object programming. Object Classes The Enhanced DeviceNet adapter supports the following object classes: Class Object Page 0x01 Identity C-2 0x02 Message Router C-4 0x03 DeviceNet C-5 0x05 Connection C-6 0x07 Register C-8 0x0F Parameter C-10 0x10 Parameter Group C-16 0x93 SCANport Pass-Through Parameter C-18 0x97 SCANport Pass-Through Fault Queue C-19 0x98 SCANport Pass-Through Warning Queue C-21 0x99 SCANport Pass-Through Link C-23 0x67 PCCC Object C-25

110 C-2 DeviceNet Objects Class Code 0x01 Identity Object The identity object provides identification and general information about the device. Class Attributes Attribute ID Access Rule Name Data Type Description 2 Get Max Instance UINT Maximum instance number of an object currently created in this class level of the device. Instances The total number of instances depends on the number of microprocessors in the SCANport product connected to the module. Instance 1 includes information on both the adapter and the product. The instances for the SCANport product s microprocessors start at instance 2. The instance for the adapter is present after all the instances for the SCANport product s microprocessors. Instance Description 1 Total Product 2 through n - 1 ➀ Product components n ➀ Enhanced DeviceNet Adapter ➀ The value of n is the maximum instance in the object. This value is obtainable via class attribute 2.

111 Instance Attributes DeviceNet Objects C-3 Attribute ID Access Rule Name Data Type Description 1 Get Vendor ID UINT Identification of each vendor by number. 1 = Allen-Bradley 2 Get Device Type UINT Indication of general type of product. 0x69 = Sub-Component 0x6F = SCANport Device 3 Get Product Code UINT Identification of a particular product of an individual vendor. 0xXX02 = 1336 PLUS HP -S/B 0xXX02 0xXX03 = 1336 PLUS HP -S/B 0xXX03 0xXX07 = 1336 PLUS II -S/B 0xXX07 0xXX10 = 1336 FORCE w/ PLC Adapter -S/B 0xXX10 0xXX11 = 2364F RGU -S/B 0xXX11 0xXX12 = 1394 Motion Drive -S/B 0xXX12 0xXX13 = 1557 Medium Voltage AC Drive -S/B 0xXX13 0xXX14 =193 SMP-3 -S/B 0xXX14 0xXX15 = 150 SMC Dialog Plus -S/B 0xXX15 0xXX17 = 1305 AC Drive -S/B 0xXX17 0xXX18 = 1397 DC Drive -S/B 0xXX18 0xXX19 = 1336 VSC -S/B 0xXX19 0xXX20 = 1336T Force w/ Std Adapter -S/B 0xXX20 0xXX22 = 1336 IMPACT -S/B 0xXX22 Note: The high byte of each code indicates a particular size or configuration within a product family. 4 Get Revision Major Revision STRUCT of USINT Revision of the item that this instance of the Identity Object represents. Value varies based on product. Minor Revision USINT 5 Get Status WORD Summary status of product. Value varies based on product. 6 Get Serial Number UDINT Serial number of product. Value varies based on product. 7 Get Product Name SHORT_ STRING Human readable identification. Value varies based on product. Common Services Implemented for: Service Code Service Name Class Instance 0x05 Yes No Reset 0x0E Yes Yes Get_Attribute_Single 0x10 No No Set_Attribute_Single 0x11 Yes N/A Find_Next_Obj_Instance Get_Attribute_All Response None supported.

112 C-4 DeviceNet Objects Class Code 0x02 Message Router Object The Message Router Object provides a messaging connection point through which a client may address to any object class or instance residing in the physical devices. Class Attributes Not supported. Instances Instance Description 1 Message Router Object Instance Attributes Attribute ID Access Rule Name Data Type Description 2 Get Number available 3 Get Number active 4 Get Active connections UINT UINT ARRAY of UINT Maximum number of connections supported by the message router. Number of connections currently used by system components. A list of the connection IDs of the currently active connections. This attribute not used. Reserved for compatibility purposes. Common Services Service Code Class Implemented for: Instance Service Name 0x0E Yes Yes Get_Attribute_Single

113 Class Code 0x03 DeviceNet Object DeviceNet Objects C-5 The DeviceNet Object is used to provide the configuration and status of a physical attachment to DeviceNet. A product must support one (and only one) DeviceNet Object per physical network attachment. Class Attributes Attribute ID Access Rule Name Data Type Description 1 Get DeviceNet Specification Word Returns 2 Instances Not supported. Instance Attributes Attribute ID Access Rule Name Data Type Description 1 Get Mac ID USINT Node Address 2 Get Data Rate USINT Data Rate 3 Get BOI BOOL Default = 0 4 Set Bus Off Counter 5 Get Allocation Information 6 Get Node Adx Switch Err 7 Get Data Rate Switch Err 8 Get Node Adx Switch 9 Get Data Rate Switch Val USINT STRUCT of BYTE USINT BOOL BOOL USINT USINT Increments if BOI is non-zero and Bus Off occurs. Can only be set to zero. The allocation information a slave supports when the master allocates. If non-zero, the Node Address NVS value does not match the online value. If non-zero, the Data Rate NVS value does not match the online value. The actual value in the EEPROM The actual value in the EEPROM or the operating value after an autobaud was completed. Common Services Not supported.

114 C-6 DeviceNet Objects Class Code 0x05 Connection The Connection Class allocates and manages the internal resources associated with both I/O and Explicit Messaging Connections. The specific instance generated by the Connection Class is referred to as a Connection Instance or a Connection Object. Important: An externally visible interface to the Connection Class across Explicit Messaging Connections DOES exist. Unless otherwise noted, all services/attributes noted in the following sections are accessible using Explicit Messaging. A Connection Object within a particular module actually represents one of the end-points of a Connection. It is possible for one of the Connection end-points to be configured and active (e.g., transmitting) without the other end-point(s) being present. Connection Objects are used to model the communication specific characteristics of a particular Application-to-Applications(s) relationship. A specific Connection Object Instance manages the communication-specific aspects related to an end-point. A Connection Object on DeviceNet uses the services provided by a Link Producer and/or Link Consumer to perform low-level data transmission and reception functions. Class Attributes Attribute ID Access Rule Name Data Type Description 1 Get Revision UINT Revision of the Connection Object class definition upon which the implementation is based Range Instances Instance Description 1 Group 2 Messaging 2 Group 2 Polling 4 Group 2 COS/Cyclic 6 Group 3 Messaging 7 Group 3 Messaging 8 Group 3 Messaging 9 Group 3 Messaging 10 Group 3 Messaging

115 Instance Attributes DeviceNet Objects C-7 Attribute ID Access Rule Name Data Type Description 1 Get State USINT State of the connection as defined in the DeviceNet specification 2 Get Instance type USINT Indicates I/O or Messaging connection 3 Get Transport Class Trigger USINT The Transport Class Trigger for this instance 4 Get Produced Cnxn ID USINT CAN Identifier to transmit on 5 Get Consumed Cnxn ID USINT CAN Identifier to receive on 6 Get Initial Comm Char USINT Defines the DeviceNet message groups that the tx/rx Cnxn s apply 7 Get Produced Cnxn Size UINT Max bytes to transmit across this connection 8 Get Consumed Cnxn Size UINT Max bytes to receive across this connection 9 Get/Set EPR UINT Expected Packet Rate 12 Get/Set Watchdog Action USINT How to handle inactivity/watchdog time-outs 13 Get Produced Path Length UINT Number of bytes in the produced connection path attribute 14 Get Produced Cnxn Path ARRAY of USINT Specifies the application object whose data is to be produced by this connection 15 Get Consumed Path Length UINT Number of bytes in the consumed connection path attribute 16 Get Consumed Cnxn Path ARRAY of USINT Specifies the application object to receive the data consumed by this application 17 Get/Set Production Inhibit Time UINT Defines minimum time between new data production for COS connections Common Services Not supported.

116 C-8 DeviceNet Objects Class Code 0x07 Register Object The Register Object is used to address individual bits or a range of bits. It may operate as either a producer (input) register or a consumer (output) register. A producer register object produces data onto the network. A consumer register object consumes data from the network. Message writes to the Register Object can perform control functions. Therefore, message writes are only allowed when the controller is not actively controlling the module and the message write is done through a connection with a time-out value not equal to zero. Writes cannot be performed through an unconnected message. After a write, any time-out or closure of the connection may cause the SCANport product to fault. Refer to Chapter 7, Using DeviceNet Explicit Messaging, for information about writing to the Register Object. Class Attributes Not supported. Instances Instance Description 1 All polled data being read from the SCANport device (read-only) 2 All polled data written to the SCANport device (read/write) 3 Logic Status and Feedback data (read-only) 4 Logic Command and Reference data (read/write) 5 Datalink A input data (read-only) 6 Datalink A output data (read/write) 7 Datalink B input data (read-only) 8 Datalink B output data (read/write) 9 Datalink C input data (read-only) 10 Datalink C output data (read/write) 11 Datalink D input data (read-only) 12 Datalink D output data (read/write) 13 Logic Status and Feedback Data (read-only) 14 Logic Command and Reference Data ➀ (read/write) ➀ The command word is set to the value of the first word of the data where there are ones in the second word of the data. Command = (word 1 and not word 2) or (word 1 and word 2). This only controls specified bits in the logic command data to the SCANport product and does not change the reference value.

117 Instance Attributes DeviceNet Objects C-9 Setting of an assembly attribute can only be accomplished through a connection. This feature is to prevent accidental control of the SCANport product. Attribute ID Access Rule Name Data Type Description 1 Get Bad Flag BOOL If set to 1, then attribute 4 may contain invalid, bad or otherwise corrupt data. 0 = good 1 = bad 2 Get Direction BOOL Direction of data transfer 0 = Producer Register 1 = Consumer Register 3 Get Size UINT Size of register data in bits 4 Conditional ➀ Data ARRAY of BITS Data to be transferred ➀ The access rule of Set is optional if attribute 2, Direction = 1. If Direction = 0, the access rule is Get. Common Services Service Code Class Implemented for: Instance Service Name 0x0E Yes Yes Get_Attribute_Single 0x10 No Yes Set_Attribute_Single

118 C-10 DeviceNet Objects Class Code 0x0F Parameter Object The Parameter Object provides a known, public interface for device configuration data. This object also provides all the information necessary to define and describe each individual configuration parameter of a device. Class Attributes Attribute ID Access Rule Name Data Type Description 1 Get Revision UINT Revision of this object. First revision, value = 1. 2 Get Max Instance UINT Maximum instance number of an object currently created in this class level of the device. 8 Get Parameter Class Descriptor 9 Get Configuration Assembly Instance 10 Set Native Language WORD UINT USINT Bits that describe parameters. Instance number of the configuration assembly. This attribute is set to zero because a configuration assembly is not supported. Language ID for all character array accesses. 0 = English 1 = French 2 = Spanish 3 = Italian 4 = German 5 = Japanese 6 = Portuguese Instances The number of instances varies based on the number of parameters in your SCANport product. The adapter parameters immediately follow the SCANport product parameters. Instance Description 1 through n - 42 ➀ SCANport Product Parameters n - 41 through n ➀ Module Parameters ➀ The value of n is the maximum instance in the object. This value is obtainable via class attribute 2.

119 Instance Attributes DeviceNet Objects C-11 Attribute ID Access Rule Stub/Full Name Data Type Description 1 ➀ Stub Parameter Value Specified in Descriptor, Data Type and Data Size attributes. Actual value of parameter. Data type specified in descriptor, data type, and data size. ➀➁ 2 Get Stub Link Path Size USINT Size of Link Path attribute. If this attribute is 0, then no link is specified. Number of BYTEs in attribute 3. 3 Get Stub Link Path ARRAY of path segments Segment type/port Segment Address BYTE Path (format depends on data contained in segment type/port) Path to the object from where this parameter value is retrieved. The link path is limited to 255 BYTEs. 4 Get Stub Descriptor WORD Descriptor of parameter. Refer to the table on page C Get Stub Data Type USINT Data type code. Refer to the table on page C Get Stub Data Size USINT Number of BYTEs in attribute 1, Parameter Value. 7 Get Full Parameter Name String SHORT_ STRING 8 Get Full Units String SHORT_ STRING 9 Get Full SHORT_ STRING 10 Get Full Minimum Value Same as attribute 1 11 Get Full Maximum Value Same as attribute 1 12 Get Full Default Value Same as attribute 1 A human readable string representing the parameter name. For example, frequency #1. The maximum number of characters is 16. (The first byte is a length code.) Engineering unit string. The maximum number of characters is 4. (The first byte is a length code.) The maximum number of characters is 64. (The first byte is a length code.) Always returns 0. The minimum valid actual value to which attribute 1, Parameter Value can be set. The maximum valid actual value to which attribute 1, Parameter Value can be set. The actual value attribute 1, Parameter Value should be set to when the user wants the default for the parameter. 13 Get Full Scaling Multiplier UINT Multiplier for scaling formula. 14 Get Full Scaling Divisor UINT Divisor for scaling formula. ➀ ➁ The access rule is defined in bit 4 of instance attribute 4, the Descriptor. If bit 4 is 0 the access rule is Set and the Parameter Value can be read and written. If bit 4 is 1, the access rule is Get and the Parameter Value can only be read. Data type specified in instance attributes 4 (Descriptor), 5 (Data Type) and 6 (Data Size).

120 C-12 DeviceNet Objects Attribute ID Access Rule Stub/Full Name Data Type Description 15 Get Full Scaling Base UINT Base for scaling formula. 16 Get Full Scaling Offset UINT Offset for scaling formula. 17 Get Full Multiplier Link UINT Parameter object instance number of multiplier source. 18 Get Full Divisor Link UINT Parameter object instance number of base source. 19 Get Full Base Link UINT Parameter object instance number of offset source. 20 Get Full Offset Link UINT Parameter object instance number of offset source. 21 Get Full Decimal Precision USINT Specifies number of decimal places to use when displaying the scaled engineering value. Also used to determine actual increment value so that incrementing a value causes a change in scaled engineering value to this precision. ➀ ➁ The access rule is defined in bit 4 of instance attribute 4, the Descriptor. If bit 4 is 0 the access rule is Set and the Parameter Value can be read and written. If bit 4 is 1, the access rule is Get and the Parameter Value can only be read. Data type specified in instance attributes 4 (Descriptor), 5 (Data Type) and 6 (Data Size). Bit Definitions for Instance Attribute 4 Bit Definition Value 0 Supports settable path 0 = Link path can not be set. 1 = Link path can be set. 1 Supports enumerated strings 0 = Enumerated strings are not supported. 1 = Enumerated strings are supported and may be read with the Get_Enum_String service. 2 Supports scaling 0 = Scaling not supported. 1 = Scaling is supported. The scaling attributes are implemented and the value presented is in engineering units. 3 Supports scaling links 0 = Scaling links not supported. 1 = The values for the scaling attributes may be retrieved from other parameter object instances. 4 Read only parameter 0 = Parameter value attribute can be written (set) and read (get). Access rule is set. 1 = Parameter value attribute can only be read. Access rule is get. 5 Monitor parameter 0 = Parameter value attribute is not updated in real time by the device. 1 = Parameter value attribute is updated in real time by the device. 6 Supports extended precision scaling 0 = Extended precision scaling is not supported. 1 = Extended precision scaling should be implemented and the value presented to the user in engineering units.

121 Data Types for Instance Attribute 5 DeviceNet Objects C-13 Attribute ID Value Definition Data Type Description Scaling Supported on this Data Type 1 WORD 16-bit word No 2 UINT 16-bit unsigned integer Yes 3 INT 16-bit signed integer Yes 4 BOOL Boolean No 5 SINT Short integer Yes 6 DINT Double integer Yes 7 LINT Long integer Yes 8 USINT Unsigned short integer Yes 9 Not Supported Unsigned double integer Yes 10 Not Supported Unsigned long integer Yes 11 Not Supported Single floating point format (IEEE 754) 12 Not Supported Double floating point format (IEEE 754) Yes Yes 13 Not Supported Duration (short) Yes 14 Not Supported Duration Yes 15 Not Supported Duration (high resolution) Yes 16 Not Supported Duration (long) Yes 17 Not Supported Date No 18 Not Supported Time of Day No 19 Not Supported Date and time No 20 Not Supported 8-bit per character string 21 Not Supported 16-bit per character string 22 Not Supported N-byte per character string 23 Not Supported Short N-byte character string No No No No 24 Not Supported 8-bit string No 25 Not Supported 32-bit string No 26 Not Supported 64-bit string No

122 C-14 DeviceNet Objects Common Services Service Code Class Implemented for: Instance Service Name 0x01 No Yes Get_Attribute_All 0x0E Yes Yes Get_Attribute_Single 0x10 No Yes Set_Attribute_Single 0x4B No Yes Get_Enum_String 0x05 Yes No Reset_Request (sets all parameters to default values) 0x15 Yes No Restore_Request 0x16 Yes No Save_Request Get_Attribute_All Response Not supported. At the instance level, the order of attributes returned in the Get_Attributes_All response is as follows: Class Attribute ID Attribute Name and Default Value 1 Parameter Value 2 Link Path Size 3 Link Path 4 Descriptor 5 Data Type 6 Data Size 7 Parameter Name String, default character count = 0 8 Units String, default character count = 0 9 Help String, default character count = 0 10 Minimum Value default = 0 11 Maximum Value default = 0 12 Default Value default = 0 13 Scaling Multiplier Default = 1 14 Scaling Divisor Default = 1 15 Scaling Base Default = 1 16 Scaling Offset Default = 0 17 Multiplier Link Default = 0 18 Divisor Link Default = 0 19 Base Link Default = 0 20 Offset Link Default = 0

123 DeviceNet Objects C-15 Class Attribute ID Attribute Name and Default Value 21 Decimal Precision Default = 0 Object Specific Services Service Code Class Implemented for: Instance Service Name 0x4B No Yes Get_Enum_String Enumerated strings are human-readable strings that describe either a bit or a value depending on the data type of instance attribute 1, the Parameter Value. If the data type is a BYTE or WORD, the enumerated string is a bit enumerated string. If the data type is INT or UINT, the enumerated string is a value enumerated string. Any other data type does not have enumerated strings. The table below lists the parameters for the Get_Enum_String request service. Name Data Type Description of Attribute Enumerated String Number USINT Number of enumerated string to retrieve (MAX value is 255). If the string to be returned is a bit enumerated string, then the enumerated string number represents a bit position and the Get_Enum_String service returns a string from that bit. If the string to be returned is a value enumerated string, then the enumerated string number represents a value and the Get_Enum_String service returns a string for that value. The enumerated string is returned in the form of a SHORT_STRING and is 16 characters long plus the preceding length byte.

124 C-16 DeviceNet Objects Class Code 0x10 Parameter Group Object The Parameter Group Object identifies and provides access to groups of parameters in a device grouping. The Parameter Group Object provides convenient access to related sets of parameters. Class Attributes Attribute ID Access Rule Name Data Type Description 1 Get Parameter group version UINT Returns 1 2 Get Max Instance UINT Maximum instance number of an object currently created in this class level of the device. 8 Get Native Language USINT Language ID for all STRING accesses. 0 = English 1 = French 2 = Spanish (Mexican) 3 = Italian 4 = German 5 = Japanese 6 = Portuguese Instances The number of instances varies based on the number of groups in the SCANport product. One additional group is added for the module. Instance Description 1 (n - 1) SCANport product groups n ➀ Module group ➀ n is the value returned by a get from class attribute 2 (max instance). Instance Attributes Attribute ID Access Rule Name Data Type Description 1 Get Group Name String SHORT_ STRING 2 Get Number of Members in Group 3 Get 1st Parameter Number in Group 4 Get 2nd Parameter Number in Group n Get (n-2)th Parameter Number in Group UINT UINT UINT UINT A human-readable string representing the group name (e.g., set-up, frequency set). Maximum number of characters = 16 Number of parameters in group. Parameter instance number. Parameter instance number. Parameter instance number.

125 Common Services DeviceNet Objects C-17 Service Code Class Implemented for: Instance Service Name 0x0E Yes Yes Get_Attribute_Single Get_Attribute_All Response Not supported.

126 C-18 DeviceNet Objects Class Code 0x93 SCANport Pass-Through Parameter Object The SCANport Pass-Through Parameter Object lets you perform a scattered read or write. Class Attributes Not supported. Instance Attributes Not supported. Common Services Not supported. Object-Specific Services Service Code Class Implemented for: Instance Service Name 0x32 Yes No 0x34 Yes No Scattered_Parameter_ Value_Read ➀ Scattered_Parameter_ Value_Write ➀ ➀ Must be directed to Attribute 0, Instance 0. The table below lists the parameters for the Scattered_Parameter_ Value_Read and Scattered_Parameter_Value_Write object-specific services: Name Data Type Description Scattered Parameters STRUCT of Parameter Number WORD Parameter to read or write Parameter Value WORD Parameter value to write (zero when reading) Important: The STRUCT may repeat up to 32 times in a single message.

127 DeviceNet Objects C-19 Class Code 0x97 SCANport Pass-Through Fault Object The SCANport Pass-Through Fault Object provides information on the product s fault queue. Class Attributes Attribute ID Access Rule Name Data Type Description 0 Set Write Fault Command BYTE 1 = Clear Faults 2 = Clear Fault Queue 3 = Reset Product 1 Get Read Number of Fault BYTE Reads the number of fault queue entries. Queue Entries 2 Get Read Fault Queue Trip Index BYTE Reads the index of the fault that tripped the product. Instance Attributes Attribute ID Access Rule Name Data Type Description ➀ ➁ 0 Get Read Fault Queue Entry Full/All Info STRUCT of Fault Text ARRAY of BYTE 16 character string (no length information, no terminating null). Fault Code WORD Fault Code. Fault Time Stamp STRUCT BYTE 1/100 Second (0 99). BYTE Second (0 59). BYTE Minute (0 59). BYTE Hour (0 23). BYTE Day of Week (0 6). ➀ BYTE Date (1 31). BYTE Month (1 12). BYTE Year (0 99 ➁ ). 128 Get Fault Code and Time Stamp STRUCT of Fault Code WORD Fault Code. Fault Time Stamp STRUCT of BYTE 1/100 Second (0 99). BYTE Second (0 59). BYTE Minute (0 59). BYTE Hour (0 23). BYTE Day of Week (0 6). ➀ 129 Get Read Fault Text String Only Sunday is a value of zero. Year is an offset from BYTE Date (1 31). BYTE Month (1 12). BYTE Year (0 99 ➁ ). ARRAY of BYTE 16 character string (no length information, no terminating null).

128 C-20 DeviceNet Objects Common Services Implemented for: Service Code Service Name Class Instance 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single

129 DeviceNet Objects C-21 Class Code 0x98 SCANport Pass-Through Warning Object The SCANport Pass-Through Warning Object provides information on the product s warning queue. Class Attributes Attribute ID Access Rule 0 Set Write Warning Command 1 Set Read Number of Warning Queue Entries Instance Attributes Name Data Type Description BYTE BYTE Write Warning Command. 1 = Clear Warnings 2 = Clear Warning Queue 3 = Reset Product Attribute ID Access Rule 0 Get Read Warning Queue Entry Full/All Info Name Data Type Description Warning Text Warning Code Warning Time Stamp (Time Stamps not available in all products) ➀ Sunday is a value of zero. ➁ Year is an offset from STRUCT of ARRAY of BYTE WORD STRUCT 16 character string (no length information, no terminating null). Fault Code. BYTE 1/100 Second (0 99). BYTE Second (0 59). BYTE Minute (0 59). BYTE Hour (0 23). BYTE Day of Week (0 6). ➀ BYTE Date (1 31). BYTE Month (1 12). BYTE Year (0 99 ➁ ).

130 C-22 DeviceNet Objects Attribute ID Access Rule 128 Get Warning Code and Time Stamp (Time Stamps not available in all products) Common Services Warning Code Warning Time Stamp (Time Stamps not available in all products) 129 Get Read Warning Text String Only ➀ Sunday is a value of zero. ➁ Year is an offset from Name Data Type Description STRUCT of WORD STRUCT of Fault Code. BYTE 1/100 Second (0 99). BYTE Second (0 59). BYTE Minute (0 59). BYTE Hour (0 23). BYTE Day of Week (0 6). ➀ BYTE Date (1 31). BYTE Month (1 12). BYTE Year (0 99 ➁ ). ARRAY of BYTE 16 character string (no length information, no terminating null). Service Code Class Implemented for: Instance Service Name 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single

131 Class Code 0x99 SCANport Pass-Through Link Object DeviceNet Objects C-23 The SCANport Pass-Through Link Object lets you perform a scattered read or write of a number of links or a single read or write of a link. Class Attributes Attribute ID Access Rule Name Data Type Description 0 Set Link Command BYTE 1 = Clear all links. 1 Get NVS Link Diagnostic Value WORD Checksum. Instance Attributes An instance in this class is the number of a parameter that is to get its value from another parameter. Attribute ID Access Rule Name Data Type Description 0 Set Parameter Link Reference ➀ WORD ➀ The Parameter Link Reference value is the number of the parameter whose value is to be transferred. Common Services Implemented for: Service Code Service Name Class Instance 0x0E Yes Yes Get_Attribute_Single 0x10 Yes Yes Set_Attribute_Single Object-Specific Services Implemented for: Service Code Class Instance 0x32 Yes No 0x34 Yes No Service Name Scattered_Link_ Reference_Value_Read ➀ Scattered_Link_ Reference_Value_Write ➀ ➀ Must be directed to Attribute 0, Instance 0.

132 C-24 DeviceNet Objects The table below lists parameters for Scattered_Link_Reference_Read and Scattered_Link_Reference_Write object-specific services. Name Data Type Description Scattered Link Read/Write STRUCT of Parameter Number WORD Parameter Link Reference to read or write. Parameter Link Reference WORD Link Reference value to write (zero when reading). Important: The STRUCT may repeat up to 32 times in a single message.

133 Class Code 0x67 PCCC Object DeviceNet Objects C-25 The PCCC Object is used to process encapsulated PCCC messages from DeviceNet. The PCCC Object does not implement any specific class or instance attributes, so the instance field for any received messages is ignored. Class Attributes Not supported. Instance Attributes Not supported. Common Services Not supported. Object Specific Services Service Code Class Implemented for: Instance Service Name 0x4B No Yes Execute_PCCC 0x4D No Yes Execute_Local_PCCC Message Structure for Execute_PCCC Request Response Name Data Type Description Name Data Type Description Length USINT Length of requestor ID Length USINT Length of requestor ID Vendor UINT Vendor number of requestor Vendor UINT Vendor number of requestor Serial Number UDINT ASA serial number of requestor Serial Number UDINT ASA serial number of requestor Other Product Specific Identifier of user, task, etc. on the requestor Other Product Specific Identifier of user, task, etc. on the requestor CMD USINT Command byte CMD USINT Command byte STS USINT 0 STS USINT Status byte TNSW UINT Transport word TNSW UINT Transport word. Same value as the request. FNC USINT Function code. Not used for all CMD s. PCCC_params ARRAY of USINT CMD/FNC specific parameters PCCC_results ARRAY of USINT EXT_STS USINT Extended status. Not used for all CMD s. CMD/FNC specific result data

134 C-26 DeviceNet Objects Message Structure for Execute_Local_PCCC Request Response Name Data Type Description More Information Name Data Type Description CMD USINT Command byte CMD USINT Command byte STS USINT 0 STS USINT Status byte TNSW UINT Transport word TNSW UINT Transport word. Same value as the request. FNC USINT Function code. Not used for all CMD s. PCCC_params ARRAY of USINT CMD/FNC specific parameters PCCC_results ARRAY of USINT EXT_STS USINT Extended status. Not used for all CMD s. CMD/FNC specific result data For more information on PCCC messages, refer to Appendix D, Supported PCCC Messages.

135 Appendix D Supported PCCC Messages Appendix Objectives Appendix D describes the PCCC object, which allows existing PLC-type controllers to connect to the DeviceNet network. In this appendix, you will learn about the following: DF-1/PCCC support (1203-GU6 only). A list of supported PCCC messages. DF-1/PCCC Support (1203-GU6 Only) The 1203-GU6 translates PCCC messages into SCANport messages between the SCANport device and the module. To communicate to the SCANport device, you need: A PC running software that can communicate and translate the DF-1/PCCC messages supported by the module. A modem that supports full duplex communication (if you re connecting the modem to a serial port that utilizes point-to-point DF-1 full duplex protocol at selected baud rates).

136 D-2 Supported PCCC Messages Supported PCCC Messages The 1203-GU6 and 1336-GM6 support the following PCCC messages: CMD FNC Message Definition Supported? 0x06 0x03,4,5,0,1 Identify Host and Some Status Yes 0x0F 0x67 PLC-5 Typed Write Yes 0x0F 0x68 PLC-5 Typed Read Yes Logical ASCII Address Logical Binary Address PLC-2 System Address PLC-3 Symbolic Address Yes No No No 0x0F 0xA1 SLC-500 Protected Typed Logical Read w/ 2 Address Fields File, Element No 0x0F 0xA2 SLC-500 Protected Typed Logical Read w/ 3 Address Fields File, Element, Sub-Element Yes 0x0F 0xA9 SLC-500 Protected Typed Logical Write w/ 2 Address Fields File, Element No 0x0F 0xAA SLC-500 Protected Typed Logical Write w/ 3 Address Fields File, Element, Sub-Element 0x0F 0xAB SLC-500 Protected Typed Logical Write w/ 4 Address Fields File, Element, Sub-Element, Bit Mask Yes No 0x0F 0x95 Encapsulate Other Protocol message Yes Related Documentation For more information on PCCC messages, refer to the DF1 Protocol and Command Set Reference Manual, publication

137 Appendix E N-File Addresses Appendix Objectives N-File Addresses Appendix E provides information on the N-File addresses used when accessing the PCCC object or the DF-1 serial port. When using messages, you can use the N-file addresses to locate information about the adapter or SCANport product. The 1203-GU-6 and 1336-GM6 support the N-file addresses shown below: Address N-File Addresses N10:0 Number of SCANport product parameters N10:1 999 SCANport product parameters (value only) N11:0 999 SCANport product parameters (value only) N12:0 999 SCANport product parameters (value only) N13:0 Number of SCANport adapter parameters N13:1 999 SCANport adapter parameters (value only) N30:1 999 SCANport product parameters (all information read only) N31:1 999 SCANport product parameters (all information read only) N32:1 999 SCANport product parameters (all information read only) N33:1 999 SCANport adapter parameters (all information read only) N40:0 63 Block Transfer Emulation file N42: Gx2 Firmware Emulation Version The firmware version of the 1203-Gx2 this adapter emulates for DriveTools compatibility. N42:6 Max Network Node The maximum DeviceNet Node Number N42:7 Adapter Port # The SCANport adapter port number the adapter is connected to on the SCANport product N42:8 Reserved for future use Always zero

138 E-2 N-File Addresses Address N-File Addresses N50:0 Number of SCANport product parameters N50:1 249 SCANport product parameters (value only) N51:0 249 SCANport product parameters (value only)... N61:0 249 SCANport product parameters (value only) N90:1 249 SCANport product parameters (value only) N91:0 249 SCANport product parameters (value only)... N101:0 249 SCANport product parameters (value only)

139 Appendix F Supported Emulated Block Transfer Commands Appendix Objectives Appendix F provides information about the Emulated Block Transfer commands supported by the DeviceNet adapter. In this appendix, you will learn about the following: Emulated block transfer commands. Emulated block transfer error response. Setting up data files for listed emulated block transfer commands. Examples of each emulated block transfer command listed. What is Emulated Block Transfer? Emulated block transfer is a method used by some SCANport peripherals to read and write information using PCCC messages. Some Allen-Bradley DeviceNet products can send PCCC messages. Other products can send PCCC messages using a DF-1 connection. This appendix assumes that you have experience using emulated block transfer commands with SCANport peripherals.! ATTENTION: Hazard of equipment damage exists. If explicit messages are programmed to frequently write parameter data to certain drive products, the EEPROM (Non-Volatile Storage) will quickly exceed its life cycle and cause the product to malfunction. Do not create a program that frequently uses explicit messages to write parameter data to a product. Datalinks do not write to the EEPROM and should be used for frequently changed parameters. Supported Emulated Block Transfer Commands The following table lists the supported emulated block transfer commands and where you can find more information on them. Command Page Command Page Parameter Value Read ➀ F-3 NVS Functions F-14 Parameter Value Write ➀ F-4 Fault Command Write ➀ F-15 Parameter Read Full ➀ F-5 Fault Queue Entry Read Full ➀ F-16 Product ID Number Read ➀ F-8 Fault Queue Size ➀ F-18 Scattered Parameter Read Value F-10 Trip Fault Queue Number ➀ F-19 Scattered Parameter Write Value F-12 ➀ This function can be accessed in the module and product. The following examples describe how to access it in the product. To do so in the module, add to the decimal value of header word 2.

140 F-2 Supported Emulated Block Transfer Commands Emulated Block Transfer Status Word When an operation is unsuccessful, header word 2 of the drive response contains a negative value (bit 15 = 1). If an error occurs, the drive also returns a status word to indicate the reason for the failure. The location of the status word is typically header word 4 in the drive response, but will depend on the message. Figure F.1 Example Message Structure and Error Message Reply PLC Request Message Length Header Word 0 4 Header 1 Header Word 1 Header 2 Header Word 2 Data Data Word 3 Drive Response Message Length Header Word 0 Header 1.OR.0x8000 Header Word 1 Header 2 Header Word 2 Error Code Header Word 3 The following table lists the error codes. Value Description 0 No error occurred. 1 The service failed due to an internal reason, and the drive could not perform the request. 2 The requested service is not supported. 3 An invalid value in the block transfer emulation request header word 2. 4 An invalid value in the block transfer emulation request header word 3. 5 An invalid value in the block transfer emulation request header word 2. 6 The data value is out of range. 7 There is a drive state conflict. The drive is in an incorrect state to perform the function. The drive cannot be running when you perform certain functions.

141 Parameter Value Read Supported Emulated Block Transfer Commands F-3 Parameter Value Read reads the 16-bit parameter data value for the selected parameter number. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 3 words Drive response instruction length: 1 word Figure F.2 Message Structure Message Length 3 PLC Decimal Value 769 Parameter Number (See Drive List) PLC Request Header Word 0 Header Word 1 Header Word 2 Drive Response Header 0 Header Word 0 PLC Decimal Value Header Word 1 769=OK 31999=Error Header 2 Header Word 2 Parameter Value or Status Word Data Word 3 Message Operation Parameter Value Read reads parameter values from the drive and places that value (or an error code) in word 3 of the drive response data file. The value is shown in device units. Device units are listed in the user manual for the device you are using. If an error occurs: Word 3 of the response contains the status code. The status area of the data file is non-zero. Example In this example, the value of parameter 20 was requested from a 1336 PLUS drive and a value of 4096 was returned is the internal drive unit value for Maximum Rated Voltage. This corresponds to a value of 100% Drive Rated Volts in Display Units. Data File Format PLC request * Drive response * 4069* * Example only These values vary depending on parameters and products.

142 F-4 Supported Emulated Block Transfer Commands Parameter Value Write Parameter Value Write writes a 16-bit parameter data value to the selected parameter number. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 1 word Drive response instruction length: 4 words Figure F.3 Message Structure PLC Request Drive Response Message Length 4 PLC Decimal Value Parameter Number Header Word 0 Header Word 1 Data Word 2 Message Length 4 PLC Decimal Value 769 Message OK Message Error Parameter Number Header Word 0 Header Word 1 Data Word 2 Parameter Data Data Word 3 Status Word Data Word 3 Message Operation Parameter Value Write sends a new value to the specified parameter. The value must be in device units. Units for each parameter are listed in the device manual. If an error has occurred, word 1 of the response returns a value of 31999, and word 3 contains a status code. Example In this example, a value of 4096 was sent to Parameter is in drive units and indicates a value of 100% Drive Rated Volts, as defined in P147, Drive Rated Volts. Data File Format PLC request * 4096* Drive response * * Example only These values vary depending on parameters and products.

143 Parameter Read Full Supported Emulated Block Transfer Commands F-5 Parameter Read Full provides all known attributes for the parameters requested. This information includes the parameter s current value, descriptor, multiply and divide value, base value, offset value, text string, group element reference, minimum value, maximum value, default value, and unit text string. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 3 words Drive response instruction length: 20 words Figure F.4 Message Structure PLC Request Message Length 3 PLC Decimal Value 768 Parameter Number (See Drive List) Header Word 0 Header Word 1 Header Word 2 Message Length 23 PLC Decimal Value 768 Message OK Message Error Parameter Number Header Word 0 Header Word 1 Data Word 2 Parameter Value or Status Word Data Word 3 Descriptor Data Word 4 Multiply Value Data Word 5 Divide Value Data Word 6 Base Value Data Word 7 Offset Value Data Word 8 Char 2 Char 1 Data Word 9 Char 4 Char 3 Data Word 10 Char 6 Char 5 Data Word 11 Parameter Text Char 8 Char 7 Char 10 Char 9 Data Word 12 Data Word 13 Char 12 Char 11 Data Word 14 Char 14 Char 13 Data Word 15 Char 16 Char 15 Data Word 16

144 F-6 Supported Emulated Block Transfer Commands Figure F.4 Message Structure (Continued) Drive Response Unit Text File, Group, Element Minimum Value Maximum Value Default Value Char 2 Char 1 Char 4 Char 3 Data Word 17 Data Word 18 Data Word 19 Data Word 20 Data Word 21 Data Word 22 Message Operation Parameter Read Full retrieves the attributes of the specified parameter. The attributes for each parameter include the data, minimum and maximum values, and the parameter text. The response message returns this information. If an error has occurred in reading any of the values, word 3 contains the status word. The parameter text is returned with each data word containing two ASCII characters per word. The first and second characters are in opposite order. Example In this example, a Parameter Read Full was performed through block transfer on a 1336 PLUS drive. N10:10 shows the header message for the request. The data is returned in the response data file, starting with word 3, for parameter 20. Word 3 shows the present value in drive units. Word 4 through word 8 provide scaling information, used to convert drive units to engineering units for the Human Interface Module (HIM). Word 9 through word 16 provide the parameter name.

145 Supported Emulated Block Transfer Commands F-7 This example shows the response message in both binary and ASCII. Note the ASCII information beginning with word 9. The parameter name characters return in reverse order for each word. Word 9 has the ASCII value of (am). To read this, reverse the word to read (Ma). The next word (ix), reversed, gives you (xi). These words, along with the following two words, form the word Maximum. You can see the parameter name Maximum Voltage in word 9 through word 16 of the response message. In addition, words are also returned in this format. These words provide the units in which the parameter is defined. In this example it is vlts. Word 17 contains the file, group, and element which are used to reference the parameter. Words contain the minimum, maximum, and default values of this parameter. Data File Format PLC request * Drive response * 4096* 355* 1* 4096* 460* 0* 24909* (Decimal) 27000* 30061* 8301* 28502* 29804* 26465* 8293* 1794* 1024* 4915* 4096* 27734* 29556* Drive response \00\17 \03\00 \00\14 \10\00 \01 c \00\01 \10\00 \01\CC \00\00 a M (ASCII) i x u m m o V t l g a e \13 0 \10\00 l V s t * Example only These values vary depending on parameters and products.

146 F-8 Supported Emulated Block Transfer Commands Product ID Number Read Product ID Number Read returns the product ID of the device to which the DeviceNet adapter is connected. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 3 words Drive response instruction length: 4 words Figure F.5 Message Structure Message Length 3 PLC Decimal Value PLC Request Header Word 0 Header Word 1 Data Word 2 Drive Response Message Length 6 PLC Decimal Value 256 Message OK Message Error 0 Product ID Number Header Word 0 Header Word 1 Header Word 2 Data Word 3 Product Code (Hex) Product Code (Decimal) Bulletin Number Product 0x S 1336 PLUS Fractional HP 0x S 1336 PLUS 0x F 1336 PLUS II 0x T 1336 FORCE w/plc Adapter Board 0x F 2364 RGU DC Bus Regen Front End 0x Motion Drive 0x Medium Voltage AC Drive 0x SMP-3 0x SMC Dialog Plus 0x AC Drive 0x DC Drive 0x R 1336 Line Regeneration Package 0x T 1336 FORCE w/standard Adapter Board 0x E 1336 IMPACT

147 Supported Emulated Block Transfer Commands F-9 Message Operation Product ID Number Read, through the drive response message word 3, indicates the type of device the DeviceNet adapter is connected to. This value is defined in the message response chart shown above. If an error has occurred, word 1 of the response returns a negative value of Example In this example, the Product ID Number Read was requested. The drive response contained a value of 3 in word 3 of its message response, indicating a connection to a 1336 PLUS drive. Data File Format PLC request Drive Response * * Example only These values vary depending on parameters and products.

148 F-10 Supported Emulated Block Transfer Commands Scattered Parameter Value Read Scattered Parameter Value Read reads a scattered list of parameters. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 5 63 words Drive response instruction length: 5 63 words Figure F.6 Message Structure PLC Request Drive Response Message Length Header Word Message Length Header 5 63 Word 0 PLC Decimal Value Header Word 1 3 PLC Decimal Value Header 3 Message OK Message Error Word 1 Number of Parameter Header Word 2 Values to Read Number of Parameter Data Values to Read Word 2 Parameter Number Data Word 3 1 bit Parameter Number Data 15 0 Data Word 4 1 Word 3 Parameter Value or Data Status Word Parameter Number Data Word 5 1 Word 4 2 bit Parameter Number Data 0 Data Word Word 5 Parameter Value or Status Word Data Parameter Number Data Word 7 2 Word Parameter Number 30 Data Word 8 Data Word 61 bit Parameter Number 15 3 Parameter Value or Status Word 3 Data Word 7 Data Word 8 0 Data Word 62 bit Parameter Number Parameter Value or Status Word 30 Data Word 61 Data Word 62

149 Supported Emulated Block Transfer Commands F-11 Message Operation Scattered Parameter Value Read reads a predefined group of parameter values, in any order, from the device. You define the number of parameters to read in word 2 of the request. The parameters to be read and their order is defined starting with word 3. An unused word is left between each parameter request, so the drive can respond with the parameter value, as shown. If an error has occurred in reading any of the parameters: Word 1 of the drive response returns a value of Bit 15 of the drive response word for the number of that parameter is set. The drive response word for the value of that parameter returns a status word instead of returning the parameter value. Example In this example, eight parameters were read from a 1336 PLUS drive, as defined in word 2 of the request. Parameter numbers 5, 7, 8, 20, 18, 17, 19, and 36 were requested. The drive response returned the values of these parameters in the data file. These values are in drive units. Data File Format PLC request * 5* 0 7* 0 8* 0 20* 0 18* 0* 17* 0 19* 0 36* 0 Drive response * 5* 6* 7* 1000* 8* 1000* 20* 4096* 18* 4096* 17* 51* 19* 60* 36* 6144* * Example only These values vary depending on parameters and products.

150 F-12 Supported Emulated Block Transfer Commands Scattered Parameter Value Write Scattered Parameter Value Write writes to a scattered list of parameters and returns the status of each parameter. If any of the states have errors, the parameter number is negative. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 5 63 words Drive response instruction length: 5 63 words Figure F.7 Message Structure PLC Request Drive Response Message Length Header Word Message Length Header 5 63 Word 0 PLC Decimal Value Header Word PLC Decimal Value Header 3 Message OK Message Error Word 1 Number of Parameter Header Word 2 Values to Write Number of Parameter Data Parameter Number Values to Write Word 2 1 Data Word 3 Data bit Parameter Number Parameter Value 15 1 Word 3 1 Data Word 4 Data Status Word 1 Word 4 Parameter Number 2 Data Word 5 Data bit Parameter Number 15 2 Word 5 Parameter Value Data Word 6 2 Data Status Word 2 Word 6 Parameter Number Data Word 7 3 Parameter Value 3 Parameter Number 30 Parameter Value 30 Data Word 8 Data Word 61 Data Word 62 bit 15 bit 15 Parameter Number 3 Status Word 3 Parameter Number 30 Status Word 30 Data Word 7 Data Word 8 Data Word 61 Data Word 62

151 Supported Emulated Block Transfer Commands F-13 Message Operation Scattered Parameter Value Write writes data values to a predefined group of device parameters in any order. You define the number of parameters to write in word 2. The parameters to be written to and their order is defined starting with word 3. If an error occurs while writing to any of the parameters: Word 1 of the drive response returns a value of Bit 15 of the drive response word for that parameter s number is set. The drive response word for that parameter s status word is non-zero. If no error has occurred: Word 1 of the drive response returns a value of 3. Each of the drive response s parameter numbers are the same as in the request. Each of the drive response status words returns a value of 0. Example In this example, six parameters were written to in a 1336 PLUS drive. Word 2 of the request defines the number of parameter values that are transferred. Beginning with word 3, the message lists each parameter number followed by the value of the parameter. The values are entered in device units. The drive response returns the status of each parameter write. If the request was successful, a zero is returned. If an error has occurred, the response returns a status word code for the error. Data File Format PLC request * 90* 1* 150* 4* 30* 20* 31* 10* 10* 2* 12* 5* Drive response * 90* 0* 150* 0* 30* 0* 31* 0* 10* 0* 12* 0* * Example only These values vary depending on parameters and products.

152 F-14 Supported Emulated Block Transfer Commands NVS Functions NVS (Non-Volatile Storage) Functions activates the specified NVS functions. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 4 words Drive response instruction length: 3 words Figure F.8 Message Structure Message Length 4 PLC Decimal Value NVS Command PLC Request Header Word 0 Header Word 1 Header Word 2 Data Word 3 Drive Response Message Length 3 PLC Decimal Value 770 Message OK Message Error 0 Header Word 0 Header Word 1 Header Word 2 Value NVS Command Not Used NVS Save NVS Recall NVS Default Initialize Message Operation The NVS storage function allows three different message requests: NVS Save saves parameter information from the working memory or RAM to NVS Storage. NVS Recall retrieves the last saved data from NVS Storage and places it in the working memory or RAM. NVS Default Initialize clears the RAM and NVS Storage and sets all parameter values to default. If an error has occurred, response word 1 returns a value of Example This example requests the NVS Storage Save function be performed. Data File Format PLC request * 0, 1, 2, or 3 Drive response * * Example only These values vary depending on parameters and products.

153 Fault Command Write Supported Emulated Block Transfer Commands F-15 Fault Command Write activates the Clear Fault, Clear Fault Queue, and Drive Reset functions. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 4 words Drive response instruction length: 4 words Figure F.9 Message Structure PLC Request Drive Response Message Length Header Word 0 4 Message Length Header 4 PLC Decimal Value Word 0 Header Word 1 PLC Decimal Value Header 1792 Message OK Message Error Word 1 0 Header Word 2 Header 0 Word 2 Fault Command Data Word 3 Data Status Word Word 3 Value Fault Command Not Used Clear Fault Clear Fault Queue Drive Reset (1336 FORCE Only) Message Operation The specified fault Clear/Reset function sends a fault handling request to the device. A Clear Fault request clears the last fault that occurred. A Clear Fault Queue clears the entire fault buffer. Certain devices may store more than one fault. A Drive Reset is used with the 1336 FORCE drive product only. This function resets the drive; it clears the fault queue and writes the parameter information stored in NVS Storage to RAM. Data File Format PLC request , 1, 2, or 3 Drive response * * Example only These values vary depending on parameters and products.

154 F-16 Supported Emulated Block Transfer Commands Fault Queue Entry Read Full Fault Queue Entry Read Full reads the contents of the specified fault queue entry. A message is returned which includes the fault text and fault code associated with the specified fault queue entry. The 1336 FORCE drive also returns the time stamp associated with the fault. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 3 words Drive response instruction length: 12 or 16 words Figure F.10 Message Structure PLC Request Drive Response Message Length Header Word 0 3 Message Length Header 18 PLC Decimal Value Word 0 Header Word PLC Decimal Value Header 1792 Message OK Message Error Word 1 Fault Queue Entry Number Header Word 2 Fault Queue Header Entry Number Word 2 Fault Text Char 2 Char 1 Char 4 Char 3 Char 6 Char 5 Char 8 Char 7 Char 10 Char 9 Char 12 Char 11 Data Word 3 Data Word 4 Data Word 5 Data Word 6 Data Word 7 Data Word 8 Char 14 Char 13 Char 16 Char 15 Fault Code Value SES REF Data Word 9 Data Word 10 Data Word 11 Data Word FORCE Drive Only Clock Time Hour Date Minute Day Data Word 13 Data Word 14 Year Month Data Word 15

155 Supported Emulated Block Transfer Commands F-17 Message Operation Fault Queue Entry Read Full reads the contents of the fault queue specified in word 3 of the request. The response returns the fault text which can be ASCII text. Every two characters of text are in reverse order. Also, the 1336 FORCE drive returns a time stamp, indicating the day and time the fault occurred. If an error has occurred, word 1 of the response returns a negative value. Example In this example, Fault Queue Entry number 3 was retrieved from a 1336 PLUS drive. The drive response returned the ASCII text Drive Reset Flt, with each character reversed. The fault code for this example is 22. Data File Format PLC request * Drive response * 29252* 20313* 8293* 25938* 25971* 8308* 27718* 8303* 22* Drive response \00\12 \07\00 \03\00 r D v i e e R e s t l F t \00\16 * Example only These values vary depending on parameters and products.

156 F-18 Supported Emulated Block Transfer Commands Fault Queue Size Fault Queue Size gets the number of fault entries allowed in the fault queue. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 3 words Drive response instruction length: 4 words Figure F.11 Message Structure PLC Request Drive Response Message Length Header Word 0 3 Message Length Header 5 PLC Decimal Value Word Header Word 1 PLC Decimal Value Header 1793 Message OK Message Error Word 1 0 Header Word 2 0 Header Word 2 Fault Queue Size Data Word 3 Message Operation Fault Queue Size reads back the size of the fault queue available in the product. Each product may have a different number of fault queue entries available for storage. If an error has occurred, word 1 of the response returns a value of Example In this example, a 1336 PLUS drive was used. This product has a fault queue of four storage locations available to store faults. This value is seen in word 3 of the response header message. Data File Format PLC request Drive response * * Example only These values vary depending on parameters and products.

157 Trip Fault Queue Number Supported Emulated Block Transfer Commands F-19 Trip Fault Queue Number provides the fault queue number of the fault that caused the device to trip. PLC Block Transfer Emulation Instruction Data PLC request instruction length: 3 words Drive response instruction length: 4 words Figure F.12 Message Structure Message Length 3 PLC Decimal Value PLC Request Header Word 0 Header Word 1 Header Word 2 Drive Response Message Length 4 PLC Decimal Value 1794 Message OK Message Error 0 Number of Trip Fault Header Word 0 Header Word 1 Header Word 2 Header Word 3 Message Operation Trip Fault Queue Number provides the number of the entry in the fault queue that tripped the device in word 3 of the drive response. The fault queue number is 0 when the device is not faulted. If an error has occurred in the block transfer, word 1 of the response is negative. Example In this example, the device has stored a fault in the first entry of the fault queue that caused the drive to trip. Word 3 of the response indicates the entry number. Data File Format PLC request Drive response * * Example only These values vary depending on parameters and products.

158 F-20 Supported Emulated Block Transfer Commands Notes:

159 Appendix G Event Queue Messages Appendix Objectives Event Queue Messages Appendix G provides information on the messages in the adapter s Event Queue. This queue is only available using the DF-1 serial port on the 1203-GU6 module. The following table lists the messages you might receive. Event Empty Queue DeviceNet Reset SP Msg Timeout Noise Corruption SCANport Reset Logon Error No Pings Found No I/O Messages Datalink Missed I/O Port Changed SCANport Bus-Off SP Fault Msg SP PIN ID 7 DN Poll Timeout DN I/O Timeout DN I/O Too Long Manual Reset Bad I/O Fragment Idle I/O Message Peer I/O Timeout Adapter Reset Bad EEPROM CRC SP Fault Clear DN COS Timeout Nothing to report. What It Means A reset to the DeviceNet Identity Object was received. The SCANport product did not respond to a message request. Verify the cables are connected. This should never occur. If you see this message, it is usually the result of external noise. The SCANport product issued a reset command. An incorrect response was made to the SCANport logon sequence. SCANport pings. (Heartbeat messages were not received for more than 2 seconds. Check cables.) SCANport I/O messages were not received for more than 2 seconds. Possible drive problem. Not all datalinks selected have been received in the last 2 seconds. The SCANport PIN ID has changed. This message is normal after a power cycle. The SCANport CAN connection turn bus-off. Normally caused by too much noise. The drive issued a fault broadcast message. A SCANport PIN ID of seven indicates that no SCANport product is connected to the adapter. A polled I/O connection has timed out. An expected packet rate timer expired on a DeviceNet I/O connection. A DeviceNet I/O message was longer than the configured length to be received. You may need to reconfigure the I/O length in the scanner. Reset Adapter was set to cause an adapter reset. A DeviceNet I/O fragment was recived out of sequence. Possible line noise problem. The DeviceNet scanner was placed in the Program mode. A peer I/O message was not received for the time-out period. The adapter microprocessor was reset. Normal after a power cycle. The adapter parameter storage EEPROM has a corrupt CRC. To correct this, save a new value to one of the adapter parameters and check that all adapter parameters are at their desired values. A SCANport product has issued a fault cleared message. A Change of State (COS) connection has timed out.

160 G-2 Event Queue Messages Event What It Means DN Poll Allocate DN COS Allocate DN Poll Closed DN COS Closed A polled connection has been allocated. A Change of State (COS) I/O connection has been allocated. A poll I/O connection was explicitly closed. A change of state connection was explicitly closed.

161 Index Numerics 1203-GU6 configuring to communicate with a scanner, 5-1 to 5-8 default settings, 3-1 to 3-2 description, 1-2 DF1 statistics, 3-13 editing parameters in, 3-9 event queue, 3-10 firmware, 3-15 flash upgrade, 3-15 function, 1-1 hardware, 1-5 I/O data, 3-12 illustration, 1-5 installation, 2-1 LEDs, 8-1 to 8-4 network node address, B-10 parameters, B-10 to B-15 removal, 2-5 resetting, B-12 serial connection to, 3-2 serial number, 3-14 setting up, 1-7 specifications, A-1 troubleshooting, GM6 configuring to communicate with a scanner, 5-1 to 5-8 description, 1-2 function, 1-1 hardware, 1-6 illustration, 1-6 installation, 2-6 LEDs, 8-1 to 8-4 network node address, B-10 parameters, B-10 to B-15 removal, 2-9 resetting, B-12 setting up, 1-7 specifications, A-2 troubleshooting, 8-1 A audience for this manual, P-1 B baud rate DeviceNet parameter, B-10 setting, B-2 serial parameter, B-12 setting in terminal, 3-8 setting in terminal emulation software, 3-6 block transfer emulation, refer to emulated block transfer commands C cables DeviceNet connecting to adapter, 2-3, 2-8 disconnecting from adapter, 2-5, 2-9 selecting, 2-2 SCANport connecting to module, 2-4 disconnecting from module, 2-5 selecting, 2-2 change of state, B-5 communications module, refer to 1203-GU6 or 1336-GM6 Cyclic, B-5

162 I 2 Index D data rate on DeviceNet, B-2 datalinks description, B-2 list of, B-10 using, B-3 DeviceNet cable, 2-2 definition, P-3 network node addresses, B-1 overview, 1-1 setting data rate, B-2 DeviceNet objects, C-1 to C-26 connection, C-6 DeviceNet, C-5 identify, C-2 message router, C-4 parameter, C-10 PCCC, C-25 register, C-8 SCANport pass-through fault queue, C-19 SCANport pass-through link, C-23 SCANport pass-through parameter, C-18 SCANport pass-through warning queue, C-21 DF1 protocol statistics, 3-13 DIN rail attaching modules, 2-3 specification, A-1 E electrostatic discharge precautions, 2-7 emulated block transfer commands fault command write, F-15 fault queue entry read full, F-16 fault queue size, F-18 NVS functions, F-14 parameter read full, F-5 parameter value read, F-3 parameter value write, F-4 product ID number read, F-8 scattered parameter value read, F-10 scattered parameter value write, F-12 trip fault queue number, F-19 equipment required, 1-7 configuring a scanner, 5-1 installation 1203-GU6, GM6, 2-6 ladder logic programming, 6-1 serial connection, 3-2 event queue, 3-10, G-1 F fault configurable inputs, B-9 firmware upgrading, 3-15 flash upgrades, 3-15 H HyperTerminal, 3-3 I I/O data, 3-12, B-2 installation of 1203-GU6, 2-1 of 1336-GM6, 2-6 L ladder logic programs description, 6-2 example, 6-3 to 6-8 LEDs DeviceNet, 8-2 location, 8-1 module, 8-2 SCANport, 8-3 M manual audience, P-1 contents, P-2 conventions, P-4 purpose, P-1 master-slave communications, B-4, B-16, B-18

163 messaging controlling devices with, 7-10 description, 7-1 emulated block transfer, F-1 to F-19 examples, 7-6 to 7-10 explicit 1747-SDN scanner, SDN scanner, 7-2 N-file structure, E-1 PCCC, D-1 writing to register object, 7-12 module, refer to 1203-GU6 or 1336-GM6 N navigation techniques in software, 3-9 network node address, B-1 N-file structure, E-1 O objects, refer to DeviceNet objects P parameters module datalinks, B-2 default settings, 3-1 to 3-2 editing, 3-9 fault configurable inputs, B-9 list of, B-10 to B-15 SCANport product using emulated block transfer commands to view, F-3 to F-13 using RSNetWorx to view, 4-5 PCCC, D-1 peer-to-peer communications, B-6 PLC explicit messaging example, 7-6 I/O example, 6-5 polling, B-4 polling and change of state, B-6 polling and Cyclic, B-6 R removal of 1203-GU6, 2-5 of 1336-GM6, 2-9 resetting of the module, B-12 RSLogix, 6-1 RSNetWorx for DeviceNet creating an EDS file, 4-4 editing parameters with, 4-5 going online, 4-2 setting up a scan list with, 5-2 using to map I/O, 5-5 web site, 5-1 Index I 3 S safety precautions, P-3 SCANport cables, 2-2 definition, P-3 peripherals, P-3, 1-4 products, P-3, 1-4 serial connection cable, 3-2 using a PC running terminal emulation software, 3-3 using a VT100-compatible terminal, 3-8 serial number, 3-14 serial port rate, refer to baud rate SLC explicit messaging example, 7-9 I/O example, 6-7 specifications, A-1 T technical support, P-4 terminal, 3-8 terminal emulation software, 3-3 terms and abbreviations, P-3 troubleshooting, 8-1

164 I 4 Index Notes:

165 Notes

166 Notes

167 Notes

168 Notes

169 We Want Our Manuals to be the Best! You can help! Our manuals must meet the needs of you, the user. This is your opportunity to make sure they do just that. By filling out this form you can help us provide the most useful, thorough, and accurate manuals available. Please take a few minutes to tell us what you think - then mail this form or FAX it. FAX: your local Allen-Bradley Sales Office or 414/ PUBLICATION NAME PUBLICATION NUMBER, DATE AND PART NUMBER (IF PRESENT) CHECK THE FUNCTION THAT MOST CLEARLY DESCRIBES YOUR JOB. SUGGEST/RESPONSIBLE FOR THE PURCHASE OF EQUIPMENT DESIGN/IMPLEMENT ELECTRICAL SYSTEMS SUPERVISE FLOOR OPERATIONS MAINTAIN/OPERATE PROGRAMMABLE MACHINERY TRAIN/EDUCATE MACHINE USERS WHAT LEVEL OF EXPERIENCE DO YOU HAVE WITH EACH OF THE FOLLOWING PRODUCTS? NONE LITTLE MODERATE EXTENSIVE PROGRAMMABLE CONTROL AC/DC DRIVES PERSONAL COMPUTERS NC/CNC CONTROLS DATA COMMUNICATIONS/LAN RATE THE OVERALL QUALITY OF THIS MANUAL BY CIRCLING YOUR RESPONSE BELOW. (1) = POOR (5) = EXCELLENT HELPFULNESS OF INDEX/TABLE OF CONTENTS CLARITY EASE OF USE ACCURACY AND COMPLETENESS QUALITY COMPARED TO OTHER COMPANIES MANUALS QUALITY COMPARED TO OTHER ALLEN-BRADLEY MANUALS WHAT DID YOU LIKE MOST ABOUT THIS MANUAL? WHAT DID YOU LIKE LEAST ABOUT THIS MANUAL? PLEASE LIST ANY ERRORS YOU FOUND IN THIS MANUAL (REFERENCE PAGE, TABLE, OR FIGURE NUMBERS). CUT ALONG DOTTED LINE DO YOU HAVE ANY ADDITIONAL COMMENTS? COMPLETE THE FOLLOWING. NAME COMPANY TITLE DEPARTMENT STREET CITY STATE ZIP TELEPHONE DATE