Allen-Bradley DeviceNet 1784-PCIDS Configuration Manual
Allen-Bradley DeviceNet 1784-PCIDS Configuration Manual

Allen-Bradley DeviceNet 1784-PCIDS Configuration Manual

Hide thumbs Also See for DeviceNet 1784-PCIDS:
Table of Contents

Advertisement

Allen-Bradley
DeviceNet
Scanner
(Cat. Nos. 1784-PCIDS,
–CPCIDS)
Configuration
Manual
AB PLCs

Advertisement

Table of Contents
loading

Summary of Contents for Allen-Bradley DeviceNet 1784-PCIDS

  • Page 1 Allen-Bradley Configuration DeviceNet Scanner Manual (Cat. Nos. 1784-PCIDS, –CPCIDS) AB PLCs...
  • Page 2 Reproduction of the contents of this copyrighted publication, in whole or in part, without written permission of Allen-Bradley Company, Inc., is prohibited. Throughout this manual we make notes to alert you to possible injury to people or damage to equipment under specific circumstances.
  • Page 3 Preface About This Manual What’s in This Manual? Use this manual with both the 1784–PCIDS and the–CPCIDS scanners. Important: This manual describes both the 1784–PCIDS and –CPCIDS scanners since they are functionally equivalent. Throughout this manual, we use the generic term “1784–family scanner”...
  • Page 4 P–2 Conventions The following conventions appear throughout this manual to guide you through the information and concepts. Important: Your screens may appear slightly different than the ones depicted in this manual if you are running DeviceNet Manager software on a platform other than Windows NT, version 4.0.
  • Page 5 P–3 Terminology This term Means Change of State The scanner module can send and receive data with slave devices that have the change of state feature. Data is sent whenever a data change occurs or at a user-configurable heartbeat rate. Cyclic The scanner module can send and receive data with slave devices that have the cyclic feature.
  • Page 6 P–4 Support Services At Rockwell Automation, customer service means experienced representatives at Customer Support Centers in key cities throughout the world for sales, service, and support. Our value-added services include: Technical Support SupportPlus programs telephone support and 24-hour emergency hotline software and documentation updates technical subscription services Engineering and Field Services...
  • Page 7: Table Of Contents

    Table of Contents Planning Your Configuration Chapter 1 Planning Your Configuration ......1–1 What’s in This Chapter? .
  • Page 8 toc–ii Table of Contents Removing Devices from the Scan List ....3–9 Viewing Device Information in the Scan List ....3–9 Adding Devices to the Scan List from the Scan List Editor Screen 3–11...
  • Page 9: What's In This Chapter

    Chapter Planning Your Configuration What’s in This Chapter? This chapter introduces questions you should ask before configuring your 1784–family scanner. In addition, it presents an example DeviceNet network and I/O data mapping scheme. For information about See page What you need to know 1–1 Beginning the process 1–1...
  • Page 10: Planning Examples

    1–2 Planning Your Configuration Planning Examples The following examples illustrate a data-mapping plan for a DeviceNet network. About This Example This example has the following characteristics: a PCI bus based host platform a 1784–family scanner a Series 9000 photoelectric sensor (strobed) a RediSTATION operator interface (polled) Important: In the following examples, output is data sent to a...
  • Page 11: Part I - Photoelectric Sensor Mapping Input Data

    Planning Your Configuration 1–3 Part I – Photoelectric Sensor Mapping Input Data The photoelectric sensor inputs are mapped to the scanner’s input data table and then to the host platform’s input data file. Series 9000 Photoelectric Sensor Inputs = unused bits D = data bit S = status bit usage example:...
  • Page 12: Part Ii - Redistation Operator Interface Mapping Input Data

    1–4 Planning Your Configuration Part II – RediSTATION Operator Interface Mapping Input Data The RediSTATION operator interface’s input byte is mapped to the scanner’s data table. In the RediSTATION’s byte is a bit for the: red button (on/off) green button (on/off) RediSTATION Inputs = unused bits R = bit for red button...
  • Page 13: Part Iii - Redistation Operator Interface Mapping Output Data

    Planning Your Configuration 1–5 Part III – RediSTATION Operator Interface Mapping Output Data The RediSTATION operator interface’s output is mapped to the scanner’s discrete output data table. Within each of these output bytes is a bit for the indicator light. The output image table is then transferred from the host application.
  • Page 14: What's Next

    1–6 Planning Your Configuration What’s Next? The next step is to understand how to configure the scanner and perform I/O data mapping through DeviceNet Manager software. The next chapter details: Module Configuration Scan List Editor Edit Display Properties Edit Device I/O Parameters Auto Map Data Table Map Scan List Editor upload and download...
  • Page 15: Before You Begin

    Chapter Before You Begin What’s in This Chapter? Read this chapter to understand communication between a host platform and DeviceNet devices through a 1784-family scanner, the data tables, and the DeviceNet Manager screens used to configure data tables. For information on See page What you need to know 2–1...
  • Page 16: What Your Scanner Does

    2–2 Before You Begin What Your Scanner Does In a typical configuration, the scanner acts as an interface between DeviceNet devices and a host platform. The scanner communicates with DeviceNet devices over the network to: read inputs from a device write outputs to a device download configuration data monitor a device’s operational status...
  • Page 17: Communicating With Your Devices

    Before You Begin 2–3 Communicating with Your Devices Your scanner communicates with scanned device via strobe, poll, A strobe message is a change of state, and cyclic messages. It uses these messages to multicast transfer of data (which is 64 bits in length) solicit data from or deliver data to each device.
  • Page 18: Communicating With Your Host Platform

    2–4 Before You Begin Communicating with Your Host Platform Your host platform communicates with the scanner via input and output image tables. Input data, gathered from the network’s devices, is organized within the scanner and made available for the processor to “read” from the input image table. The scanner does not send data to your host platform.
  • Page 19: What Scanner Data Tables Are And What They Do

    Before You Begin 2–5 What Scanner Data Tables To manage the flow of data between your processor and a network’s Are and What They Do devices, the scanner uses the following data tables. Scanner Configuration Table Scan List Table Device Input Data Table Device Output Data Table Device IdleTable Device Failure Table...
  • Page 20: Devicenet Manager Software As A Configuration Tool

    2–6 Before You Begin DeviceNet Manager DeviceNet Manager software configures the scanner’s data tables. Software as a This software tool connects to the scanner via the DeviceNet Configuration Tool network and an RS-232 interface module (1770-KFD) or PC Card (1784-PCD, 1784-PCID, 1784–CPCID). User Data in this table DeviceNet Manager...
  • Page 21: 1784-Family Scanner Configuration Screen-Map

    Before You Begin 2–7 1784-Family Scanner Configuration Screen-Map The main dialog screen can be accessed through either the Network Who or Project View. To access the Module Configuration screen from a Network Who, double To access the Module Configuration click on the scanner icon. screen from a Project View, double click on the scanner icon.
  • Page 22: What's Next

    2–8 Before You Begin What’s Next? Chapter 2 covers the configuration-process planning stage through a data-mapping example. Chapter 3 details the configuration screens and how to use them. Appendix A lists the possible error messages you may see when mapping your I/O. We recommend that you: use chapter 2 to become familiar with data mapping.
  • Page 23: Configuring Through Devicenet Manager Software

    Chapter Configuring Through DeviceNet Manager Software What’s in This Chapter This chapter presents a summary and entry procedure for each DeviceNet Manager software scanner-configuration screen. For information on See page What you need to know 3–1 Beginning the configuration process 3–1 Configuring your 1784-family scanner 3–3...
  • Page 24: Online And Offline Configuration

    3–2 Configuring Through DeviceNet Manager Software Online and Offline Configuration You can configure your scanner module in an online or offline mode. The following illustrates a typical process for each mode. Online configuration 1. Load settings into the configuration utility (editor) from a previously stored file.
  • Page 25: Configuring Your 1784-Family Scanner

    Configuring Through DeviceNet Manager Software 3–3 Configuring Your Use the Module Configuration screen to configure parameters 1784-Family Scanner associated with the scanner itself and to gain access to other configuration screens. For information about See page Accessing the Module Configuration 3–3 screen Assigning names from the project...
  • Page 26: Setting The Module's Operational Parameters

    3–4 Configuring Through DeviceNet Manager Software You see this screen. The scan list editor title bar indicates (in parenthesis) where the data comes from (file, project, PCIDS, CPCIDS, or Who). The Module Configuration screen allows you to set the scanner’s module operational parameters.
  • Page 27 Configuring Through DeviceNet Manager Software 3–5 You see a screen similar to this one. You will only see the Network button if your pc is connected to a network. Select the file you wish to load and choose OK. C. To load module defaults from your scanner, in the Load From field, choose Module Defaults.
  • Page 28: Assigning Names From The Project

    3–6 Configuring Through DeviceNet Manager Software Assigning Names From the Project To assign the project names you specified in the Project View screen to the configuration file, choose Assign Names from Project. Names include project, module, and network. The Module Configuration screen automatically updates with the names from the project.
  • Page 29: Accessing The Scan List Editor Screen

    Configuring Through DeviceNet Manager Software 3–7 Accessing the Scan List Editor Screen Entering the Scan List Editor Screen Through a Project project view module configuration scan list editor *.sl8 file project device list Entering the Scan List Editor Screen Through Network Who Network Who module configuration scan list editor...
  • Page 30: Scan List Editor Functions

    3–8 Configuring Through DeviceNet Manager Software Using the Scan List The Scan List Editor screen displays a summary of the network Editor Screen selected in the Module Configuration screen. For information about See page Scan list editor functions 3–8 Removing devices from the scan list 3–9 Viewing device information in the 3–9...
  • Page 31: Removing Devices From The Scan List

    Configuring Through DeviceNet Manager Software 3–9 Removing Devices from the Scan List To remove devices from the scan list in the Scan List Editor screen, highlight the device(s) you want to eliminate and choose Remove. Viewing Device Information in the Scan List 1.
  • Page 32 3–10 Configuring Through DeviceNet Manager Software You see a screen similar to this one. Select the file you wish to load and choose OK. 2. Click on the device you wish to view so it is highlighted. 3. Click on the Active in Scanlist check box to include the device in the scan cycle.
  • Page 33: Adding Devices To The Scan List From The Scan List Editor Screen

    Configuring Through DeviceNet Manager Software 3–11 Important: Certain display-property combinations can result in a blank Scan List Editor screen. 7. Choose OK. You return to the Scan List Editor screen. 8. Save your data: In this Field Choose Save data to your scanner’s non-volatile memory Save to PCIDS or CPCIDS...
  • Page 34 3–12 Configuring Through DeviceNet Manager Software If you see this screen, the devices are currently in the scan list but are not in the network. Select and drag the device(s) you want to add to the scan list over the scanner icon and release them. 2.
  • Page 35: Configuring A Device In The Scan List

    Configuring Through DeviceNet Manager Software 3–13 Notice the red box and the node number next to the device indicating to which scan list it belongs. 3. Once you’ve made your changes, choose OK. Configuring a Device in the Scan List 1.
  • Page 36: Using The Slave Mode Function

    3–14 Configuring Through DeviceNet Manager Software 2. Click on the Enabled check box in the appropriate field, depending upon whether your device is strobed, polled, change-of-state, or cyclic. Important: Once you click on the check box next to Enabled in the change of state/cyclic field, you must click on the appropriate radio button next to change-of-state or cyclic, depending upon your device and/or application.
  • Page 37: Determining Data-Mapping Preferences With Auto Map

    Configuring Through DeviceNet Manager Software 3–15 4. Click on the box Enabled check box in the appropriate field, depending upon whether your scanner will be strobed, polled, change-of-state, or cyclic. Important: Once you click on the Enabled check box in the change-of-state/cyclic field, you must click on the appropriate radio button next to change-of-state or cyclic, depending upon your...
  • Page 38: About The Data Table Map

    3–16 Configuring Through DeviceNet Manager Software Data type Designates Input image Locations within your image table to which the selected device’s data is mapped Output Image Where data destined for the selected device resides in your image table’s memory 4. From the appropriate drop list, depending upon what you selected in the above step, select the appropriate region to which you want to begin mapping the selected device’s input and/or output data.
  • Page 39: Using The Data Table Map For Custom Editing

    Configuring Through DeviceNet Manager Software 3–17 Input Data Map Output Data Map Apply Segment inserts the values from the Data Entry fields into your scan list’s data table map. Delete Segment removes the selected map segment from the data table map. Print to File prints the data table map to a text file using the .mr8 file extension.
  • Page 40 3–18 Configuring Through DeviceNet Manager Software 5. Click on the desired input data’s location in the Map Data To drop list. This indicates to the scanner which type of message will arrive – strobe, poll, change-of-state, or cyclic. This entry must match the type of communication you chose when defining the device’s communication characteristics in the Edit I/O Parameters screen.
  • Page 41: Mapping Specific Bits To Specific Device Memory Locations

    Configuring Through DeviceNet Manager Software 3–19 Mapping Specific Bits to Specific Device Memory Locations 1. To edit the data table map, click on the radio button next to Data Entry. You see a screen similar to this one. Once you’ve completed the following procedure, the map segment’s data is displayed in the appropriate position within this window.
  • Page 42 3–20 Configuring Through DeviceNet Manager Software 8. Enter the output data’s mapping location by indicating the word and bit at which the data begins in your scanner’s memory in the Word and Bit edit boxes. 9. Enter the size of the output data you are mapping from the location in the Map Data To field in the No.
  • Page 43: About Your Files

    Configuring Through DeviceNet Manager Software 3–21 About Your Files When you save Module Configuration or Scan List Editor information to a file, each is given a specific extension. MCC data is stored in .sm8 files Scan list data is stored in .sl8 files Scan list reports are stored in .lr8 files Scan list map reports are stored in .mr8 files Custom launch data is stored in .clc files...
  • Page 44 3–22 Configuring Through DeviceNet Manager Software Publication 1784-6.5.28 – July 1998...
  • Page 45: Troubleshooting

    Appendix Troubleshooting What’s in This Appendix? This appendix lists possible DeviceNetManager software error messages specific to scan list configuration. The first column, Message, is further divided into these categories: Input Maps 1-4 Error messages resulting from input-data entries for one of your input map segments, 1, 2, 3, or 4 Input Message Type Error messages resulting from a I/O type mismatch.
  • Page 46 A–2 Troubleshooting Message Description Recommendation Input Maps 1-4 Number of strobe bits exceeds strobe Rx size The no. bit value exceeds the The no. bits (number of bits) indicated in the strobe Rx size value. input data-map must be equal to or less than the strobe Rx size.
  • Page 47 Troubleshooting A–3 Message Description Recommendation Output Message Type Scan type prohibits poll bit assignment The type of I/O communication Determine what mode of communication you Scan type prohibits strobe bit assignment indicated does not match the wish to use: strobe, poll change of state, and/or Scan type prohibits strobe, poll, change of state, output data Map’s Map Data To.
  • Page 48 A–4 Troubleshooting Publication 1784-6.5.28 –July 1998...
  • Page 49: Scan List Example

    Appendix Scan List Example What’s in This Appendix? The following pages combine the data mapping examples from chapter 2 with DeviceNetManager software. For information on See page Understanding a scan list example B–2 Photoelectric sensor input mapping B–3 scheme example Node address 1 input data B–4 Node address 2 input data...
  • Page 50: Understanding A Scan List Example

    B–2 Scan List Example Understanding a This example illustrates how each Scan List Configuration screen Scan List Example appears when the mapping example’s network is configured. Series 9000 photoelectric sensor RediSTATION operator interface Two input bits from each photoelectric Two input bits from each RediSTATION sensor will be mapped.
  • Page 51: Photoelectric Sensor Input Mapping Scheme Example

    Scan List Example B–3 Photoelectric Sensor Input Mapping Scheme Example photoelectric sensor node address 1 photoelectric sensor node address 2 The status and data bits from each photoelectric 1 byte 1 byte sensor are mapped into the scanner’s input Photoelectric Sensor Input Bytes image table.
  • Page 52: Node Address 1 Input Data

    B–4 Scan List Example Node Address 1 Input Data Series 9000 photoelectric sensor photoelectric sensor input byte 1 byte The photoelectric sensor at node address 1 is a strobed device that produces 1 byte of input data. Remember that this node must be enabled in the scan list before it may participate in I/O communication with the scanner.
  • Page 53: Node Address 3 Input Data

    Scan List Example B–5 Node Address 3 Input Data Series 9000 photoelectric sensor photoelectric sensor input byte 1 byte The photoelectric sensor at node address 3 is a strobed device that produces 1 byte of input data. Remember that this node must be enabled in the scan list before it may participate in I/O communication with the scanner.
  • Page 54: Redistation Operator Interface Input Mapping Scheme Example

    B–6 Scan List Example RediSTATION Operator Interface Input Mapping Scheme Example RediSTATION Operator Interface Input Bytes What’s Happening? The bits for each start/stop station node address 5 start/stop station node address 6 RediSTATION operator interface’s red and green 1 byte 1 byte buttons are mapped into the scanner’s input image table.
  • Page 55: Redistation Operator Interface Output Mapping Scheme Example

    Scan List Example B–7 RediSTATION Operator Interface Output Mapping Scheme Example RediSTATION Operator Interface Output Bytes The station indicator-light bit for each RediSTATION operator interface is RediSTATION node address 5 RediSTATION node address 6 mapped to the scanner’s output image table. 1 byte 1 byte The output image table...
  • Page 56: Node Address 5 Input And Output Data

    B–8 Scan List Example Node Address 5 Input and Output Data RediSTATION operator interface RediSTATION input byte 1 byte The RediSTATION operator interface at node address 5 is a polled device that produces 1 byte of input data. Remember that this node must be enabled in the scan list before it may participate in I/O communication with the scanner.
  • Page 57: Flex I/O Module Input Mapping Scheme Example

    Scan List Example B–9 FLEX I/O Module Input Mapping Scheme Example FLEX I/O Module Input Bytes The FLEX I/O module produces 6 bytes What’s Happening? of input data and consumes 4 bytes of output data. The bits from each FLEX I/O module are 1794-ADN 1794-IB16 1794-OB16...
  • Page 58: Flex I/O Module Output Mapping Scheme Example

    B–10 Scan List Example FLEX I/O Module Output Mapping Scheme Example FLEX I/O Module Output Bytes The host application transfers data to the output image table. 1794-ADN 1794-IB16 1794-OB16 adapter module input module output module The FLEX I/O output message 1 byte 1 byte 1 byte...
  • Page 59: Node Address 22 Input And Output Data

    Scan List Example B–11 Node Address 22 Input and Output Data FLEX I/O input bytes FLEX I/O module 1 byte 1 byte 1 byte 1 byte 1 byte 1 byte The FLEX I/O module at node address 22 is a change of state device that produces 6 bytes of input data.
  • Page 60 B–12 Scan List Example Publication 1784-6.5.28 – July 1998...
  • Page 61 Index Symbols devices in the scan list, 3–13 example, 2–2 .clc, 3–2, 3–21 offline, 3–2 .lr8, 3–2, 3–21 online, 3–2 online/offline, 3–2 .mr4, 3–17 scanner, 3–3 .mr8, 3–2, 3–21 custom editing, datatable map, 3–17 .sl8, 3–2, 3–21 cyclic, 2–4, 2–5 .sm8, 3–2, 3–4, 3–9, 3–21 message, definition, 2–3 messaging, 3–14, 3–15...
  • Page 62 Index I–2 adding to scan list, scan list editor input screen, 3–11 data, 2–5 configuring in scan list, 3–13 definition, 2–3 failure table, 2–5 data map, 3–17 I/O data, 2–2 image table, 1–3 input data table, 2–5 mapping scheme output data table, 2–5 FLEX I/O module, B–9 removing from scan list, 3–9 photoelectric sensor, B–3...
  • Page 63 Index I–3 module settings, 3–4 SDN, 3–5, 3–11, 3–15 saving files, 3–21 scan list Add Devices to Scan List screen, 3–12 names, assigning from project, 3–6 adding devices to, scan list editor screen, 3–11 network, who, 3–3 auto map, 3–15 screen, 2–7 configuring a device, 3–13 no.
  • Page 64 Index I–4 align all, 3–16 and bit, 3–18 vendor, 3–10 X, 3–16 word Publication 1784-6.5.28 – July 1998...
  • Page 65 Sequence What is not in the right order? Other Comments Use back for more comments. Your Name Location/Phone Return to: Technical Communication, Allen-Bradley Co., 1 Allen-Bradley Drive, Mayfield Hts., OH 44124 Phone: (216)646-3166 FAX: (216)646-4320 AB PLCs Publication ICCG-5.21-August 1995...
  • Page 66 PLEASE FASTEN HERE (DO NOT STAPLE) Other Comments PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE Technical Communication 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124-9705...
  • Page 67 AB PLCs...
  • Page 68 Puerto Rico Qatar Romania Russia–CIS Saudi Arabia Singapore Slovakia Slovenia South Africa, Republic Spain Sweden Switzerland Taiwan Thailand Turkey United Arab Emirates United Kingdom United States Uruguay Venezuela Yugoslavia Allen-Bradley Headquarters, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1) 414 382-2000 Fax: (1) 414 382-4444 Publication 1784-6.5.28 – July 1998 PN 955132–82...

This manual is also suitable for:

Devicenet 1784-cpcids

Table of Contents