769-SDN DeviceNet Scanner Module Catalog Numbers 1769-SDN User Manual
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://www.rockwellautomation.com/literature/) describes some important differences between solid state equipment and hard-wired electromechanical devices.
Summary of Changes The information below summarizes the changes to this manual since the last printing. We have included change bars as shown to the right of this paragraph to help you find new and updated information in this release of the manual. The table below lists the changes that have been made to this revision of the manual.
Summary of Changes 4 Publication 1769-UM009E-EN-P - August 2009
Table of Contents Preface About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Who Should Use This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Conventions in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Chapter 1 Overview Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 4 Automatically Configure a DeviceNet Network Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 How AutoScan Operates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Determine If You Can Use AutoScan. . . . . . . . . . . . . . . . . . . . . . . . . . 38 How AutoScan Effects Your Network. . . . . . . . . . . . . . . . . . . . . . . . . 38 Connect Each Device to the Network . . . . . . . . . . . .
Table of Contents Chapter 6 DeviceNet I/O Image Publication 1769-UM009E-EN-P - August 2009 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 1769-SDN Input Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 MicroLogix 1500 Status Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Scan Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 MicroLogix 1500 Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 RSLogix 500 Programming Software I/O Configuration . . . . . . . . . 104 Start the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 I/O Configuration Screen . . . . . . . . . . .
Preface Read this preface to familiarize yourself with the rest of the manual. About This Manual This manual is a user manual for the Compact I/O 1769-SDN DeviceNet scanner module. It describes the procedures you use to install, program, and troubleshoot your scanner module. This manual: • provides instructions on installing the scanner module. • contains information about using the scanner module on the DeviceNet network. • provides tips on troubleshooting the scanner module.
Preface Preface Conventions in This Manual The following conventions are used throughout this manual: • Bulleted lists such as this one provide information, not procedural steps. • Numbered lists provide sequential steps or hierarchical information. Additional Resources The following documents contain additional information concerning Rockwell Automation products. Contact your local Rockwell Automation distributor to order hard copy publications. For electronic copies, go to http://literature.
Chapter 1 Overview Introduction This chapter provides an overview of communication between the CompactLogix and MicroLogix 1500 programmable controllers and DeviceNet devices via the 1769-SDN scanner module.
Chapter 1 Overview Module Features Use the following figure to identify the features of the scanner.
Overview Scanner Module Operation Chapter 1 In a typical configuration, the scanner module acts as an interface between DeviceNet devices and the programmable controller.
Chapter 1 Overview Communication with Your Slave Devices The scanner module communicates with devices via strobe, poll, change of state, or cyclic I/O messages. It uses these messages to solicit data from or deliver data to each device. Data received from the devices, input data, is organized by the scanner module and made available to the controller. Data sent from your controller, output data, is organized in the scanner module and sent on to your devices.
Overview 1769-SDN Scanner Module Data Tables Chapter 1 The scanner module uses input and output data images to transfer data, status, and command information between the scanner module and the MicroLogix controller to manage the flow of data between your controller and network devices. Input Data Image - MicroLogix 1500 The input data image is transferred from the scanner module to the controller across the Compact I/O bus.
Chapter 1 Overview Module Command Array Bit Assignments Output Word Bit Description Behavior 0 0 Run This bit controls when the module scans its mapped slave devices. When set (1), the scanner module will process I/O data as defined by its scanlist. The Fault and Disable Network command bits must be clear (0) to scan the network. 1 Fault When set, the scanner’s I/O mode will be Halt; messaging will still operate.
Overview RSNetWorx for DeviceNet Software as a Configuration Tool Chapter 1 RSNetWorx for DeviceNet software is used to configure the scanner’s slave devices. This software tool connects to the scanner module over the DeviceNet network via an RS-232 interface (1770-KFD module) or PC card (1784-PCD or 1784-PCID). We recommend RSNetworx for DeviceNet software, version 3.00 or later. If your RSNetWorx configuration software does not include the required electronic data sheet (EDS) file, go to http://www.ab.
Chapter 1 Overview RSNetWorx Configuration Dialog Map The main RSNetWorx dialog. Click Online and select the driver to browse the network. Double-click the 1769-SDN icon to access the 1769-SDN scanner module. Click on the Scanlist tab to access the scanlist. Click the Input tab and click the AutoMap button to automatically map input devices. Move the device into the scanlist. Click Download to Scanner to download the scanlist.
Chapter 2 Quick Start for Experienced Users Introduction This chapter helps you get started using the 1769-SDN scanner module. Topic Page Required Tools and Equipment 19 What You Need to Do 20 Procedures are based on the assumption that you have an understanding of Rockwell Automation controllers. You should understand electronic process control and be able to interpret the ladder logic instructions required to generate the electronic signals that control your application.
Chapter 2 Quick Start for Experienced Users What You Need to Do Follow these steps to get started using the 1769-SDN scanner module. 1. Verify planned system configuration. a. Ensure system power supply has sufficient current. Maximum Current Draw Module 5V DC 24V DC 1769-SDN 440 mA 0 mA The scanner module cannot be located more than four modules away from the system power supply. b. Verify that the DeviceNet network has adequate power.
Quick Start for Experienced Users Chapter 2 3. Assemble and mount the I/O bank. The scanner module can be attached to an adjacent controller, power supply, or I/O module. The scanner module can be panel or DIN-rail mounted. Modules can be assembled before or after mounting. Be sure to observe minimum spacing guidelines for adequate ventilation. 4. Ground the scanner module and complete the DeviceNet network wiring. 5. Apply power to the system. 6.
Chapter 2 Quick Start for Experienced Users Notes: 22 Publication 1769-UM009E-EN-P - August 2009
Chapter 3 Installation and Wiring This chapter describes how to install and wire the 1769-SDN scanner module. This table describes what this chapter contains and where to find specific information.
Chapter 3 Installation and Wiring General Considerations The Compact I/O system is suitable for use in an industrial environment when installed in accordance with these instructions. Specifically, this equipment is intended for use in clean, dry environments (Pollution Degree 2(1)) and to circuits not exceeding Over Voltage Category II(2) (IEC 60664-1).(3) Hazardous Location Considerations This equipment is suitable for use in Class I, Division 2, Groups A, B, C, D or nonhazardous locations only.
Installation and Wiring Chapter 3 Preventing Electrostatic Discharge ATTENTION Electrostatic discharge (ESD) can damage integrated circuits or semiconductors if you touch the bus connector pins. Follow these guidelines when you handle the module: • Touch a grounded object to discharge static potential. • Wear an approved wrist-strap grounding device. • Do not touch the bus connector or connector pins. • Do not touch circuit components inside the module. • Use a static-safe work station, if available.
Chapter 3 Installation and Wiring Protecting the Circuit Board from Contamination The printed circuit boards of the modules must be protected from dirt, oil, moisture, and other airborne contaminants. We recommend installing the system in an enclosure suitable for the environment to protect these boards. The interior of the enclosure should be kept clean and the enclosure door should be kept closed whenever possible.
Installation and Wiring System Assembly Chapter 3 The scanner module can be attached to an adjacent controller, power supply, or I/O module. This procedure shows you how to assemble the Compact I/O system. A D E C B G B F 1. Disconnect power. 2. Check that the bus lever of the scanner module (A) is in the unlocked (fully right) position. 3. Use the upper and lower tongue-and-groove slots (B) to secure the modules together. 4.
Chapter 3 Installation and Wiring System Mounting During panel or DIN rail mounting of all devices, be sure that all debris (metal chips, wire strands) is prevented from falling into the module. Debris that falls into the module could cause damage at power up. ATTENTION Minimum Spacing Maintain spacing from enclosure walls, wireways, and adjacent equipment. Allow 50 mm (2 in.) of space on all sides for adequate ventilation, as shown below.
Installation and Wiring Chapter 3 Panel Mounting Using the Dimensional Drawing All dimensions are in millimeters (inches). Hole spacing tolerance: ±0.4 mm (0.016 in.). Compact I/O System with L35E CompactLogix Controller and Power Supply 67.5 mm (2.68 in) 15 mm (0.59 in) 70.0 mm (2.76 in) 52.5 mm (2.06 in) 35.0 mm (1.38 in) 132 mm (5.20 in) 118 mm (4.65 in) 52.5 mm (2.07 in) 35.0 mm (1.38 in) 35.0 mm (1.38 in) 35.0 mm (1.38 in) 35.0 mm (1.
Chapter 3 Installation and Wiring Panel Mounting Procedure Using Modules as a Template This procedure lets you use the assembled modules as a template for drilling holes in the panel. Due to module mounting hole tolerance, it is important to follow these procedures. 1. On a clean work surface, assemble no more than three modules. 2. Using the assembled modules as a template, carefully mark the center of all module-mounting holes on the panel. 3.
Installation and Wiring Replace the Scanner Module within a System Chapter 3 The scanner module can be replaced while the system is mounted to a panel (or DIN rail) once power is removed. 1. Remove power. 2. Remove the DeviceNet cable from the scanner module by removing the DeviceNet connector. 3. Remove the upper and lower mounting screws from the scanner module (or open the DIN rail latches using a flat-blade screwdriver). 4.
Chapter 3 Installation and Wiring Field Wiring Connections Follow these procedures to wire the scanner module. Grounding the Scanner Module This product is intended to be mounted to a well-grounded mounting surface, such as a metal panel. Additional grounding connections from the scanner’s mounting tabs or DIN rail (if used), are not required unless the mounting surface cannot be grounded.
Installation and Wiring Chapter 3 1. Connect the DeviceNet cable to the removable connector as shown. 2. Insert the removable female connector into the mating male connector on the DeviceNet scanner module. 3. Screw the removable connector to the scanner module case with the upper and lower mounting screws to a torque of 0.6...0.7 Nm (5...6 in-lbs).
Chapter 3 Installation and Wiring Notes: 34 Publication 1769-UM009E-EN-P - August 2009
Chapter 4 Automatically Configure a DeviceNet Network Introduction This chapter provides a quick method for configuring a DeviceNet network. It uses the AutoScan feature to establish communication between the controller and your devices with minimal steps.
Chapter 4 Automatically Configure a DeviceNet Network 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 scan list. The scanner only checks for devices with node addresses between 0 and 61, inclusive. The connections to these devices are made on a round robin basis.
Automatically Configure a DeviceNet Network Chapter 4 The input and output data is mapped into the scanner's I/O data table based on the device's node address and the configured fixed mapping size.
Chapter 4 Automatically Configure a DeviceNet Network Make sure your network meets the following requirements to use this chapter: Determine If You Can Use AutoScan • The scanner’s I/O allocation size is configured to accommodate the input and output data sizes of all devices on your DeviceNet network. The default AutoScan setting allocates a 4-byte entry in both the input and output memory maps in the scanner for each slave device detected on the network.
Automatically Configure a DeviceNet Network Chapter 4 Consideration Description New devices are automatically available. While the scanner is in idle mode, AutoScan continues to establish communication with devices that you connect to the network, as long as the device uses input data and output data sizes that fit in the scanner’s I/O allocation size. The Automatic Device Recovery (ADR) option is not available.
Chapter 4 Automatically Configure a DeviceNet Network 3. Connect the rest of your devices to the network one at a time. • Out of the box, a DeviceNet device is preset for address 63. Connect and set the devices one at a time to set the scanner’s DeviceNet address. Otherwise the address conflicts may prevent communication with them. • If a device has a switch to set its baud rate, set the switch to autobaud, if available. Otherwise, set the device to the baud rate of the network.
Automatically Configure a DeviceNet Network IMPORTANT Chapter 4 The 193-DNCT terminal is shipped so that when it is placed on a DeviceNet network for the first time, it automatically sets its baud rate to that of the traffic on the network. The terminal uses Auto Addressing to assign itself an unused network node address. After 10 seconds a Network Who screen similar to the example shown below should appear that displays all Nodes and associated devices on the network.
Chapter 4 Automatically Configure a DeviceNet Network Set the Node Address of a Device Via a DeviceNet Configuration Terminal Follow these steps to set the node address of a device on your DeviceNet network via the 193-DNCT terminal. 1. Connect the 193-DNCT terminal to the network. The following display should appear for 10 seconds that shows the unit setup and the baud rate and node number values it has determined.
Automatically Configure a DeviceNet Network Chapter 4 5. Press and a screen appears with the NodeComm option highlighted. 6. Press and the Node Commissioning screen appears as shown below with the BaudRate option highlighted. 7. Because you do not need to change the baud rate, press advance to the Address option and highlight it. to 8.
Chapter 4 Automatically Configure a DeviceNet Network Add the scanner to the I/O configuration of the controller to access the data of your network. Add the Scanner to the RSLogix 5000 Project Add the Scanner to the I/O Configuration Folder 1. Right-click and choose New Module. 2. Choose the type of scanner. 3. Click OK.
Automatically Configure a DeviceNet Network Chapter 4 4. Select the Major revision of the scanner. 5. Click OK. 4 5 Define the Properties of the Scanner 1. Name the scanner. 2. Set the scanner Minor Revision. 3. Choose the size of the input and output memory maps that the scanner will allocate for each device it detects on the network. Valid values range from 0 to 32 bytes per node. 4.
Chapter 4 Automatically Configure a DeviceNet Network Implement AutoScan Make sure that the appropriate version of DeviceNet scanner is used to implement this feature. You must use the CompactLogix 1769-SDN DeviceNet scanner with firmware revision 4.1 or greater This section describes how to set up the feature and how it operates. Notice that explicit messaging is used for some of the steps. There are several ways that an explicit message can be sent on DeviceNet.
Automatically Configure a DeviceNet Network Chapter 4 2. Set up I/O allocation size in the scanner. This step is optional. TIP The default AutoScan setting allocates a 4-byte entry in both the input and output memory maps in the scanner for each slave device detected on the network. This default size is chosen to accommodate the default Logix native data size of 32 bits (DINT). If that is adequate for the application, skip to step 3.
Chapter 4 Automatically Configure a DeviceNet Network Configure I/O Allocation Size Via the User Program Use the parameters shown in the MSG message setup screen below to adjust the I/O allocation size. Make sure that the message is sent to the appropriate DeviceNet Scanner.
Automatically Configure a DeviceNet Network Chapter 4 Initiate AutoScan Via the User Program Follow these steps to initiate AutoScan using a MSG instruction. 1. Verify that the scanner is in IDLE mode, that is bit 0 in the scanner control output word = 0, and that all slave nodes are connected to and communicating on the DeviceNet network. 2. In the RSLogix 5000 programming software Tag Editor, create new tags to initiate AutoScan via ladder programming as shown in the example below. 3.
Chapter 4 Automatically Configure a DeviceNet Network 5. Set the path to your DeviceNet scanner. 6. Return the scanner to Run mode, that is bit 0 in the scanner control output word = 1, and the scanner status display should display the scanner node address. The previous example is from RSLogix 5000 programming software; refer to the appropriate user manuals to determine how to perform explicit messaging in other PLC platforms.
Automatically Configure a DeviceNet Network Chapter 4 Initiate AutoScan via the 193-DNCT Terminal Follow these steps to enable AutoScan using the 193-DNCT terminal, version 2.1 or higher. 1. Put your controller into Program mode, and verify that the scanner is in Idle mode (CommandRegister.Run = 0) and that all slave nodes are connected and communicating on the DeviceNet network. 2. Plug the 193-DNCT terminal into the DeviceNet network. 3.
Chapter 4 Automatically Configure a DeviceNet Network 12. Change AutoScan setting to Enable and press down to Save. IMPORTANT to scroll When setting the AutoScan mode from Disable to Enable, the 1769-SDN scanner clears all existing configuration. Notice that the 1769-SDN module status indicator flashes red and back to green, while the status display momentarily shows 72. When the AutoScanning is complete, the status display blinks between 65 and the node address of the scanner. 13.
Automatically Configure a DeviceNet Network Additional Considerations Regarding AutoScan Chapter 4 The factory default setting for AutoScan is disabled for all products. 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. TIP IMPORTANT Nodes 0…61 inclusive are scanned and added to the scanlist if they are not already mapped and I/O space exists.
Chapter 4 Automatically Configure a DeviceNet Network Scanlist 54 Data Allocation (bytes) Max Node 1 61 2 61 3 61 4 61 5 61 6 60 7 51 8 45 9 40 10 36 11 32 12 30 13 27 14 25 15 24 16 22 17 21 18 20 19 18 20 18 21 17 22 16 23 15 24 15 25 14 26 13 27 13 28 12 29 12 30 12 31 11 32 11 Publication 1769-UM009E-EN-P - August 2009
Automatically Configure a DeviceNet Network Chapter 4 The AutoScan feature is automatically disabled in the scanner as soon as the scanner configuration is modified by RSNetWorx for DeviceNet software. For example, any manual changes to the scanlist using RSNetWorx for DeviceNet software disables the AutoScan feature in the scanner. One new status code has been added to the Node Status list. This code is presented in the Node Status Table.
Chapter 4 Automatically Configure a DeviceNet Network Type of Connection that the Scanner Sets Up The type of update (connection) that the scanner sets up with each device depends on the device. The scanner chooses the first connection type that the device supports in this order: 1. change-of-state (COS) 2. polled 3. strobed 4. cyclic at 1000 ms The scanner tries to set up a change-of-state connection.
Automatically Configure a DeviceNet Network Access Device Data Chapter 4 When you add the scanner to the I/O configuration of the controller, RSLogix 5000 software automatically creates a set of tags for the input, output, and status data of the network: input data from the scanner output data for the scanner status data from the scanner The tags for your DeviceNet data follow this format: location :type .Data IO_offset .
Chapter 4 Automatically Configure a DeviceNet Network While you can use the input and output tags of the scanner directly in your logic, it is a lot easier to use alias tags. alias tag – a tag that represents another tag • Both tags share the same data. • When the data changes, both tags change. • An alias tag provides a descriptive name for data, such as DeviceNet input or output data. As an option, create tags that describe each device without pointing them to the actual addresses of the devices.
Automatically Configure a DeviceNet Network Chapter 4 4. Select the Alias button. 5. Select the tag that this alias tag represents. 6. Select the scope for the alias tag. 7. Choose OK. 4 5 6 7 Select the address of the data. Click ▼ to select a bit. Look in the controller-scoped tags.
Chapter 4 Automatically Configure a DeviceNet Network Put the Scanner in Run Mode Follow these steps to run the DeviceNet network. 1. Place the controller in Run/Remote Run mode. 2. Set the following bit of the output structure for the scanner. If you want to Set this bit To: run the network …O.CommandRegister.Run 1 not run the network (idle mode) …O.CommandRegister.Run 0 3. Check to see if the scanner is in Run mode, by making sure an 80 status code does not appear on the scanner’s display.
Chapter 5 Manually Configure the DeviceNet Network Introduction Software Versions This chapter describes how to configure the DeviceNet network using RSLinx and RSNetWorx for DeviceNet software. This table describes what this chapter contains and where to find specific information.
Chapter 5 Manually Configure the DeviceNet Network Install the Software Follow these steps to install RSLinx and RSNetWorx for DeviceNet software 1. Insert the software CD-ROM in the drive. The CD-ROM supports Windows Autorun. If you have Autorun configured, the installation will automatically start when you insert the CD-ROM in your drive. If you do not have Autorun configured, perform steps 2 and 3. 2. From the Windows Start menu, choose Run. 3. Browse for the Setup program on the CD-ROM and open it.
Manually Configure the DeviceNet Network Chapter 5 2. From the Communications menu, choose Configure Drivers. 3. From the Available Driver Types pull-down menu, choose Add/New. 4. .Select your driver. 5. Your driver setup will depend on your particular system setup (COM port, communication rate, node address). Choose the appropriate settings for your system. The software will take a few seconds to configure the driver.
Chapter 5 Manually Configure the DeviceNet Network 6. .Click OK. 7. Click OK to use the default driver name. 8. Minimize RSLinx software. You will use the driver you just configured to browse and configure the network with RSNetWorx for DeviceNet software. Use RSNetWorx for DeviceNet Software to Configure the 1769-SDN Scanlist This manual assumes a certain level of familiarity with RSNetWorx for DeviceNet software.
Manually Configure the DeviceNet Network Chapter 5 2. From the File menu, choose New. If you have ControlNet configured on your system you may see this dialog. Otherwise, proceed to step 4. 3. Select DeviceNet Configuration and click OK. 4. Click the Online button on the toolbar. A list of the available networks will appear. Your list may be different from that shown below, depending upon the drivers you have configured on your system. 5. Select your DeviceNet driver and click OK.
Chapter 5 Manually Configure 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, your network is displayed. RSNetWorx for DeviceNet software performs a single pass browse when you go online or choose the browse feature. The software will poll for devices one time and display the results.
Manually Configure the DeviceNet Network Chapter 5 Set the Node Address Once the network browse is complete, the node addresses appear to the right of their icons. Use this procedure to change the node address of devices on the network (such as a photoeye). You can also change the network communication rate (baud rate) of some devices. Depending upon the device, you may need to cycle power for communication rate changes to take effect.
Chapter 5 Manually Configure the DeviceNet Network 2. Click Browse. 3. Select the DeviceNet network. The devices on the network will appear in the right panel of the dialog.
Manually Configure the DeviceNet Network Chapter 5 4. Select the device you are commissioning in the right panel and click OK. You will see the Node Commissioning dialog with the current settings for your scanner module. The default scanner module settings are as follows. • Communication rate = 125 Kbps • Node address = 63 5. In the Node Address box, enter the new node address. 6. Click Apply and Exit the dialog.
Chapter 5 Manually Configure the DeviceNet Network Configure the I/O Devices The information in this section will focus on the scanner module’s configuration and parameters that you can change by using RSNetWorx for DeviceNet software. This dialog shows how a DeviceNet network is shown within RSNetWorx for DeviceNet software. As you can see, node one is a 1769-SDN scanner. Double-click on the scanner module to view or modify the scanner’s parameters.
Manually Configure the DeviceNet Network Chapter 5 General Tab This dialog shows the properties that RSNetWorx for DeviceNet software displays for the 1769-SDN scanner module. Available items are accessed through a series of tabs located across the top of the dialog. The General tab is the default tab and provides information relative to the module. If you ever need product support, you will need to provide the revision number when you contact Rockwell Automation Technical Support.
Chapter 5 Manually Configure the DeviceNet Network Module Tab Interscan Delay This parameter defines the delay time the scanner module uses between scans of the DeviceNet network. If you have slave devices configured for polled behavior in the 1769-SDN scanner module scanlist, Interscan Delay (ISD) defines the amount of time the scanner module waits between DeviceNet I/O updates. Increasing the ISD time causes a longer network scan, which adversely affects overall input-to-output performance.
Manually Configure the DeviceNet Network Chapter 5 Foreground to Background Poll Ratio Devices set for polled behavior can be polled on every I/O scan (foreground) or they can be polled less frequently (background). Setting a device for foreground or background behavior is done when you configure each device in the scanner’s input section. Foreground/Background Polling Behavior Each waveform shows polling frequency for the given Foreground to Background Poll Ratio.
Chapter 5 Manually Configure the DeviceNet Network This parameter enables the slave functionality of the scanner, and lets you set the I/O behavior, with the amount of data to be exchanged. The Slave mode settings are described in this table. Slave Mode Settings Connection Format Description Strobed Not supported by the 1769-SDN scanner module. Polled Values entered into Rx and Tx parameters define how much data will be exchanged over the polled connection that owns the scanner’s slave I/O.
Manually Configure the DeviceNet Network Chapter 5 Expected Packet Rate (EPR) When the scanner module opens a polled or strobed I/O connection, it sets a maximum timeout (expected packet rate) with the device. If the device does not receive a packet from the scanner module within four times the EPR value, the slave device drops the connection.
Chapter 5 Manually Configure the DeviceNet Network Scanlist Tab The Scanlist defines which devices on the DeviceNet network are owned by the scanner. Available Devices These are the devices on the network that have the ability to be slave I/O devices. Slave-capable devices do not have to be used as slave I/O by a scanner. They may alternately be used as slave I/O by another scanner module on the same network, or they may have dual functionality.
Manually Configure the DeviceNet Network Chapter 5 Scanlist These devices have been assigned to be slave I/O to this scanner. A slave device on the DeviceNet network can be owned by only one master at a time. Devices in the scanlist are configured using the input and output tabs. Automap on Add Automap allows a slave’s I/O to be automatically mapped into the scanner’s input or output image tables when the slave device is added to the scanlist.
Chapter 5 Manually Configure the DeviceNet Network Input Tab The input tab dialog lets you to define how data from all of the scanner’s slave devices are mapped into the input image of the controller. In this example, four input devices are mapped into the scanner’s input image. The dialog shows each device’s: • node number. • catalog number. • connection type used between the scanner module and the slave device (strobed, polled, cyclic, or change of state).
Manually Configure the DeviceNet Network Chapter 5 Advanced The scanner module allows each node’s slave data to be broken up (segmented) into separate input image areas. This capability lets you group data from multiple slave nodes into contiguous memory locations. This is simply an ease-of-use feature. For maximum performance, do not segment a slave device’s data. Output Tab The output tab dialog lets you define how data from the scanner module is mapped to the outputs of the slave devices.
Chapter 5 Manually Configure the DeviceNet Network In this example, four output devices are mapped into the scanner’s output image. The dialog box shows each device’s: • node number. • catalog number. • connection type used between the scanner module and the slave device (strobed, polled, cyclic, or change of state). • amount of data that will be exchanged (in bytes). • word within the controller’s output image.
Manually Configure the DeviceNet Network Chapter 5 ADR allows a slave device to be removed from the network and replaced with another identical slave device that is residing on the network at node address 63 and is not in the scan list. The replacement device will have its node address automatically changed to that of the device being replaced.
Chapter 5 Manually Configure the DeviceNet Network Configure ADR Parameters On the ADR tab, you can configure the ADR parameters for the 1769-SDN scanner module. Using the controls on this tab, you can select ADR parameters and enable or disable this functionality either globally or on a device-specific basis. Configure each device on the network. If online, make sure that the configuration is synchronized with the online devices. 1. On the ADR tab, select the device you want to configure to use ADR. 2.
Manually Configure the DeviceNet Network Chapter 5 3. Click the Configuration Recovery checkbox. Notice the ADR space (in bytes) is displayed for the module you are updating. 4. Click the Auto-Address Recovery checkbox if desired. The Enable Auto-Address Recovery checkbox needs to be checked in order for AAR to work. 5. Repeat steps 1...4 for each desired module.
Chapter 5 Manually Configure the DeviceNet Network Summary Tab The summary tab provides a condensed picture of the scanner’s configuration: which nodes are mapped, if they are active, and receive and transmit information. Download and Save Your Configuration Follow these steps to download and save your configuration. 1. Click the Scanlist tab and then Download to Scanner. 2. Click All Records. 3. Click Download to download the configuration to the scanner. 4.
Manually Configure the DeviceNet Network Chapter 5 5. From the File menu, choose Save As. 6. Save the configuration to a DeviceNet file. 7. Close RSNetWorx for DeviceNet software.
Chapter 5 Manually Configure the DeviceNet Network Notes: 86 Publication 1769-UM009E-EN-P - August 2009
Chapter 6 DeviceNet I/O Image Introduction 1769-SDN Input Structure This chapter describes the input and output data structure. This table describes what this chapter contains and where to find specific information.
Chapter 6 DeviceNet I/O Image MicroLogix 1500 Status Structure The first area of the MicroLogix 1500 controller input image is the Status Structure. The status words are described in more detail in the following sections.
DeviceNet I/O Image Chapter 6 Device Failure Array These 64 bits provide status information for use in your control program. For each slave device owned by the scanner, you should monitor the respective bit within these four words. If a slave device faults, the bit that corresponds to that node address will be set (1). If a slave device is not faulted or returns from a faulted state to an operating state, the corresponding bit for that node will be cleared (0).
Chapter 6 DeviceNet I/O Image Slave Device Configuration Comparison to Scanner Module Configuration Input Word Bit 0...15 Description (1) Node 0…15 Bit ON (1) = Slave node mismatch 7(2) Node 16…31 Bit OFF (0) = Slave node match 8(3) Node 32…47 9(4) Node 48…63 6 (1) Bit 0 corresponds to Node 0, Bit 1 corresponds to Node 1 … Bit 15 corresponds to Node 15. (2) Bit 0 corresponds to Node 16, Bit 1 corresponds to Node 17 … Bit 15 corresponds to Node 31.
DeviceNet I/O Image Chapter 6 Active Node Array The Active Node array contains 64 bits of data that represents each slave node’s status. A slave node is considered active when it is present and enabled in the master’s scanlist. A bit value of 0 means Not Active, a bit value of 1 means Active. Slave Node Status Input Word Bit 0...
Chapter 6 DeviceNet I/O Image Reserved Array Reserved Array Input Word Description(1) 22…31 Always 0 (1) Do not manipulate reserved bits. Doing so may interfere with future compatibility. Device Status Array The Device Status Array is a 64-byte array containing the information shown in this table. Each byte indicates the status code of the scanner’s master and the slave devices.
DeviceNet I/O Image Chapter 6 Module Status Register The scanner module supports a 32-bit Module Status Register.
Chapter 6 DeviceNet I/O Image CompactLogix Status Structure The second area of the CompactLogix controller input image is the Status Structure. The status words are described in more detail in the following sections. Description Data Type I.Status.Scan Counter 2 words I.Status.Device Failure Register 64-bit array I.Status.Autoverify Failure Register 64-bit array I.Status.Device Idle Register 64-bit array I.Status.Active Node Register 64-bit array I.Status.Status Display 8 bytes I.Status.
DeviceNet I/O Image Chapter 6 Device Failure Register These 64 bits provide status information for use in your control program. For each slave device owned by the scanner, you should monitor the respective bit within these four words. If a slave device faults, the bit that corresponds to that node address will be set (1). If a slave device is not faulted or returns from a faulted state to an operating state, the corresponding bit for that node will be cleared (0).
Chapter 6 DeviceNet I/O Image Slave Device Configuration Comparison to Scanner Module Configuration Input Word Bit 0...15 Description (1) Node 0…15 Bit ON (1) = Slave node mismatch 7(2) Node 16…31 Bit OFF (0) = Slave node match 8(3) Node 32…47 9(4) Node 48…63 6 (1) Bit 0 corresponds to Node 0, Bit 1 corresponds to Node 1 … Bit 15 corresponds to Node 15. (2) Bit 0 corresponds to Node 16, Bit 1 corresponds to Node 17 … Bit 15 corresponds to Node 31.
DeviceNet I/O Image Chapter 6 Active Node Register The Active Node array contains 64 bits of data that represents each slave node’s status. A slave node is considered active when it is present and enabled in the master’s scanlist. A bit value of 0 means Not Active, a bit value of 1 means Active. Slave Node Status Input Word Bit 0...
Chapter 6 DeviceNet I/O Image Scrolling Device Status The Scrolling Device Status is the status of the node with errors. The data updates once per second, scrolling through all nodes with errors. Device Status The Device Status is the status of each DeviceNet node, indexed by node number into a 64-byte array. CompactLogix Status Register The third area of the CompactLogix controller input image is the Status Register. The status words are described in more detail in the following sections.
DeviceNet I/O Image Chapter 6 Fault This bit displays whether the network is faulted. • 0 = Network is not faulted • 1 = Network is faulted Disable Network This bit displays whether the network is disabled. • 0 = Network is not disabled • 1 = Network is disabled Device Failure This bit displays whether any device failures have occurred on the network.
Chapter 6 DeviceNet I/O Image Dup Node Failure This bit displays whether a network failure exists because of a duplicate node address. • 0 = No failure exists • 1 = Failure exists due to duplicate node address Dnet Power Detect This bit displays whether a DeviceNet power failure exists on the network.
DeviceNet I/O Image Chapter 6 Fault This bit forces the scanner into a faulted condition. • 0 = Network is not faulted • 1 = Network is faulted Disable Network This bit disables the DeviceNet network. • 0 = Network is not disabled • 1 = Network is disabled Halt Scanner This bit halts the scanner. • 0 = Scanner is not halted • 1 = Scanner is halted Reset This bit resets the scanner. • 0 = The scanner has not been reset • 1 = The scanner has been reset. Do not leave this bit = 1.
Chapter 6 DeviceNet I/O Image Input Data Image The Input Data Image is described on page 15 for the MicroLogix 1500 controller and on page 16 for the CompactLogix controller. 1769-SDN Output Structure The Output Structure is described on page 15 for the MicroLogix 1500 controller and on page 16 for the CompactLogix controller.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers Introduction MicroLogix 1500 Controllers This chapter contains an example in which the 1769-SDN scanner module is used with a MicroLogix 1500 controller. This table describes what this chapter contains and where to find specific information.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers RSLogix 500 Programming Software I/O Configuration One of the advanced features of RSLogix 500 software is the ability to have the programming software establish a communication connection with the controller and read which I/O modules are attached to the controller. This capability significantly reduces the effort involved in configuring a system.
Use the 1769-SDN Scanner Module with MicroLogix Controllers Chapter 7 Start the Project Follow these steps to begin your project. 1. Open RSLogix 500 software. 2. Choose File ⇒New ⇒MicroLogix 1500 LRP series C. This dialog should match what you see on your computer. In this example the name for this application is TEMP. In the TEMP dialog, you see everything associated with the application. Within the Controller folder you will see I/O Configuration. 3. Double-click I/O Configuration.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers I/O Configuration Screen The I/O configuration dialog shows each of the controller I/O slots. For the MicroLogix 1500 controller, slot 0 contains the embedded I/O that is part of the MicroLogix 1500 base unit. Slots 1...16 are for Compact I/O expansion modules (referred to as local I/O, because they are physically attached to the controller). Slots 9...16 are available using only a series C processor with a series B base unit.
Use the 1769-SDN Scanner Module with MicroLogix Controllers Chapter 7 Read I/O Configuration Next you see a communication dialog that lets you select a communication path by using RSLinx software to connect to the MicroLogix controller. If you have previously connected to a controller, the communication driver that you used before will be the active driver. This dialog provides the ability to change the driver or perform a Who Active across a network to locate the specific MicroLogix controller.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers 1769-SDN Scanner Module Configuration Double-click the module to configure a specific module. Double-click the module in slot 1 to configure the scanner module in this example. Input Words This is the number of input words the controller assigns to the module. The first 66 words (0...65) are required by the scanner module for status. DeviceNet slave input data words start at slot word 66.
Use the 1769-SDN Scanner Module with MicroLogix Controllers Chapter 7 Changing the 1769-SDN Configuration You can change (add or remove) the amount of data the controller has assigned to the scanner module in the expansion module configuration dialog. From within RSLogix 500 software, I/O configuration, open the 1769-SDN scanner module and change the input or output words as needed. Save the program and download to the controller.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers The configuration dialog for the scanner module is shown below. Ignore Configuration Error Checking (enabling) the Ignore Configuration error checkbox instructs the module to ignore I/O size mismatches. If this is checked and the input/output scanlist configured by RSNetWorx for DeviceNet software (DeviceNet side of the 1769-SDN scanner module) does not match the amount of I/O data assigned by the controller (0...
Use the 1769-SDN Scanner Module with MicroLogix Controllers Backplane Messaging Chapter 7 The MicroLogix 1500 1764-LRP processor and the 1769-SDN scanner module also support backplane messaging. This new level of functionality allows the processor to read (get) or write (set) data to other devices on the DeviceNet network. This is also referred to as Explicit Messaging. You can use two different types of messages to exchange information with the DeviceNet device.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers Program Upload and Download Before performing a program upload or download through the scanner, be sure that the module is properly installed in the system, and that a terminator is present at the end of the Compact I/O expansion bus. IMPORTANT DeviceNet networks can operate at 125 Kbps, 250 Kbps, or 500 Kbps.
Use the 1769-SDN Scanner Module with MicroLogix Controllers Configure a Local DeviceNet Message Chapter 7 This section describes how to configure a local message by using the scanner module and a MicroLogix 1500 1764-LRP processor. Message Setup Dialog Rung 0 shows a standard RSLogix 500 message (MSG) instruction preceded by conditional logic. Access the Message Setup dialog by double-clicking the Setup Screen. The RSLogix 500 Message Setup dialog appears.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers Channel Parameter The 1764-LRP controller supports three different pathways for messaging. Channels 0 and 1 are RS-232 ports and are functionally identical to MicroLogix 1200 and MicroLogix 1500 1764-LSP controllers. The 1764-LRP controller also supports backplane communication through the Expansion Communication Port (ECP) as illustrated below. When ECP is chosen, you are able to select which slot position (1...
Use the 1769-SDN Scanner Module with MicroLogix Controllers Chapter 7 Communication Command The 1764-LRP controller supports the six standard types of communication commands (same as all other MicroLogix 1200 and 1500 controllers) and CIP Generic.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers CIP Generic Control & Information Protocol (CIP) is a newer and more versatile protocol than PCCC. It is an open protocol that is supported by newer Allen-Bradley controllers and third-party products. CIP messaging is the native messaging format for the DeviceNet network. All DeviceNet devices are compliant with CIP messaging.
Use the 1769-SDN Scanner Module with MicroLogix Controllers Chapter 7 Data Table Address (receive and send) This value identifies the data file location within the 1764-LRP controller that will receive data from the DeviceNet device, and/or the starting data file location that will be sent to the destination DeviceNet device. Size in Bytes (receive and send) Since all data transmitted on the DeviceNet network is byte based, you must enter the number of bytes that will be received and sent.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers Target Device 118 Field Definition Message Timeout Message timeout is specified in seconds. If the target does not respond within this time period, the message instruction will generate a specific error. The amount of time that is acceptable should be based on application requirements and network capacity/loading. Target Type You can select either Module or Network Device.
Use the 1769-SDN Scanner Module with MicroLogix Controllers Chapter 7 Field Definition Service The DeviceNet network uses services to provide specific messaging functions. A number of standard services with their corresponding parameters have been preconfigured for ease of use. If you need to use a service that is not available, select one of the generic services. The generic service lets you enter specific service code parameters.
Chapter 7 Use the 1769-SDN Scanner Module with MicroLogix Controllers MSG Instruction Error Codes When the processor detects an error during the transfer of Expansion I/O Communication Module message data, the processor sets the ER bit and writes an error code at MG file sub-element #18 that you can monitor from your programming software.
Chapter 8 Troubleshooting Introduction Status Indicators The 1769-SDN scanner module’s front panel status indicators aid in troubleshooting the module. The diagnostics provided by these indicators are described in this chapter. Topic Page Status Indicators 121 Error Codes 124 The first step in troubleshooting is to observe the 1769-SDN scanner module’s status indicators and seven-segment numeric displays.
Chapter 8 Troubleshooting This table summarizes the meanings of the status indicators and numeric codes. Module Indicator Network Indicator Node Address and Status Display Troubleshooting the Status Indicators and Numeric Display Indicator Color/Status Description Module Off No power applied to module. Apply power. Flashing Green No bus master (MicroLogix or CompactLogix controller) present. Verify module connectors are properly seated. If they are, cycle power to the controller.
Troubleshooting Chapter 8 Troubleshooting the Status Indicators and Numeric Display Indicator Color/Status Description Network Off No module power, no network power, or communications are not occurring between the module and the DeviceNet network. (This may be an acceptable condition.) Verify module has power. Check that the DeviceNet cable is securely connected and the DeviceNet network is powered. Verify that network power is adequate (11...5V DC). Flashing Green Device is operational.
Chapter 8 Troubleshooting Error Codes The following table describes the error codes indicated by the seven-segment numeric display. Device Status Code Name Description 67 Backup Mode Scanner in Backup Scanner mode. 68 No Backup Scanner No backup scanner module present. (decimal) Install and configure a backup scanner, if needed. 69 Backup Scanner Invalid CRC The configuration of the primary and the secondary controller does not match. Either one or both of the configurations is incorrect.
Troubleshooting Chapter 8 Device Status Code Name Description In Idle Mode Module is in Idle mode. (decimal) 80 Put the controller into RUN mode and enable the RUN bit in the Module Command Array. See page 16. 81 Scanner Faulted The scanner module has stopped producing and consuming I/O data. This condition does not affect the scanner’s system or messaging modes. Check the FAULT value in the Module Command Array. See page 16.
Chapter 8 Troubleshooting Device Status Code Name Description FLASH Update Flash Update In Progress (decimal) 95 IMPORTANT: Do not disconnect the module from the network while a FLASH update is in progress. 98 Firmware Corrupted Firmware is corrupted. Reflash module firmware. Do not power cycle the module. Doing so may cause the module to become inoperable. If the problem persists contact Rockwell Automation Technical Support. 99 126 Hard Fault Cycle power. Reflash module firmware.
Appendix A 1769-SDN DeviceNet Class Codes Introduction This appendix contains the most commonly used class codes for the 1769-SDN DeviceNet scanner module. They are shown in the following tables.
Appendix A 1769-SDN DeviceNet Class Codes Notes: 128 Publication 1769-UM009E-EN-P - August 2009
Appendix B CompactLogix Backup on the DeviceNet Network Introduction This appendix offers a solution to back up your CompactLogix controller on the DeviceNet network. CompactLogix system backup on the DeviceNet network is a simple, low-cost, back-up system most effective when used in smaller applications that require fast switchovers from a primary to a secondary controller.
Appendix B CompactLogix Backup on the DeviceNet Network How the Backup Works The following figure shows an example backup system. In the backup system, the following occurs: • Both controllers/scanners simultaneously receive all inputs. • Both controllers execute in parallel but are not synchronized. • Only the primary controllers send output data to the I/O devices. A virtual switch in the 1769-SDN scanner module is used to switch outputs between primary and secondary controllers.
CompactLogix Backup on the DeviceNet Network Appendix B Backup System Requirements The CompactLogix backup on DeviceNet solution requires that you use the following: • RSLogix 5000 programming software, version 10 or later • Two CompactLogix controllers, firmware revision 10.x or later • Two 1769-SDN scanner modules, firmware revision 3.
Appendix B CompactLogix Backup on the DeviceNet Network Configure the Backup System Follow these steps to configure a CompactLogix backup system on the DeviceNet network. Some of these steps are described in greater detail in the rest of the appendix. 1. Install all I/O and operator interfaces that you need to back up on the DeviceNet network. We recommend that you reserve node addresses 0 and 1 for the two 1769-SDN scanner modules used with the CompactLogix controllers within a backup system.
CompactLogix Backup on the DeviceNet Network Appendix B 9. Connect the other CompactLogix controller with a 1769-SDN scanner module on the network. 10. Set the node address to 0. 11. Apply power to the controller and scanner module. 12. Use RSNetWorx for DeviceNet software to download the same scanlist used in step 5. It may be necessary to browse the network again before downloading the scanlist.
Appendix B CompactLogix Backup on the DeviceNet Network Develop the CompactLogix Backup Application The CompactLogix backup is enabled from an RSLogix 5000 programming software user program with a few simple ladder rungs.
CompactLogix Backup on the DeviceNet Network Appendix B Setting the Heartbeat Constant You can set the heartbeat constant with five rungs of ladder logic. This figure shows rungs 0 and 1 and the message setup used in rung 1. The message in rung 1 uses the INT data type. Rung 1 Message Configuration and Communication tabs.
Appendix B CompactLogix Backup on the DeviceNet Network This figure shows rung 2 and the message setup used on it. The message in rung 2 uses the INT data type. Rung 2 Message Configuration and Communication tabs.
CompactLogix Backup on the DeviceNet Network Appendix B This figure shows rungs 3 and 4 and the message setup used on it. The message in rung 3 uses the INT data type. Rung 3 Message Configuration and Communication tabs. This completes the required portion of ladder logic to enable the CompactLogix backup on the DeviceNet network. The following sections describe how to use additional ladder logic to read backup state and status. However, these sections are not required to complete the backup solution.
Appendix B CompactLogix Backup on the DeviceNet Network Reading Backup State Rung You can read the backup state of the DeviceNet scanner module with a single rung of ladder logic. The backup state is useful for debugging or more sophisticated backup schemes. The message in this rung uses the SINT data type. This figure shows the rung you can use to read the backup state. Rung 5 Message Configuration and Communication tabs.
CompactLogix Backup on the DeviceNet Network Appendix B This table describes the possible values this message may return when reading the backup state of the DeviceNet scanner.
Appendix B CompactLogix Backup on the DeviceNet Network Reading Backup Status You can read the backup status of the DeviceNet scanner module with a single rung of ladder logic. The backup state is useful for debugging or more sophisticated backup schemes. The message in this rung uses the SINT data type. This figure shows the rung you can use to read the backup state. Rung 6 Message Configuration and Communication tabs.
CompactLogix Backup on the DeviceNet Network Using Indicators to Check Status Appendix B The 1769-SDN scanner module’s status indicators provide useful information (for example, determining which scanner module is primary) about backup scanner module status. Module Status Indicator Network Status Indicator Node Address and Status Display Module Status Indicator This table lists the indicators to monitor when checking backup status.
Appendix B CompactLogix Backup on the DeviceNet Network Node Address and Status Display The seven-segment numeric display shows the following information about the primary and secondary scanner modules in either Run or Idle modes. TIP If error codes other than those shown in these tables appear in the display, refer to Chapter 8, Troubleshooting, for more information on error codes.
CompactLogix Backup on the DeviceNet Network Appendix B Lost Primary Scanner Module With Valid Backup Scanner Module Run Mode Primary Secondary Node Number 00 01 or 00 Status Undefined error 68 (No backup scanner present) or 00 (Run mode) Primary or Secondary -- P - (Primary) Primary Secondary Node Number 00 00 or 01 Status Undefined error 68 (No backup scanner present) or 80 (Idle mode) Primary or Secondary -- P - (Primary) Primary Secondary Node Number 00 or 01 00 or 01 Status
Appendix B CompactLogix Backup on the DeviceNet Network Development and Debugging Tips When you implement the CompactLogix system backup on the DeviceNet network, we recommend that you consider the following development and debugging tips: • Develop and debug the entire application with only the primary controller and scanner module present. When the application is totally verified, then download the program and exact same scanlist to the secondary controller, without the primary controller present.
CompactLogix Backup on the DeviceNet Network Appendix B • Unlike some backup systems (such as PLC-5 controller systems), the primary controller still maintains control of the I/O, and switchover does not occur if the primary controller is set to Program/Idle mode. The secondary 1769-SDN scanner module also indicates that it is in Idle mode. • By default, a switchover will not occur if the default fault routine or user fault routine is executed in the primary controller.
Appendix B CompactLogix Backup on the DeviceNet Network Notes: 146 Publication 1769-UM009E-EN-P - August 2009
Glossary Auto-Address Recovery (AAR) Auto-Address Recovery (AAR) allows a slave device to be removed from the network and replaced with another identical slave device that is residing on the network at node address 63 and not in the scan list. The replacement device will have its node address automatically changed to that of the device being replaced.
Glossary 148 Dual Mode The scanner module is in Dual mode when it serves as a master to one or more slaves and as a slave to another master simultaneously. Electronic Data Sheet (EDS) A vendor-supplied template that specifies how information is displayed as well as what is an appropriate entry (value). Explicit Messaging A type of messaging used for lower priority tasks, such as configuration and data monitoring.
Glossary 149 Network The DeviceNet network or the RSNetWorx for DeviceNet software representation of the network. Node Hardware that is assigned a single address on the network. Also referred to as a device. Offline When the host platform is not communicating on the network. 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 scanner module’s memory.
Glossary 150 Rx Abbreviation for receive Scanlist The list of devices (nodes) with which the scanner module is configured to exchange I/O data. Scanner The function of the 1769-SDN scanner module to support the exchange of I/O with slave modules. Slave Mode The 1769-SDN scanner module is in slave mode when it is placed in another DeviceNet master’s scanlist as a slave device. Strobed A type of I/O data communication. A strobed message solicits a response from each strobed device (a multicast transfer).
Index Numerics 1770-KFD RS-232 DeviceNet adapter 19, 61 193-DNCT terminal 40 initiating AutoScan 51-52 A accessing device data 57-59 additional resources 10 Auto Device Replacement in RSNetWorx for DeviceNet software 80-83 AutoScan additional considerations 53-56 firmware requirements 38 implementing 46-60 initiate via a 193-DNCT terminal 51-52 initiate via a user program 49-50 overview 38 when to use 38 B backplane messaging 111 backup CompactLogix backup on the DeviceNet network 129-145 baud rate settin
Index I I/O allocation configuring via a user program 48 in CompactLogix controller 37 in MicroLogix 1500 controller 37 maximum node number 54 implementing AutoScan 46-60 input data definition 14 installation 23-33 getting started 19 grounding 32 heat and noise considerations 25 required equipment 19 M manually configuring the DeviceNet network 61-85 message instruction error codes 120 messaging backplane 111 configuring a local DeviceNet message 113-118 MicroLogix 1500 controllers 103-120 minimum spacing
How Are We Doing? Your comments on our technical publications will help us serve you better in the future. Thank you for taking the time to provide us feedback. You can complete this form and mail (or fax) it back to us or email us at RADocumentComments@ra.rockwell.com. Pub. Title/Type 1769-SDN DeviceNet Scanner Module Cat. No. 1769-SDN Pub. No. 1769-UM009E-EN-P Pub. Date August 2009 Part No. Please complete the sections below.
PLEASE FASTEN HERE (DO NOT STAPLE) PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO.
Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://support.rockwellautomation.com, you can 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.
