Enhanced DeviceNet™ Communications Module Catalog Numbers: 1203-GU6 and 1336-GM6 Firmware: 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.
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 Description Additions Added an Allen-Bradley proprietary object used by the PCP group. Corrections 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.
Summary of Changes Notes:
Table of Contents Preface Using this Manual Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Use this Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii Table of Contents Chapter 4 Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 What is RSNetWorx for DeviceNet? . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Required Equipment and Software . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Going Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Creating an EDS File . . . . . . . .
Table of Contents iii Appendix B 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. . . . . . . . . . . . . . . . . .
iv Table of Contents Appendix F 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Using this Manual Objectives Who Should Use 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.
P-2 Using this Manual Contents of this Manual This manual contains the following information: Chapter Title Contents 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.
Using this Manual Safety Precautions Please read the following safety precautions carefully. ! ! ! Terms and Abbreviations P-3 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.
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.
Chapter 1 Overview Chapter Objectives Overview of the Communications Adapter 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.
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 1.2 Example DeviceNet NetWork 1336 PLUS 1305 SMC 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.
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.
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.
Overview Hardware and Parts Description 1-5 The hardware included with the adapter depends on the adapter that you have. 1203-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 1 2 4 5 3 Number Part Description 1 DIN Rail Mount Securely attaches and electronically grounds the module to the DIN rail.
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 1 3 2 Number Part 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.
Overview Overview of Setting Up the Adapter 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.
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 http://www.software.rockwell.com for more information on these software products. 1336-GM6 Board To install and configure a 1336-GM6 board, you need the following: • Enhanced DeviceNet communications board (1336-GM6).
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.
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 1m 1202-C10 1m 1202-H10 3m 1202-C30 3m 1202-H30 9m 1202-C90 9m 1202-H90 • Use less than 10 meters (33 feet) of cable between the SCANport product and adapter.
Installation 2-3 Installing the 1203-GU6 Communications Module 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.
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.
Installation 2-5 You must now edit the adapter’s node address, and you may want to edit some of its other parameters.
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.
Installation 2-7 Electrostatic Discharge Precautions 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.
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.
Installation 2-9 7. Reapply power to the SCANport product. 8. Reapply power to the DeviceNet network. 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.
2-10 Notes: Installation
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.
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.
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.
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.
Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 5. 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.
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 19200 bps, set the bps to 19200 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.
Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3-7 15. 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.
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 3.1. 2. Start your terminal. 3. Select the following settings: – 9600 in the Bits per second field.
Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Navigation Techniques 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 Return to Main Menu or abort changes to a parameter. Down Arrow View the next parameter.
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.
Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3-11 2. 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 1 2–7 8 Name Description Clr Event Queue Enable = Clears the event queue. Ready = Leaves the event queue as is.
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.
Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Viewing DF-1 Statistics 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.
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.
Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection Performing a Flash Upgrade to the Module 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.
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. ! Figure 3.13 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.
Configuring the 1203-GU6 Enhanced DeviceNet Module Using a Serial Connection 3-17 4. 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.
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.
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.
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.
Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet 4-3 5. 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.
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.
Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet Accessing and Editing Parameters 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.
4-6 Notes: Configuring the Enhanced DeviceNet Adapter Using RSNetWorx for DeviceNet
Chapter 5 Configuring a Scanner to Communicate with the Adapter Chapter Objectives Required Equipment and Software Example DeviceNet Network 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.
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 4. 2. Select Network > Single Browse Path. The devices on the network are displayed in the configuration view. Figure 5.2 Configuration View (Graph) 3.
Configuring a Scanner to Communicate with the Adapter Figure 5.3 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.
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.
Configuring a Scanner to Communicate with the Adapter Mapping the Product’s Data in the Scanner 5-5 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.
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.
Configuring a Scanner to Communicate with the Adapter Saving the Configuration 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.
5-8 Notes: Configuring a Scanner to Communicate with the Adapter
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.
6-2 Ladder Logic Programming For more information on RSLogix5 or RSLogix500, consult the respective software’s documentation. What are Ladder Logic Programs? 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.
Ladder Logic Programming Example Ladder Logic Programs 6-3 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.
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.
Ladder Logic Programming 6-5 PLC Ladder Logic Example 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.
6-6 Ladder Logic Programming Figure 6.2 Example PLC Ladder Logic Program (Continued) This rung enables the scanner. 1771-SDN Scanner Port A Enable N10:0 0004 0 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.
Ladder Logic Programming 6-7 SLC Ladder Logic Program Example 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.
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:0 0004 0 1746-I*16 Operator Input Drive Stop Command Bit I:2.0 1 1336PLUS STOP Command Bit N10:0 0005 1 1746-I*16 Operator Input Drive Jog Command Bit I:2.
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.
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.
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.
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.
Using DeviceNet Explicit Messaging 7-5 Each of the data fields in the transaction header are one byte in length: Data Field Description TXID 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.
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.
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.
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.
Using DeviceNet Explicit Messaging 7-9 SLC Messaging 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 Explicit Message COP Copy File Source #N20:10 Dest #M0:1.
7-10 Using DeviceNet Explicit Messaging The following table display data sent to and received from the scanner. Values are in hexadecimal.
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.
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 SC
Chapter 8 Troubleshooting Chapter Objectives LEDs on the Enhanced DeviceNet Adapter 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. 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.
8-2 Troubleshooting DeviceNet Network Status LED States LED Viewed: If: The LED closest to the DeviceNet connector is the DeviceNet Status LED, labeled “NET.” It functions as follows: State: 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.
Troubleshooting SCANport Status LED States LED Viewed: SCANport Status LED If: 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: 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.
8-4 Notes: Troubleshooting
Appendix A Specifications Appendix Objectives 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. 1203-GU6 Specifications The following table gives the specifications for the 1203-GU6 Enhanced DeviceNet communications module. Category Specifications Dimensions 1.8" W x 3.0" H x 5.0" D (4.57 cm x 7.62 cm x 12.7 cm) Weight 6.
A-2 Specifications 1336-GM6 Specifications The following table gives the specifications for the 1336-GM6 Enhanced DeviceNet communications board. Category Specifications Dimensions 4.5" W x 2.8" H x 0.5" D (11.43 cm x 7.112 cm x 1.27 cm) Weight 1.
Appendix B Enhanced DeviceNet Adapter’s Parameters Appendix Objectives 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.
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.
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.
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.
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).
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 1. 6. Reset the adapter by setting the Reset Adapter (22) parameter to Enable. 7.
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.
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.
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.
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.
Enhanced DeviceNet Adapter’s Parameters # Name 9 Idle Flt Action Valid Values/ Settings Fault Zero Data Hold Last Fault Cfg Default Writable Reset or Power Cycle Fault Yes No Description 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.
B-12 Enhanced DeviceNet Adapter’s Parameters # Name Valid Values/ Settings Default Writable Reset or Power Cycle 13 Fault Cfg A1 In 0 – 65535 0 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 0 – 65535 0 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.
Enhanced DeviceNet Adapter’s Parameters # Name Valid Values/ Settings Default Writable Reset or Power Cycle 23 Active I/O Cfg 0 or 1 for each bit N/A No No B-13 Description Displays what I/O is activated in the adapter. datalink B datalink C datalink A datalink D Cmd/Stat xxx0, 0000 0 = 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.
B-14 Enhanced DeviceNet Adapter’s Parameters Valid Values/ Settings Default Writable Reset or Power Cycle COS Feedback Change 0 – 65535 0 = 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.
Enhanced DeviceNet Adapter’s Parameters B-15 # Name Valid Values/ Settings Default Writable Reset or Power Cycle 35 Peer Inp Time-out 0.01-180.00 sec 10.00 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.
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.
Enhanced DeviceNet Adapter’s Parameters B-17 ALLOCATION (Number Of Words) ADAPTER CONFIGURATION 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 10100 xxxx0 4 NA NA NA NA 10101 xxxx0 6 NA NA NA NA 10110 xxxx0 6 NA NA NA NA 10111 xxxx0 8 NA NA NA NA 11000 xxxx0 4 NA NA NA NA 11001 xxxx0 6 NA NA NA NA 11011 xxxx0 8 NA NA NA NA 11100 xxxx0 6 NA NA NA NA 11101 xxxx0
B-18 Enhanced DeviceNet Adapter’s Parameters ALLOCATION (Number Of Words) ADAPTER CONFIGURATION 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 11011 xxxx1 8 8 8 8/0 8/0 11100 xxxx1 6 6 6 6/0 6/0 11101 xxxx1 8 8 8 8/0 8/0 11110 xxxx1 8 8 8 8/0 8/0 11111 xxxx1 10 10 10 10/0 10/0 M-S Output Parameter Configurations The M-S Output parameter has the following five configurable bits.
Enhanced DeviceNet Adapter’s Parameters B-19 ALLOCATION (Number Of Words) Data Size Sent From The Adapter To The Controller M-S Output Poll Only COS Only Cyclic Only Poll & COS Poll & Cyclic 10010 4 NA NA NA NA 10100 4 NA NA NA NA 10110 6 NA NA NA NA 11000 4 NA NA NA NA 11010 6 NA NA NA NA 11100 6 NA NA NA NA 11110 8 NA NA NA NA 00001 2 2 2 2/2 2/2 00011 4 2 2 4/2 4/2 00101 4 2 2 4/2 4/2 00111 6 2 2 6/2 6/2 01011 6 2 2 6/2 6/2 0
B-20 Notes: Enhanced DeviceNet Adapter’s Parameters
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.
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 2 Get Max Instance UINT Description 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.
DeviceNet Objects C-3 Instance Attributes 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 0.5 – 10 HP -S/B 0xXX02 0xXX03 = 1336 PLUS 7.
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 1 Description Message Router Object Instance Attributes Attribute ID Access Rule 2 Get Number available UINT Maximum number of connections supported by the message router.
DeviceNet Objects Class Code 0x03 — DeviceNet Object 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 1 Get Name DeviceNet Specification Data Type Word Description Returns 2 Instances Not supported.
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.
DeviceNet Objects C-7 Instance Attributes Attribute ID Access Rule 1 Get 2 Name Data Type Description State USINT State of the connection as defined in the DeviceNet specification 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 Defin
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.
DeviceNet Objects C-9 Instance Attributes 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 1 ➀ Name Data Type Get Bad Flag BOOL If set to 1, then attribute 4 may contain invalid, bad or otherwise corrupt data.
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 1 Get Revision UINT Revision of this object. First revision, value = 1.
DeviceNet Objects C-11 Instance Attributes Attribute ID Access Rule Stub/Full Name 1 ➀ Stub Parameter Value 2 Get Stub Link Path Size 3 Get Stub Link Path Data Type Specified in Descriptor, Data Type and Data Size attributes. Description Actual value of parameter. Data type specified in descriptor, data type, and data size.➀➁ USINT Size of Link Path attribute. If this attribute is 0, then no link is specified. Number of BYTEs in attribute 3.
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.
DeviceNet Objects C-13 Data Types for Instance Attribute 5 Attribute ID Value Data Type Description Definition 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 Support
C-14 DeviceNet Objects Common Services Implemented for: Service Code Service Name Class Instance 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.
DeviceNet Objects Class Attribute ID 21 C-15 Attribute Name and Default Value Decimal Precision Default = 0 Object Specific Services Implemented for: Service Code 0x4B Service Name Class Instance 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.
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 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.
DeviceNet Objects C-17 Common Services Implemented for: Service Code 0x0E Service Name Class Instance Yes Yes Get_Attribute_All Response Not supported.
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 Implemented for: Service Code ➀ Service Name Class Instance 0x32 Yes No Scattered_Parameter_ Value_Read➀ 0x34 Yes No Scattered_Parameter_ Value_Write➀ Must be directed to Attribute 0, Instance 0.
DeviceNet Objects Class Code 0x97 — SCANport Pass-Through Fault Object C-19 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 Get BYTE 2 Get Read Number of Fault Queue Entries Read Fault Queue Trip Index 1 = Clear Faults 2 = Clear Fault Queue 3 = Reset Product Reads the number of fault queue entries.
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
DeviceNet Objects Class Code 0x98 — SCANport Pass-Through Warning Object C-21 The SCANport Pass-Through Warning Object provides information on the product’s warning queue.
C-22 DeviceNet Objects Attribute ID Access Rule 128 Get Name Data Type Warning Code and Time Stamp (Time Stamps not available in all products) Warning Code Warning Time Stamp (Time Stamps not available in all products) STRUCT of WORD BYTE BYTE BYTE Get Read Warning Text String Only ➀ Sunday is a value of zero. ➁ Year is an offset from 1990. Fault Code. STRUCT of BYTE BYTE BYTE BYTE BYTE 129 Description ARRAY of BYTE 1/100 Second (0 – 99). Second (0 – 59). Minute (0 – 59).
DeviceNet Objects Class Code 0x99 — SCANport Pass-Through Link Object 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.
C-24 DeviceNet Objects The table below lists parameters for Scattered_Link_Reference_Read and Scattered_Link_Reference_Write object-specific services. Name Scattered Link Read/Write Data Type Description 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.
DeviceNet Objects Class Code 0x67 — PCCC Object 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.
C-26 DeviceNet Objects Message Structure for Execute_Local_PCCC Request Data Type Name Response Description Data Type Name 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. EXT_STS USINT Extended status. Not used for all CMD’s.
Appendix D Supported PCCC Messages Appendix Objectives DF-1/PCCC Support (1203-GU6 Only) 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. The 1203-GU6 translates PCCC messages into SCANport messages between the SCANport device and the module.
D-2 Supported PCCC Messages Supported PCCC Messages CMD The 1203-GU6 and 1336-GM6 support the following PCCC messages: 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 Yes Logical Binary Address No PLC-2 System Address No PLC-3 Symbolic Address No 0x0F 0xA1 SLC-500 Protected Typed Logical Read w/ 2 Address Fields — File, Element No 0x0F 0xA2 SLC-500 Prot
Appendix E N-File Addresses Appendix Objectives 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.
E-2 N-File Addresses Address N-File Addresses N50:0 Number of SCANport product parameters N50:1 – 249 SCANport product parameters 1 – 249 (value only) N51:0 – 249 SCANport product parameters 250 – 499 (value only) . . . N61:0 – 249 SCANport product parameters 2750 – 2999 (value only) N90:1 – 249 SCANport product parameters 1 – 249 (value only) N91:0 – 249 SCANport product parameters 250 – 499 (value only) . . .
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: What is Emulated Block Transfer? • 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.
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.
Supported Emulated Block Transfer Commands Parameter Value Read 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.
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.
Supported Emulated Block Transfer Commands Parameter Read Full 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.
F-6 Supported Emulated Block Transfer Commands Figure F.4 Message Structure (Continued) Drive Response File, Group, Element Data Word 17 Minimum Value Data Word 18 Maximum Value Data Word 19 Default Value Char 2 Char 1 Char 4 Char 3 Unit Text 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.
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.
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.
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 –32512. Example In this example, the Product ID Number Read was requested.
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.
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.
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.
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 –32765. • Bit 15 of the drive response word for that parameter’s number is set.
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.
Supported Emulated Block Transfer Commands Fault Command Write 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.
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.
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.
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.
Supported Emulated Block Transfer Commands Trip Fault Queue Number 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.
F-20 Notes: Supported Emulated Block Transfer Commands
Appendix G Event Queue Messages Appendix Objectives 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. Event Queue Messages The following table lists the messages you might receive. Event Empty Queue What It Means Nothing to report. DeviceNet Reset A reset to the DeviceNet Identity Object was received. SP Msg Timeout The SCANport product did not respond to a message request.
G-2 Event Queue Messages Event What It Means DN Poll Allocate A polled connection has been allocated. DN COS Allocate A Change of State (COS) I/O connection has been allocated. DN Poll Closed A poll I/O connection was explicitly closed. DN COS Closed A change of state connection was explicitly closed.
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, 8-1 1336-G
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 equipment required, 1-7 c
Index 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, 7-4 1771-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
I–4 Notes: Index
Notes
Notes
Notes
Notes
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.
FOLD HERE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST CLASS PERMIT NO. 413 MEQUON, WI POSTAGE WILL BE PAID BY ADDRESSEE ALLEN-BRADLEY Attn: Marketing Communications P.O.
1336 FORCE, 1336 IMPACT, DriveExplorer, SCANport, RSLinx, RSNetWorx, RSLogix5 and RSLogix500 are trademarks of Rockwell Automation. PLC and PLC-5 are registered trademarks of Rockwell Automation. SLC and SLC-5/03 are registered trademarks of Rockwell Automation. DeviceNet is a trademark of the Open DeviceNet Vendor Association. Windows and Microsoft are either registered trademarks or trademarks of Microsoft Corporation.
Reach us now at www.rockwellautomation.com Wherever you need us, Rockwell Automation brings together leading brands in industrial automation including Allen-Bradley controls, Reliance Electric power transmission products, Dodge mechanical power transmission components, and Rockwell Software. Rockwell Automation's unique, flexible approach to helping customers achieve a competitive advantage is supported by thousands of authorized partners, distributors and system integrators around the world.
