Allen-Bradley DeviceNet 1747-SDN User Manual
  1. Manuals
  2. Brands
  3. Allen-Bradley Manuals
  4. Control Unit
  5. DeviceNet 1747-SDN
  6. User manual

Allen-Bradley DeviceNet 1747-SDN User Manual

Scanner module
Hide thumbs Also See for DeviceNet 1747-SDN:
Table of Contents

Advertisement

Quick Links

See also: Instruction and Installation Manual
1747-SDN
DeviceNet Scanner
Module
Catalog Number
1747-SDN, Series C
User Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DeviceNet 1747-SDN and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Allen-Bradley DeviceNet 1747-SDN

Summary of Contents for Allen-Bradley DeviceNet 1747-SDN

  • Page 1 1747-SDN DeviceNet Scanner Module Catalog Number 1747-SDN, Series C User Manual...
  • Page 2 Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://literature.rockwellautomation.com) describes some important differences between solid state equipment and hard-wired electromechanical devices.
  • Page 3 Summary of Changes The information below summarizes the changes to this manual since the last publication. To help you find new and updated information in this release of the manual, we have included change bars as shown to the right of this paragraph.
  • Page 4 Summary of Changes Publication 1747-UM655B-EN-P - June 2007...

  • Page 5: Table Of Contents

    Table of Contents Preface Introduction ........9 Audience .
  • Page 6 Table of Contents Chapter 5 Communicating with the What This Chapter Contains ......63 Additional Resources......64 DeviceNet Network from Another System Requirements .
  • Page 7 Table of Contents Appendix C 1747-SDN Module Firmware Purpose ........129 Revision 8.002.
  • Page 8 Table of Contents Publication 1747-UM655B-EN-P - June 2007...

  • Page 9: Preface

    Preface Introduction This user manual is designed to provide you enough information to get a small example application up and running. Use this manual if you are knowledgeable about DeviceNet and SLC 500 products, but may not have used the products in conjunction. The information provided is a base;...

  • Page 10: The Example Application

    Preface The Example Application This manual describes how to set up an example application. The manual provides examples of each step of the setup, with references to other manuals for more details. System Components We used the following devices and software for the example application.

  • Page 11: Common Techniques Used In This Manual

    Preface Quantity Product Name Catalog Number Series/Revision 24V power supply Any regulated 24V dc, 8 A Personal computer IBM-compatible Pentium+ Windows 2000 or later Software RSLogix 500 9324-RL0300xxx Rev 4.00 RSNetWorx for DeviceNet 9357-DNETL3 Rev 2.22 RSLinx 9355-WAB Rev 2.10 Common Techniques Used The following conventions are used throughout this manual: in This Manual...
  • Page 12 Preface Resource Description ControlNet Coax Media Planning and Installation Provides information on planning Guide, publication CNET-IN002 and installing ControlNet coax media systems. RediSTATION operator interface User Manual, Provides information on installing publication 2705-UM001 and using the RediSTATION operator interface. SLC 500 Module Hardware Style User Manual, Provides information on installing, publication 1747-UM011 wiring, startup, and maintenance of...

  • Page 13: What This Chapter Contains

    Chapter Before You Begin What This Chapter Contains This chapter provides an overview of communication between the SLC 500 processor and DeviceNet devices via the 1747-SDN module. The configuration data tables and the RSNetWorx for DeviceNet software dialogs and dialogs used to configure the data tables are also described.

  • Page 14: What Your 1747-Sdn Module Does

    Before You Begin What Your 1747-SDN In a typical configuration, the 1747-SDN module acts as an interface between DeviceNet devices and the SLC 500 processor. Module Does Typical DeviceNet Network Computer with RSNetWorx SLC 500 Modular Chassis for DeviceNet Software 1770-KFD PC SLC 500 1747-SDN Interface...
  • Page 15 Before You Begin Processor to I/O Input Read by Processor (Chapter 2) Configure SDN Module (Chapter 4) Computer Running Configure SDN Module (Chapter 4) RSNetWorx for DeviceNet Mapping Table (Chapters 2 and 4) Software Output Write by Output Data to Devices Processor (Chapter 2) from SDN (Chapter 2) DeviceNet Network...

  • Page 16: Communicating With Your Devices

    Before You Begin Communicating with Your The 1747-SDN module communicates with a device via strobe, poll, change of state, and/or cyclic messages. It uses these messages to Devices solicit data from or deliver data to each device. Data received from the devices, or input data, is organized by the 1747-SDN module and made available to the processor.
  • Page 17 Before You Begin Communicating With Other Devices 1747-SDN Module DeviceNet Devices Input Data From Input Data Storage DeviceNet Devices Byte Input from Different portions of data from a single the devices device can be mapped to separate to the 1747-SDN memory locations. For example, SLC 500 On/Off values can be mapped to one processor.

  • Page 18: Communicating With Your Slc 500 Processor

    Before You Begin Communicating with Your The 1747-SDN module does not send data to your processor. Data transferred between the module and the processor must be initiated SLC 500 Processor by the processor. Output data is sent, or written, to the scanner by your processor by placing the data in the M0 file.

  • Page 19: 1747-Sdn Module Data Tables

    Before You Begin 1747-SDN Module Data To manage the flow of data between your SLC 500 processor and the network devices, the 1747-SDN module uses the following data tables: Tables • Scanner configuration table (SCT) • Scanlist table (SLT) • Device input data table •...

  • Page 20: Rsnetworx Software As A Configuration Tool

    Before You Begin • the size of the input data/output data. • exactly where to map the input or output data for your processor to read or write. • how your processor reads each device’s input data (M1/M0 file or discrete I/O). Data Table Information User-configured Tables Data in This Table...
  • Page 21 Before You Begin RSNetWorx for DeviceNet Configuration Dialog Map The main RSNetWorx for DeviceNet dialog. Click Online and select the driver to browse the network. Double-click the 1747-SDN icon to access the 1747-SDN Interface Module. Click the Scanlist tab to access the scanlist.

  • Page 22: What's Next

    Before You Begin What’s Next? The remaining sections of this manual provide the following information: • Chapter 2 covers the configuration process planning stage through a data mapping example. • Chapter 3 describes the hardware setup for the example application. •...

  • Page 23: What This Chapter Contains

    Chapter Planning Your Configuration and Data Mapping Your Devices What This Chapter Contains This chapter introduces questions you should ask before configuring your 1747-SDN communication module. In addition, it presents an example DeviceNet network and I/O data mapping scheme for a photoeye and a RediSTATION operator interface.

  • Page 24: Beginning The Process

    Planning Your Configuration and Data Mapping Your Devices Beginning the Process Planning before configuring your 1747-SDN module helps you do these things: • Use your memory and bandwidth efficiently • Cater to device-specific needs and requirements • Give priority to critical I/O transfers •...
  • Page 25 Planning Your Configuration and Data Mapping Your Devices Example Network Devices This example network has the following devices: • A computer running RSNetWorx for DeviceNet software • A 1747-SDN communication module interfacing an SLC 500 processor with the DeviceNet network •...
  • Page 26 Planning Your Configuration and Data Mapping Your Devices RediSTATION Operator Interface Input and Output Data Mapping The RediSTATION operator interface has both inputs and outputs that must be mapped. The input byte is mapped to the 1747-SDN module’s M1 file and then to the SLC 500 processor’s input data file. The output byte is mapped to the 1747-SDN module’s M0 file and then to the SLC 500 processor’s output data file.
  • Page 27 Planning Your Configuration and Data Mapping Your Devices Mapping RediSTATION Input Data for an M1 File Data Table Read The following is an example of input data mapping for the RediSTATION operator interface. RediSTATION Input Byte What’s Happening? R = Bit for Red Button (STOP) 1 byte G = Bit for Green Button (START) The bits for the RediSTATION...
  • Page 28 Planning Your Configuration and Data Mapping Your Devices Mapping RediSTATION Output Data for an M0 File Data Table Write The RediSTATION operator interface’s output is mapped to the 1747-SDN module’s M0 file. Within the output byte is a bit for the indicator light.
  • Page 29 Planning Your Configuration and Data Mapping Your Devices Photoeye Input Data Mapping The photoelectric sensor (photoeye) inputs are mapped to the 1747-SDN module’s M1 file and then to the SLC 500 processor’s input data file. The procedure for doing this by using RSNetWorx for DeviceNet software is described in chapter 4.

  • Page 30: What's Next

    Planning Your Configuration and Data Mapping Your Devices Mapping Photoeye Input Data for an M1 File Data Table Read 1 byte What’s Happening? The status and data bits from the photoeye are mapped into the 1747-SDN Module’s M1 = Unused Bits file data table.

  • Page 31: What This Chapter Contains

    Chapter Hardware Setup What This Chapter Contains This chapter describes how to set up the hardware for the example application. The following table describes what this chapter contains and where to find specific information. Topic Page Installing the 1770-KFD Module Installing the SLC 500 Processor Installing the ControlNet RS-232 Interface Module...

  • Page 32: Installing The Slc 500 Processor

    Hardware Setup For detailed directions on how to install the 1770-KFD module, see the DeviceNet RS-232 Interface Module Installation Instructions, publication 1770-5.6. Installing the SLC 500 These sections give you information on installing your processor and getting it connected. Processor Identifying Processor Features Refer to the following figures to identify the features of your SLC 5/04 or SLC 5/05 processor.
  • Page 33 Hardware Setup Chassis Install Insert the SLC 500 processor into the left slot (slot 0), as shown IMPORTANT above. Remove the protective wrap after installing the processor. Establishing Data Highway Plus Communication For the examples using the Data Highway Plus (DH+) network in Chapters 5 and 6 of this manual, we installed a 1784-PKTX communication card in the host platform and an SLC 5/04 processor with these default Channel 1 DH+ configurations:...
  • Page 34 Hardware Setup DH+ Network Connection Terminating Resistor See Chapter 5 for information on configuring the SLC 5/04 processor’s DH+ communication. Installing an Ethernet SLC 500 Processor (SLC 5/05 Processor) In order to communicate with your SLC 500 processor over an Ethernet network, you must install an Ethernet version of the processor (SLC 5/05 processor, catalog numbers 1747-L551, 1747-L552, or 1747-L553).

  • Page 35: Installing The Controlnet Rs-232 Interface Module

    Hardware Setup Configuring the RS-232 Port for the ControlNet Interface If you need to communicate with your SLC 500 processor via a ControlNet network, you must install a 1747-KFC15 ControlNet interface module in the chassis with your processor. You can use either a SLC 5/04 or a SLC 5/05 processor.
  • Page 36 Hardware Setup Dip Switch Setting The upper position as shown above is ON. The lower position is OFF. For the example application, we used the following configuration to match the configuration of the SLC 500 processor’s RS-232 port described in the previous section. Channel 0 Configuration Attribute Value...
  • Page 37 Hardware Setup Bank S1 DIP Switches Switch Setting Position Switches Upper digit Digit 1…3 of DF1 station address Switches Lower digit Digit 4…6 of DF1 station address Switches 7…8 Both OFF Bank S2 DIP Switches Switch Setting Position Switches Upper digit Digit 1…3 of DF1...
  • Page 38 Hardware Setup Refer to the SLC 500 ControlNet RS-232 Interface User Manual, publication 1747-5.34, for information on setting and verifying the 1747-KFC15 and SLC 500 processor communication parameters. Configuring the 1747-KFC15 Module’s ControlNet Node Address The 1747-KFC15 modules’s ControlNet node address is set by rotary switches S4 and S5 on the top of the module.
  • Page 39 Hardware Setup Install the 1747-KFC15 Module in the Chassis Electrostatic discharge can damage semiconductor devices ATTENTION inside the 1747-KFC15 module. To guard against electrostatic damage, wear an approved wrist strap grounding device, or touch a grounded object to rid yourself of electrostatic charge before handling the products.

  • Page 40: Installing The 1747-Sdn Module

    Hardware Setup Refer to the ControlNet Coax Media Planning and Installation Guide, publication CNET-IN002, for complete instructions on connecting the tap to the ControlNet cable system. Installing the 1747-SDN These sections give you information on installing your module and getting it connected. Module Identifying Module Features Use the following figure to identify the features of the 1747-SDN...
  • Page 41 Hardware Setup Install the 1747-SDN Module In the Chassis Do not install the 1747-SDN module with the chassis power ATTENTION supply on. Installing the module with the chassis power supply on may damage the module. Follow these steps to install your module into the chassis. 1.
  • Page 42 Hardware Setup Connect the 1747-SDN Module to the DeviceNet Network Follow these steps to connect your module to the DeviceNet network. 1. Turn off the network power supply. Do not wire the 1747-SDN module with the network power ATTENTION supply on. Wiring the module with the network power supply on may short your network or disrupt communication.

  • Page 43: Installing The Redistation Operator Interface

    Hardware Setup You use RSNetWorx for DeviceNet software to configure the module’s DeviceNet address and communication rate, if needed. This is done when configuring the DeviceNet network. See page 52. For additional information about installing the 1747-SDN module, see the 1747-SDN DeviceNet Scanner Module Installation Instructions, publication 1747-IN058.

  • Page 44: Installing The Series 9000 Photoeye

    Hardware Setup See Chapter 2 of the RediSTATION Operator Interface User Manual, publication 2705-UM001, for complete information about setting the DIP switches to configure the node address, data rate, output flash rate, and output fault state. Refer to the following illustration as you connect the RediSTATION operator interface to the network.

  • Page 45: How Your Network Will Look

    Hardware Setup Top View of Series 9000 Photoeye Programming Pushbutton Sensitivity Adjustment Yellow - Output Green - Margin Red/Green - Status For detailed directions, see the instructions that came with your photoeye. How Your Network Will When you have finished installing all the devices, the network should look similar to this.

  • Page 46: What's Next

    Hardware Setup Make sure each end of the DeviceNet trunk cable is properly IMPORTANT terminated with a resistor. Refer to the DeviceNet Media Design and Installation Guide, publication DNET-UM072, for information. What’s Next? The next step is to configure the 1747-SDN module and perform I/O data mapping through RSNetWorx for DeviceNet software.

  • Page 47: What This Chapter Contains

    Chapter Configuring the DeviceNet Network What This Chapter Contains This chapter describes how to configure the DeviceNet network by using RSLinx and RSNetWorx for DeviceNet software. Topic Page Installing the Software Use RSLinx Software to Configure the DeviceNet Driver Using RSNetWorx for DeviceNet Software to Configure the 1747-SDN Module Scanlist Set Up an Online Connection Set the 1747-SDN Node Address...

  • Page 48: Use Rslinx Software To Configure The Devicenet Driver

    Configuring the DeviceNet Network Use RSLinx Software to Follow these steps to configure your DeviceNet driver. Configure the DeviceNet 1. Start RSLinx software. Driver The RSLinx main dialog opens. 2. Select Configure Drivers from the Communication menu. The following dialog appears. 3.
  • Page 49 Configuring the DeviceNet Network 4. Select the Allen-Bradley 1770-KFD driver. The Driver Configuration dialog appears. Your driver setup depends on your particular system setup (COM port, communication rate, node address). Choose the appropriate settings for your system. 5. Configure the driver by using the example above as a guide and click on OK.

  • Page 50: Using Rsnetworx For Devicenet Software To Configure The 1747-Sdn Module Scanlist

    Configuring the DeviceNet Network Using RSNetWorx for Use RSNetWorx for DeviceNet software to do the following tasks: DeviceNet Software to • Set up an online connection Configure the 1747-SDN • Set the 1747-SDN node address Module Scanlist • Configure the I/O devices •...
  • Page 51 Configuring the DeviceNet Network 4. Click Online on the toolbar. A list of the available drivers in RSLinx software appears. Your list may appear different from that shown below, depending upon the drivers you have configured on your system. 5. Select the 1770-KFD-1, DeviceNet driver and click OK. You are prompted to upload or download devices before going online.

  • Page 52: Set The 1747-Sdn Node Address

    Configuring the DeviceNet Network 6. Click OK to upload the devices and go online. RSNetWorx for DeviceNet software begins browsing for network devices. When the software is done browsing, the network displayed on your screen should appear similar to the one shown below.
  • Page 53 Configuring the DeviceNet Network If 00 appears to the right of the 1747-SDN icon and you do not need to change the node address or baud rate of any device, skip the remainder of this section and go to Configure the I/O Devices on page 55.
  • Page 54 Configuring the DeviceNet Network 3. Select the 1770-KFD driver. The devices on the network appear in the right panel of the dialog. 4. Select the device you are commissioning in the right panel and click OK. The Node Commissioning dialog appears with the current settings for your 1747-SDN module.

  • Page 55: Configure The I/O Devices

    Configuring the DeviceNet Network Configure the I/O Devices Follow these steps to configure the I/O devices. 1. Double-click the 1747-SDN module icon. The following dialog appears. 2. Click the Module tab. You receive the following prompt. Publication 1747-UM655B-EN-P - June 2007...
  • Page 56 Configuring the DeviceNet Network 3. Click Upload. After uploading, the following dialog appears. 4. Verify the 1747-SDN module slot number is correct for your system. We used slot 2. We used the Module Defaults for the other settings. For an explanation of these settings click Help.

  • Page 57: Verify The Photoeye Configuration

    Configuring the DeviceNet Network 7. Click the double arrow to add the photoeye and RediSTATION operator interface to the Scanlist. Verify the Photoeye Configuration 1. Double-click the photoeye in the Scanlist. The Edit I/O Parameters dialog appears for the photoeye. The I/O parameters define the configuration for the device in terms of how much and what data the device exchanges with the 1747-SDN module.

  • Page 58: Automap The Devices Into The Scanlist

    Configuring the DeviceNet Network The Edit I/O Parameters dialog appears for the RediSTATION operator interface. 2. Verify that the Polled box is checked and that the Rx Size and Tx Size are each 1 byte. 3. Click OK to close the Edit I/O Parameters dialog for the RediSTATION operator interface.
  • Page 59 Configuring the DeviceNet Network 1. Double-click the 1747-SDN module icon and select the Input tab. 2. Select M File in the Memory field. 3. Highlight the RediSTATION operator interface and the photoeye and click AutoMap. The resulting device mapping appears in the lower panel. Photoeye RediSTATION inputs...
  • Page 60 Configuring the DeviceNet Network Recall from Chapter 2 that the START button is bit 1 and the STOP button is bit 0. Therefore, the addresses for the RediSTATION inputs are: START - M1:2.0.1 STOP - M1:2.0.0 The input from the photoeye appears in the M1 file for the device in slot 2 as word 0, bits 8…15.
  • Page 61 Configuring the DeviceNet Network 5. Select the Output tab. After mapping, the RediSTATION output address appears here. 6. Select M File in the Memory field. 7. Highlight the RediSTATION operator interface and click AutoMap. In this example, the output to the RediSTATION operator interface appears in the M0 file for the device in slot 2 as word 0, bits 0…7.

  • Page 62: What's Next

    Configuring the DeviceNet Network Download and Save Your Configuration 1. Click the Scanlist tab and then Download to Scanner. 2. Select All Records. 3. Click Download to download the configuration to the 1747-SDN module. 4. Click OK to complete the DeviceNet scanner configuration. 5.

  • Page 63: What This Chapter Contains

    Chapter Communicating with the DeviceNet Network from Another Network What This Chapter Contains This chapter describes how to communicate with the DeviceNet network from another network, by using the SLC 500 pass-through feature. This feature can be used to adjust and fine tune the nodes on your network.

  • Page 64: Additional Resources

    Communicating with the DeviceNet Network from Another Network Additional Resources These documents contain additional information on configuring other networks. Resource Description SLC Modular Style Hardware Installation and Operation Manual, Provides information about the Data Highway Plus network. publication 1747-UM011 Ethernet SLC 500 Processors Quick Start for Experienced Users, Provides information about the Ethernet interface.

  • Page 65: Communicating With The Devicenet Network Via An Ethernet Network

    Communicating with the DeviceNet Network from Another Network The SLC 500 chassis used for these examples was set up with the following hardware mapping. The SLC 5/04 processor was used for the DH+ example. The SLC 5/05 processor was used for the Ethernet example.
  • Page 66 Communicating with the DeviceNet Network from Another Network Configure the Ethernet Devices Driver To communicate with your SLC 500 processor over the Ethernet network you must configure the Ethernet to SLC 500 driver. Follow these steps to configure the driver by using RSLinx software. 1.
  • Page 67 Communicating with the DeviceNet Network from Another Network You are prompted to choose a name for the new driver. 4. Enter an appropriate driver name (for example, AB_ETH-1) and click OK. The Configure driver for Ethernet to PLC-5/SLC-5/5820-EI dialog opens. 5.
  • Page 68 Communicating with the DeviceNet Network from Another Network 6. Click Accept and then OK. The new driver is added to the list of Configured Drivers in RSLinx software. (Your list contains the drivers you have configured.) Configure the DeviceNet Network Pass-through Driver Before you can communicate with the 1747-SDN module via the Ethernet network, you must configure the DeviceNet pass-through driver (catalog number 1747-SDNPT) by using RSLinx software,...
  • Page 69 3. From the Available Driver Types pull-down menu, select DeviceNet Drivers and click Add New. The following list of drivers appears. 4. Select the Allen-Bradley 1747-SDNPT driver. The Allen-Bradley 1747-SDNPT Driver Configuration dialog opens. 5. From the 1747-SDN Slot pull-down menu, select a pass-through port to be configured, for example Slot 2.
  • Page 70 Communicating with the DeviceNet Network from Another Network 8. Click OK. You are prompted to enter a name for the driver. 9. Enter an appropriate driver name (for example, 1747-SDNPT-2) and click OK. The new driver is added to the list of Configured Drivers in RSLinx software.
  • Page 71 Communicating with the DeviceNet Network from Another Network 1. Start RSNetWorx for DeviceNet software. 2. From the File menu, choose New. You may see the following dialog if you have the ControlNet network configured on your system. Otherwise, proceed to step 4.
  • Page 72 Communicating with the DeviceNet Network from Another Network The Browse for network dialog appears. You see the drivers you have configured on your system. 5. Highlight 1747-SDNPT-2, DeviceNet driver and click OK. You receive the following prompt. 6. Click OK to upload the devices. RSNetWorx for DeviceNet software begins browsing for network devices.

  • Page 73: Communicate With The Devicenet Network Via A Dh+ Network

    Communicating with the DeviceNet Network from Another Network You are now online to the DeviceNet network via the Ethernet network. See pages 55…62 of this manual for examples of how to use RSNetWorx for DeviceNet software to adjust network parameters. Communicate with the Before performing this example, the DH+ network must be configured and running.
  • Page 74 3. From the Available Driver Types pull-down menu, select DeviceNet Drivers and click Add New. You see the following list of drivers. 4. Select the Allen-Bradley 1747-SDNPT driver. The Driver Configuration dialog appears. 5. From the 1747-SDN Slot pull-down menu, select a pass-through port to be configured, for example Slot 3.
  • Page 75 Communicating with the DeviceNet Network from Another Network 6. Expand your DH+ driver (AB_KT-1 above) and select the SLC 500 processor. 7. Verify that the 1747-SDN Slot is correct. 8. Click OK. You are prompted to enter a name for the driver. 9.
  • Page 76 Communicating with the DeviceNet Network from Another Network 1. Start RSNetWorx for DeviceNet software. 2. From the File menu, choose New. If you have the ControlNet network configured on your system, you may see the following dialog. Otherwise, proceed to step 4. 3.
  • Page 77 Communicating with the DeviceNet Network from Another Network The Browse for network dialog appears. You see the drivers you have configured on your system. 5. Select the 1747-SDNPT-3 driver and click OK. You receive the following prompt. 6. Click OK to upload the devices. RSNetWorx for DeviceNet software begins browsing for network devices.

  • Page 78: What's Next

    Communicating with the DeviceNet Network from Another Network You are now online to the DeviceNet network via the Data Highway Plus network. See pages 55…62 of this manual for examples of how to use RSNetWorx for DeviceNet software to adjust network parameters. What’s Next? The next chapter describes how to create and run the example application program to test the DeviceNet network.

  • Page 79: What This Chapter Contains

    Chapter Creating and Running the Example Application Program What This Chapter Contains This chapter describes the procedure to create, download, and run an example ladder logic program to test the DeviceNet network. When the processor is put into Run mode, pressing the START button on the network’s RediSTATION operator interface will cause the red indicator light to come on and stay on until the STOP button is pressed.

  • Page 80: Install The Software

    Creating and Running the Example Application Program Install the Software Follow these steps to install the software. 1. Insert the software CD-ROM installation disk in the drive. The CD-ROM supports Windows Autorun. If you have Autorun configured, the installation automatically starts when you insert the CD-ROM in your drive.
  • Page 81 Creating and Running the Example Application Program 2. From the File menu, choose New. The Select Processor Type dialog opens. 3. Select your processor type from the list (for example, 1747-L542A) and click OK. 4. Enter the following ladder program. Note that the program uses the addresses mapped to the devices by RSNetWorx for DeviceNet software in chapter 4.

  • Page 82: Download And Run The Program

    Creating and Running the Example Application Program Download and Run the You cannot go online to the processor directly over the DeviceNet network. The following sections provide examples of downloading Program and running the program by using these networks: • ControlNet •...
  • Page 83 Creating and Running the Example Application Program 4. Change the SLC 500 processor mode to Run after the download is complete. You must also place the 1747-SDN module in Run mode by IMPORTANT setting the Run Bit (bit 0) in the scanner’s command register. The command register is located at word 0 in the Output image table.
  • Page 84 Creating and Running the Example Application Program Download and Run the Program via an Ethernet Network To communicate with your SLC 5/05 processor over an Ethernet IMPORTANT network you must first configure the processor’s Ethernet communication channel and assign it a unique IP address. See Appendix B for information on configuring the Ethernet communication channel.
  • Page 85 Creating and Running the Example Application Program 5. Double-click the O0 - OUTPUT file under the Data Files folder. You see the 1747-SDN module’s command register (file O:2.0 below). 6. Set bit 0 in the command register to 1, as shown above. 7.
  • Page 86 Creating and Running the Example Application Program Download and Run the Program via a DH+ Network Follow the procedure below to download and run the example program via a DH+ network. 1. From the RSLogix 500 Communication menu, choose System Communication.

  • Page 87: What's Next

    Creating and Running the Example Application Program 6. Double-click the O0 - OUTPUT file under the Data Files folder. You see the 1747-SDN module’s command register (file O:2.0 below). 7. Set bit 0 in the command register to 1. 8. Press and release the START button on the RediSTATION operator interface.
  • Page 88 Creating and Running the Example Application Program Publication 1747-UM655B-EN-P - June 2007...

  • Page 89: Module Status Indicator

    Chapter Troubleshooting The 1747-SDN interface module is provided with status diagnostic indicators on its front panel. The diagnostics provided by these indicators are described in this chapter. Topic Page Module Status Indicator Network Status Indicator Numeric Display Code Summary Module Status Indicator The bicolor (green/red) Module Status indicator (MODULE) indicates whether the 1747-SDN module has power and is functioning properly.

  • Page 90: Network Status Indicator

    Troubleshooting Network Status Indicator The bicolor (green/red) network status indicator (NET) provides troubleshooting information about the DeviceNet channel communication link. If the NET Then Which indicates Take this action indicator is The device has no power or the channel is The channel is disabled for Power-up the module, provide disabled for communication due to bus off...
  • Page 91 Troubleshooting Numeric Display Numeric Description Corrective Action Code 0…63 Normal operation. The numeric display indicates the None. 1747-SDN module’s node address on the DeviceNet network. Normal operation when AutoScan is enabled. None. Module failed Duplicate Node Address check. Change the module channel address to another available one.
  • Page 92 Troubleshooting Numeric Display Numeric Description Corrective Action Code Device is producing zero length data (idle state) while Check device configuration and slave node status. module is in Run mode. The primary owner has not allocated the slave. Put the primary owner online. The connection choices (polled, strobed) between the Reconfigure the shared input-only connection's choices to primary connection and the shared input only connection do...

  • Page 93: Devicenet Explicit Message Instruction Overview

    Chapter DeviceNet Explicit Messaging DeviceNet Explicit The DeviceNet Explicit Message (DEM) instruction allows generic Common Industrial Protocol (CIP) commands to be initiated to Message Instruction devices, such as drives, communicating on DeviceNet networks. This Overview instruction requires RSLogix 500 software, version 7.10 or later, for programming.

  • Page 94: Devicenet Explicit Message (Dem)

    DeviceNet Explicit Messaging DeviceNet Explicit This is an output instruction that lets you initiate unconnected CIP Generic messages via a 1747-SDN module installed in the local Message (DEM) chassis. These messages can be initiated to any node on the same DeviceNet network as the 1747-SDN module, as long as the node is in the scanner’s scanlist.
  • Page 95 DeviceNet Explicit Messaging Parameters for Target Device on the General Tab • Message Timeout(x1 sec) The amount of time in seconds that the processor will wait for a reply from the scanner to the explicit message command. Range is 0, 2…255. Like the Message Timeout in a standard MSG instruction, a value of 0 disables the Message Timeout and a value of 1 second gets bumped to 2 seconds upon instruction execution.
  • Page 96 DeviceNet Explicit Messaging • Class (hex)/(dec) Possible Classes are 0…FF (hex). See Volume 1 of the CIP Common Specification for the list of defined Classes. You may either enter in a hexadecimal Class value in the (hex) field or a decimal Class value in the (dec) field. •...
  • Page 97 DeviceNet Explicit Messaging DEM Instruction Setup Screen Status Bits Bit Definition Bit Mnemonic Bit Address Done Enabled Waiting for slot • Abort bit AB (word 0, bit 8) lets you abort an executing DEM instruction by setting this bit. The ER bit will be set as soon as the AB bit is set.
  • Page 98 DeviceNet Explicit Messaging Scanner Status, Error, and Error Description on the General Tab The error code displays the explicit message status returned by the module. An error code of 01h means Transaction completed successfully. DEM Instruction Scanner Codes Scanner Code Description of Scanner Status Transaction in progress.
  • Page 99 DeviceNet Explicit Messaging CIP Response Error Codes Numeric Code Name Description Resource unavailable A needed resource was not available Service unsupported Service is not defined or implemented for this class/instance Invalid attribute value Data is invalid for the specified attribute Already in requested state Object is in the requested state - redundant request Object state conflict...
  • Page 100 DeviceNet Explicit Messaging Send Data Tab The Send Data Tab provides a convenient way of viewing and entering in data to be sent along with the explicit message command. The data is shown in byte format with a selectable radix of either decimal or hex/BCD.
  • Page 101 DeviceNet Explicit Messaging Control Block Layout The control block layout is shown below. SLC 5/0x DeviceNet Explicit Message (DEM) Control Block Structure Word 0 Error Code Word 1 Message Timeout Preset Word 2 Message Timeout Accumulator Word 3 Message Timer Scaled Zero Word 4 Unused Word 5...
  • Page 102 DeviceNet Explicit Messaging Publication 1747-UM655B-EN-P - June 2007...

  • Page 103: Chapter 9 Overview

    Chapter AutoScan Overview The DeviceNet network AutoScan feature enables a scanner to automatically map a network of slave devices into its scanlist without the use of RSNetWorx for DeviceNet software. This greatly improves the ease of setting up a DeviceNet network, especially networks comprised of simple devices.
  • Page 104 AutoScan The diagram below shows an example system using the 1747-SDN module. The node addresses can be commissioned via hardware switches on the device or through other DeviceNet configurators such as the 193-DNCT DeviceNet Configuration terminal. Refer to the DeviceNet Programming Terminal user manual, publication 193-UM009, for more information on how to set up node addresses.
  • Page 105 AutoScan However, for applications where you would like to customize the I/O allocation size, configure a DEM instruction to adjust the 4-byte allocation. 2. Fill in the fields as shown, make sure to match the 1747-SDN module’s Slot and DeviceNet Address to your particular scanner module.
  • Page 106 AutoScan 4. On the DEM instruction setup screen to initiate AutoScan, fill in the fields as follows. Make sure to match the 1747-SDN Slot and DeviceNet Address to your particular scanner module. All other fields should appear exactly as shown above. 5.
  • Page 107 AutoScan The only difference between the Enable AutoScan and Disable AutoScan DEM instructions is that a 0 is sent to Disable AutoScan. 7. Download the program and then trigger each DEM instruction individually, 8. Verify that the scanner status display has stabilized prior to executing the next DEM instruction.
  • Page 108 AutoScan 9. Return the scanner to Run mode (bit 0 in the scanner control output word is set to 1) and the scanner status display should be displaying the scanner node address. If the status display is flashing other codes as well, refer Chapter 7 for troubleshooting.
  • Page 109 AutoScan 6. On the Auto Scan Setup screen, change AutoScan from Disable to Enable by pressing either the C/Up-arrow key or the D/Down-arrow key. 7. Press the B/SEL key to scroll down to Mapping. 8. Type in the number of bytes that you want to automap to each DeviceNet node (1…32).
  • Page 110 AutoScan How AutoScan Operates AutoScan is active when the feature is enabled and the scanner is in Idle mode. When active, the scanner attempts to connect to each device not enabled in the scanlist. The scanner only checks for devices with node addresses between 0…61, inclusive. The connections to these devices are made on a round robin basis.
  • Page 111 AutoScan When using five bytes for each device, the input data for EXAMPLE devices are allocated in the 1747-SDN module's input table. Note that M files are used because discrete mapping is not used with the AutoScan feature. In this case node 15 has an offset of 15*5=75 byte, therefore node 15 data is located in the data map at word 75/2 = 37.5 of the M file with the non-integer result the offset starts at the upper byte of the word.

  • Page 112: Other Important Information About Autoscan

    AutoScan Other Important Information The factory default setting for AutoScan is disabled for all products. about AutoScan Make sure that input or output data memory size in the scanner is large enough to accommodate the size required based on the number of nodes on the network and the AutoScan I/O allocation size per node.
  • Page 113 AutoScan Scanlist Data Max Node Data Max Node Allocation Allocation (bytes) (bytes) The AutoScan feature will automatically be disabled in the scanner as soon as a scanner property is modified by RSNetWorx for DeviceNet software. For example, any manual changes to the scanlist using RSNetWorx software will disable the AutoScan feature in the scanner.
  • Page 114 AutoScan When a scanner is transitioned from Run mode to Idle mode while AutoScan is enabled, it only scans the network for nodes that are not already in the scanlist. However, while in Idle mode, an AutoScan Disable mode to Enable mode transition will cause the scanner to erase the existing scanlist and scan for all nodes on the network.

  • Page 115: What This Appendix Contains

    Appendix Data Map Example What This Appendix This appendix illustrates a basic mapping example that connects a DeviceNet network to 62 simple sensor-type devices. Each device Contains sends one data byte that contains one data bit and one status bit. These are given in response to a strobe message.
  • Page 116 Data Map Example Example Framework This example adheres to the following structure: • There cannot be any 1771-SDN modules or other 1747-SDN modules on that network. • DeviceNet devices may reside only at nodes 1…62. • Address 0 must be used for the scanner. •...
  • Page 117 Data Map Example DeviceNet Message from Node #11 1 byte 1747-SDN Module Discrete-input Data Table 0 Word 0 SLC Processor Input Image Table Word 1 Word 2 Word 0 Status Word 3 Word 4 Words 1…31 DeviceNet Input Data (31 Words) Word 1 Word 2 SLC Processor M1 File...

  • Page 118: Example Output Mapping Scheme

    Data Map Example Example Output Mapping This example’s output mapping scheme is a simplified and fixed map of the discrete outputs and data from the device output data table to Scheme DeviceNet devices. Devices present in the default database are strobed only; therefore, the output data-map bits are mapped into each network’s strobe message.
  • Page 119 Data Map Example The processor writes output data for each scanned device in the scanner's discrete-output data table. The scanner then maps each bit into a strobe message that is sent to all scanned devices. The bit number, where a particular device's data is mapped, directly corresponds to that device's MAC ID.
  • Page 120 Data Map Example Publication 1747-UM655B-EN-P - June 2007...

  • Page 121: Rslogix 500 I/O Configuration

    Appendix Configuring the M0/M1 Files by Using RSLogix 500 Software RSLogix 500 I/O To enable pass-through access by using a SLC 500 processor, you must configure the M0 and M1 files associated with the 1747-SDN Configuration module at a minimum length of 361 words. Follow these steps to configure the 1747-SDN module’s M0 and M1 files by using RSLogix 500 software.
  • Page 122 Configuring the M0/M1 Files by Using RSLogix 500 Software 3. Click Read I/O Config to upload the I/O configuration from the processor. 4. Double-click the 1747-SDN module. The Advanced I/O Configuration dialog opens. 5. Set the MO Length and the M1 Length to 361 (or greater) as shown above.

  • Page 123: Programming The Module By Using The Slc M0 And M1 Files

    Configuring the M0/M1 Files by Using RSLogix 500 Software Programming the Module The M0 and M1 files are data files that reside in the module. There is no image for these files in the processor memory. The M0 file is a by Using the SLC M0 and module output file and the M1 file is a module input file.
  • Page 124 Configuring the M0/M1 Files by Using RSLogix 500 Software When You Cannot Use M0-M1 Data File Addresses You can use M0 and M1 data file addresses in all instructions except the OSR instruction and the instruction parameters below. Instruction Parameter (characterized by file indicator #) File (bit array) File (sequencer file)
  • Page 125 Configuring the M0/M1 Files by Using RSLogix 500 Software To show the state of the M0 or M1 addressed bit, transfer the state to an internal processor bit. This is illustrated below, where an internal processor bit is used to indicate the true/false state of a rung. M0:3.0 EQUAL Source A...
  • Page 126 Configuring the M0/M1 Files by Using RSLogix 500 Software The COP instruction below copies six words of data from an M1 data file in a module positioned in slot four to an integer file (N1:0). This technique is used to monitor the contents of an M0 or M1 data file indirectly, in a processor data file.
  • Page 127 Configuring the M0/M1 Files by Using RSLogix 500 Software The first two ladder diagrams in the last section illustrate a technique you use to capture and use M0 or M1 data as it exists at a specific time. In the first diagram, bit M1:2.1/1 could change state between rungs 1 and 2.
  • Page 128 Configuring the M0/M1 Files by Using RSLogix 500 Software Publication 1747-UM655B-EN-P - June 2007...

  • Page 129: Appendix C Purpose

    Appendix 1747-SDN Module Firmware History Purpose This section describes enhancements, corrected anomalies and other important information for this revision and previous revisions of the 1747-SDN module firmware. Revision 8.002 The 1747-SDN series C module includes these firmware enhancements. • Embedded EDS file - The module contains its own electronic data sheet (EDS) file within its firmware.

  • Page 130: Revision 6.002

    1747-SDN Module Firmware History • If a slave in the scanlist does not match the identity of the slave at that address on the network, the module does not communicate with that slave again. After the mismatch is resolved, you have to cycle power to the module to reestablish communication.
  • Page 131 1747-SDN Module Firmware History Enhancements This section describes the enhancements to the firmware. Enhanced Explicit Message Pass-through Capability With the 6.002 firmware revision, the size of the M0/M1 file could be expanded to 395 words. This can accommodate a larger pass-through message than previous firmware revisions.

  • Page 132: Revision 5.001

    1747-SDN Module Firmware History Revision 5.001 This section describes the enhancements for firmware revision 5.001. Enhancement The following enhancement was made to the firmware for this revision. Scanlist Commit in Run/Idle Mode With the 5.001 firmware revision, with the module in Idle mode, the scanlist can be committed to the module’s memory while the programmable controller is in Run mode.

  • Page 133: Understand The Data Organization Of The Module

    Appendix Data Organization Understand the Data The module has four data areas to transfer data, status, and command information between the module and the processor. Organization of the Module • SLC input image table • SLC output image table • SLC M1 file •...

  • Page 134: Upload Input Data From The Module To The Slc Processor

    Data Organization Upload Input Data from the The SLC 500 processor reads input data from the module by using two methods. Module to the SLC Processor • Input image table • M1 file transfer Input Image Table The input image table is a 32-word table for the module slot that is updated by the processor with each program scan.
  • Page 135 Data Organization Bit Table Status Word I:s.0 Operating Mode Description Operating Mode 1 = Run mode, 0 = Idle mode (echoed from the module The module maps output data from its scanner output table (M0) and discrete outputs to command register) each device on the network.
  • Page 136 Data Organization SLC M1 File The SLC M1 file is a file with up to 256 words or more that can be used to transfer a large quantity of information to the module with a single SLC instruction. Transferring data using this file takes more time than using the IMPORTANT input image table.
  • Page 137 Data Organization Scan Counter Word 211 is used for the module scan counter. The module increments this counter whenever a scan of the DeviceNet devices is completed. The counter rolls over when it reaches a maximum value of 65,535. It is located at M1:S.211. Device Idle Table Words 212…215 in the M1 file are used for the device idle table.

  • Page 138: Download Output Data To The Module

    Data Organization Explicit Message Program Control Words 224…255 are used for Explicit Message Program Control. Use this feature to configure device parameters on your DeviceNet network via the M0 and M1 files in the SLC processor that is controlling these devices. Download Output Data to The SLC 500 processor writes output data to the module by using two methods.
  • Page 139 Data Organization Command Register Bits Command Word 0:S.0 Operating Mode Description Operating Mode 1 = Run mode 0 = Idle mode The module maps output data from its scanner output table (M0) and discrete outputs to each device on the network. Inputs are received and mapped into the scanner input table (M1) and discrete inputs. Outputs on the network are under SLC program control.
  • Page 140 Data Organization Restore Factory Default Settings/Flush Memory Follow these steps to restore the module’s factory default settings. 1. While the SLC processor in Program mode, clear the module command word 0 and set bit 2 of word 0 for the module to ON or 1 (starting with bit 0 going from right to left, this is the third bit).
  • Page 141 Data Organization SLC M0 File The SLC M0 file is a 256 word file that can be used to transfer a large quantity of information to the module with a single SLC instruction. Transferring data by using this file can take several scans and more time than by using the output image table.
  • Page 142 Data Organization Publication 1747-UM655B-EN-P - June 2007...

  • Page 143: Using Explicit Message Program Control

    Appendix Explicit Message Program Control Using Explicit Message Use the Explicit Message Program Control feature to configure device parameters on your DeviceNet network via the M0 and M1 files. Program Control Use the Explicit Message Program Control feature to: • transmit configuration data from your module to its slave devices on your DeviceNet network.

  • Page 144: Publication 1747-Um655B-En-P - June

    Explicit Message Program Control How the Explicit Message Program Control Feature Works Explicit Message - A message used to MO file transfer (including words 224…255) transmit commands, data, requests for (sent from processor to module). data or responses. The message is sent from a client on the DeviceNet network to a server on that network.
  • Page 145 Explicit Message Program Control The module requires a precisely-formatted M0 and M1 file transfer size of 32 words including words 224…255. The module uses the file memory content as a client/server request. How to Format the Explicit Message Transaction Block Up to ten 32-word transaction blocks may be queued within the module for Explicit Message Program Control.
  • Page 146 Explicit Message Program Control Command Code Description Ignore transaction block (block empty) Execute this transaction block Get status of transaction TXID Reset all client/server transactions Delete transaction from response queue 5…255 Reserved For each upload, the status code provides the processor with status on the device and its response.
  • Page 147 Explicit Message Program Control • TXID (transaction ID) – when you create and download a request to the scanner, the processor’s ladder logic program assigns a TXID to the transaction. This is a one-byte integer in the range of 1…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.
  • Page 148 Explicit Message Program Control The following figure describes the format and mapping of transaction blocks for request and response messages in the module. Transaction Blocks Format of 32-word M0 Transfer File for Format of 32-word M1 Transfer File for Explicit Message Request Explicit Message Response TXID CMD/Status...
  • Page 149 Explicit Message Program Control Message lengths and slave device types impact transaction message completion times. If the processor has queued multiple Explicit Message Transactions to the module for multiple slave devices, the transactions with the slaves may not complete in the order in which the requests were received.
  • Page 150 Explicit Message Program Control As transactions are removed from the queue and response transaction blocks are returned to the processor, additional transaction blocks can be issued in their place, as long as the total does not exceed ten. • The module supports one transaction block per upload and download.
  • Page 151 Explicit Message Program Control Explicit Messaging Error Codes Error codes have two bytes of data. The first byte is a General Error Code and the second is an optional Additional Code Field that may contain additional information about the error. If this field is unused, the value 0FFH is shown.
  • Page 152 Explicit Message Program Control Publication 1747-UM655B-EN-P - June 2007...

  • Page 153: Glossary

    Glossary Bridge The module’s support of explicit message transfer. Background Poll Ratio Sets the frequency of poll messages to a device in relation to the number of I/O scans. For example, if the ratio is set at 10, that device will be polled once every 10 scans.
  • Page 154 Glossary Host Platform The computer on which the application software is run. An abbreviation for input and output. Implicit Messaging The type of messaging used for high-priority I/O control data; for example, change of state, cyclic, polled, or strobed. Input Data Data produced by a DeviceNet device and collected by the module for the host platform to read.

  • Page 155: Glossary

    Glossary Online When the host platform is configured and enabled to communicate on the network. Output Data Data produced by the host platform that is written to the module’s memory. This data is sent by the module to DeviceNet devices. Polled A type of input/output-data communication.

  • Page 156: Glossary

    Glossary An abbreviation for transmit. Publication 1747-UM655B-EN-P - June 2007...

  • Page 157: Index

    Index instruction parameters 94 setup parameters 94 automapping 58 download output data to module 138 autoscan 103 implementing 103 important information 112 operation 110 example application 10 overview 103 devices 25 example network 24 system components 10 example application program before you begin 13 creating the program 80 downloading and running the program 82...

  • Page 158: Index

    Index installation 47 RSNetWorx for DeviceNet software M0/M1 file configuration 121 as a configuration tool 20 program the module 123 configuration screen map 21 module features 40 configuring the DeviceNet network 50 module status indicator 89 installation 47 network status indicator 90 scanlist configuration 55 numeric display code 90 Series 9000 photoeye...
  • Page 160 Rockwell Automation Rockwell Automation provides technical information on the Web to assist you in using its products. At http://support.rockwellautomation.com, you can Support find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.

This manual is also suitable for:

C series

Table of Contents