Compact™ I/O 1769-ADN DeviceNet Adapter 1769-ADN User Manual
Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of these products must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.
ATTENTION ! Environment and Enclosure This equipment is intended for use in a Pollution Degree 2 industrial environment, in overvoltage Category II applications (as defined in IEC publication 60664-1), at altitudes up to 2000 meters without derating. This equipment is considered Group 1, Class A industrial equipment according to IEC/CISPR Publication 11.
Table of Contents Chapter 1 Installing Your DeviceNet Adapter Compact I/O Module Description . . . . . . . . . . . . . . . . . . . 1-1 Module Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Module Prevent Electrostatic Discharge . . . . . . . . . . . . . . . . . . . Remove Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Assembly. . . . . . . . . . . . . . . . . . . . . . . . . .
ii 1769-OA16 100 to 240V AC Solid State Output Module (16 Point) . . . . . . . . . . . . . . . . . . . . . . . Output Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . Output Module’s Input Data File. . . . . . . . . . . . . . . . 1769-OB16 Solid State 24V DC Source Output Module (16 Point) . . . . . . . . . . . . . . . . . . . . . . . Output Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iii Chapter 3 Configuring Your Compact I/O Series A DeviceNet Adapter About RSNetworx . . . . . . . . . . . . . . . . . . . . . . . . . Adding Your Series A DeviceNet Adapter Offline . . Configuring Your Compact I/O System Offline . . . . Configuring Your Series A Adapter . . . . . . . . . . Using Banks of I/O . . . . . . . . . . . . . . . . . . . . . . . . Configuration Rules for the Series A Adapter. . . Configuring Discrete Input Modules. . . . . . . . . . . . Configuring Discrete Output Modules . . .
iv Chapter 5 Troubleshooting with the Indicators Diagnostic Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Chapter 6 Application Examples 1747-SDN Application Example . . . . . . . . . . . . . . . . Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the SLC System . . . . . . . . . . . . . . . . Configuring the 1769-ADN DeviceNet Adapter . . Configuring the 1747-SDN . . . . . . . . . . . . . . . . . . . .
v Appendix C 1769-ADN Throughput Characteristics Series A Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . About Adapter Throughput Characteristics . . . . . . . . . . . Turn-Around Time (ttat) . . . . . . . . . . . . . . . . . . . . . . . . Minimum Inter-Scan Delay (ISD) for Polled Connections Quick Connect Performance . . . . . . . . . . . . . . . . . . . . . Quick Connect Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi Notes: Publication 1769-UM001B-EN-P - October 2002
Preface Read this preface to familiarize yourself with the rest of the manual. This preface covers the following topics: • • • • • who should use this manual how to use this manual related publications conventions used in this manual Allen-Bradley support Who Should Use This Manual Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use Allen-Bradley Compact I/O adapters.
Preface 2 Related Documentation The table below provides a listing of publications that contain important information about Compact I/O products.
Preface Title Publication Number Compact I/O Communication Bus Expansion Cables Installation Instructions 1769-5.15 Compact 1769-ECR Right End Cap/Terminator 1769-5.9 Compact 1769-ECL Left End Cap/Terminator 1769-5.16 Compact 1769-IF4 Analog Input Module Installation Instructions 1769-IN016 Compact 1769-OF2 Analog Output Module Installation Instructions 1769-IN017 3 If you would like a manual, you can: • download a free electronic version from the internet at www.theautomationbookstore.
Preface 4 Allen-Bradley Support Allen-Bradley offers support services worldwide, with over 75 Sales/Support Offices, 512 authorized distributors and 260 authorized Systems Integrators located throughout the United States alone, plus Allen-Bradley representatives in every major country in the world.
Chapter 1 Installing Your DeviceNet Adapter Module This chapter explains how to install your DeviceNetTM adapter.
1-2 Installing Your DeviceNet Adapter Module Module Installation Compact I/O 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 21) and circuits not exceeding Over Voltage Category II2 (IEC 60664-1).3 1.
Installing Your DeviceNet Adapter Module System Assembly 1-3 The adapter can be attached to adjacent 1769 modules before or after mounting. For mounting instructions, see “Panel Mounting” on page 1-4, or “DIN Rail Mounting” on page 1-6. To work with a system that is already mounted, see “Replacing the 1769-ADN within a System” on page 1-6. The following procedure shows you how to assemble the Compact I/O system. a b c a e 1769-ADN a a d 42126 1. Disconnect power. 2.
1-4 Installing Your DeviceNet Adapter Module 8. Lock the end cap bus terminator (e). A 1769-ECR or 1769-ECL right or left end cap must be used to terminate the end of the serial communication bus. IMPORTANT 9. Refer to the “DeviceNet Wiring” section on page 1-7. Mounting the Adapter and an I/O Module ATTENTION ! During panel or DIN rail mounting of all devices, be sure that all debris (metal chips, wire strands, etc.) is kept from falling into the adapter or modules.
Installing Your DeviceNet Adapter Module 1-5 Panel Mounting Using the Dimensional Template For more than 1 module: Number of modules x 35mm (1.38in) 35 35 Right End Cap 1769 I/O 28.5 (1.12) 1769 I/O 35 (1.38) 1769 Power Supply 122.6+0.2 (4.826+0.008) 70 (2.76) 1769-ADN 132 (5.197) 40 (1.58) Hole spacing tolerance: +0.4mm (0.016in). mm (in) (1.38) (1.
1-6 Installing Your DeviceNet Adapter Module DIN Rail Mounting The adapter can be mounted using the following DIN rails: • 35 x 7.5mm (EN50022 - 35 x 7.5) • 35 x 15mm (EN 50022 - 35 x 15) Before mounting the module on a DIN rail, close the DIN rail latches. Press the DIN rail mounting area of the module against the DIN rail. The latches will momentarily open and lock into place. Replacing the 1769-ADN within a System The adapter can be replaced while the system is mounted to a panel (or DIN rail). 1.
Installing Your DeviceNet Adapter Module 1-7 10. Replace the DeviceNet cable on the module by tightening the upper and lower retaining screws and attaching the connector to the module. Set the network address switches to the same value as the removed adapter. Grounding the Adapter This product is intended to be mounted to a well-grounded mounting surface such as a metal panel.
1-8 Installing Your DeviceNet Adapter Module TIP DeviceNet cable colors are shown on the wiring label on the front of the adapter. Note: A 10-pin linear plug (i.e., 1787-PLUG10R) will not fit while a 1799-DNETCON or -DNETSCON will fit.
Installing Your DeviceNet Adapter Module 1-9 Use the removable, write-on label to mark your I.D. tag, etc. with permanent ink. Your markings are visible when the module door is closed. TIP Configuring the 1769-ADN Series B adapters that have their node address switches set to 95, startup in a special factory mode that does not support I/O connections. Series B adapters should not have their node address set to 95 for normal use. The 1769-ADN must be configured with RSNetworx for DeviceNet.
1-10 Installing Your DeviceNet Adapter Module Notes: Publication 1769-UM001B-EN-P - October 2002
Chapter 2 How Communication Takes Place and I/O Image Table Mapping This chapter explains how communication takes place and about I/O image table mapping. Included is information about: • I/O Structure • Communication Choices • Mapping I/O Data into the Image Table Communication Over the 1769 Bus One 1769-ADN DeviceNet adapter can interface with up to 30 Compact I/O modules to make a Compact I/O system.
2-2 How Communication Takes Place and I/O Image Table Mapping The amount of input data in the adapter’s input image for each I/O module is based on the configuration of each I/O module done as part of the 1769-ADN configuration. If an I/O module is configured to have 0 words of input data, then it does not appear in the input image of the 1769-ADN. DeviceNet Adapter Input Image (Read Data) Adapter Status Words Slot 1 Input Data Slot 2 Input Data Slot 3 Input Data ...
How Communication Takes Place and I/O Image Table Mapping 2-3 The adapter status bit descriptions are shown in the following table.
2-4 How Communication Takes Place and I/O Image Table Mapping Communication Choices The Compact I/O DeviceNet adapter module supports multiple communication choices. These choices all use the DeviceNet adapter input image and output image structure previously described. The DeviceNet master makes the actual communication choice. The choices are: Polled1 - data is sent by the adapter in response to received data Strobe - data is sent by the adapter in response to the strobe command.
How Communication Takes Place and I/O Image Table Mapping Module Description For I/O data definition, see: 1769-OW8 AC/DC Relay Output Module (8 Point) 2-13 1769-OW8I Individually Isolated AC/DC Relay Output Module (8 Point) 2-14 1769-OW16 AC/DC Relay Output Module (16 Point) 2-15 1769-IQ6XOW4 24V DC Sink/Source Input AC/DC Relay Output Module (6 Point In, 4 Point Out) 2-16 1769-IT6 Thermocouple/mV Input Module 2-17 1769-IR6 RTD/Resistance Input Module 2-18 1769-IF4XOF2 Combination Analog Mod
How Communication Takes Place and I/O Image Table Mapping 1769-IF4 (Series A and B) Analog Current/Voltage Input Module (4 Channel) Input Data For each 1769-IF4 input module, input data words 0-3 contain the analog value of the inputs. Word 4 and 5 contain analog status and error information.
How Communication Takes Place and I/O Image Table Mapping Output Data Word For each 1769-OA8 module, output data word 0 contains the control program’s directed state of the discrete output points. Bits 8 to 15 are not used. 0 Bit Position 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0 0 0 w w w w w w w w 0 0 0 0 0 w = write Input Data For each 1769-OA8 module, input data word 0 contains the state of the module’s output data (output data echo) word 0.
2-8 How Communication Takes Place and I/O Image Table Mapping 1769-OA16 100 to 240V AC Solid State Output Module (16 Point) Output Data File Data output bits are turned on or off using the bit positions in Word 0. 1 = output on 0 = output off Example: To turn on bit position 12, type 1 in Word 0, Bit 12. For each module, slot x, word 0 in the output data file contains the control program’s directed state of the discrete output points.
How Communication Takes Place and I/O Image Table Mapping Output Data Word For each 1769-OB16 module, output data word 0 contains the control program’s directed state of the discrete output points. 0 Bit Position 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 w w w w w w w w w w w w w w w w w = write Input Data For each 1769-OB16 module, input data word 0 contains the state of the module’s output data (output data echo) word 0.
2-10 How Communication Takes Place and I/O Image Table Mapping Output Data For each 1769-OB16P module, output data word 0 contains the control program’s directed state of the discrete output points.
How Communication Takes Place and I/O Image Table Mapping 2-11 1769-OF2 (Series A and B) Output Data Analog Current/Voltage Output Module (2 Channel) For each 1769-OF2 module, output data words 0 and 1 contain the channel 0 and channel 1 output data.
2-12 How Communication Takes Place and I/O Image Table Mapping Output Data For each 1769-OV16 module, output data word 0 contains the control program’s directed state of the discrete output points.
How Communication Takes Place and I/O Image Table Mapping Output Data Word For each 1769-OW8 module, output data word 0 contains the control program’s directed state of the discrete output points. Bits 8 to 15 are not used. 0 Bit Position 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 0 0 0 w w w w w w w w 0 0 0 0 0 w = write Input Data For each 1769-OW8 module, input data word 0 contains the state of the module’s output data (output data echo).
2-14 How Communication Takes Place and I/O Image Table Mapping Output Data For each 1769-OW8I module, output data word 0 contains the control program’s directed state of the discrete output points. Bits 8 to 15 are not used.
How Communication Takes Place and I/O Image Table Mapping Output Data File Data output bits are turned on or off using the bit positions in Word 0. 1 = output on 0 = output off Example: To turn on bit position 12, type 1 in Word 0, Bit 12. For each module, slot x, word 0 in the output data file contains the control program’s directed state of the discrete output points.
2-16 How Communication Takes Place and I/O Image Table Mapping Output Data For each 1769-IQ6XOW4 module, output data word 0 contains the control program’s directed state of the discrete output points. Bits 4 to 15 are not used.
How Communication Takes Place and I/O Image Table Mapping 2-17 1769-IT6 Thermocouple/mV Input Data Input Module Word The input data file contains the analog values of the inputs.
2-18 How Communication Takes Place and I/O Image Table Mapping 1769-IR6 RTD/Resistance Input Module Input Data Word The first six words (0 to 5) of the input data file contain the analog RTD or resistance values of the inputs. Words 6 and 7 provide sensor/channel status feedback for use in your control program as shown below.
How Communication Takes Place and I/O Image Table Mapping 1769-IF4XOF2 Combination Analog Module 2-19 Input Data The input data file provides access to input data for use in the control program, over-range indication for the input and output channels, and output data feedback as described below. Word IMPORTANT Input words 6 and 7 contain the Output Data Echo/Loopback information for output channels 0 and 1 respectively.
2-20 How Communication Takes Place and I/O Image Table Mapping Output Data The output data file applies only to output data from the module as shown in the table below. Word IMPORTANT Bits 0 through 6 and bit 15 of output data words 0 and 1 should always be set to zero in your control program. If they are not set to 0, the invalid data flag (Ex) will be set for that channel. However, the channel will continue to operate with the previously converted value.
How Communication Takes Place and I/O Image Table Mapping 1769-HSC High-Speed Counter Module 2-21 Output Array The Output Array, which consists of 34 words, allows you to access the module’s real-time output data to control the module. The default value is all zeros. IMPORTANT The Output Array contains dynamic configuration data. The settings in the Output Array must be compatible with the settings in the Configuration Array.
2-22 How Communication Takes Place and I/O Image Table Mapping Word 15 14 13 20 21 12 11 10 Bit 09 08 07 06 05 Range12To15[1].OutputControl Not Used 22 23 24 25 26 27 Inv Not Used 04 LDW Type 03 02 Not Used 01 00 ToThisCtr Range12To15[2].LowLimit Range Low Limit Range12To15[2].OutputControl 28 29 30 31 32 33 Inv Not Used LDW Type Not Used ToThisCtr Range12To15[3].LowLimit Range Low Limit Range12To15[3].
How Communication Takes Place and I/O Image Table Mapping Word 3 4 5 6 7 8 9 10 11 12 15 14 13 12 11 10 Not Used 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 04 03 02 01 Not Used Not Used Function Ctr[0].CurrentCount Counter 0 Current Count Ctr[0].StoredCount Counter 0 Stored Count Ctr[0].CurrentRate Counter 0 Current Rate Ctr[0].PulseInterval Counter 0 Pulse Interval C0PW RV Not Used IDW REZ CUdf COvf Counter 0 Status Flags Not Used Ctr[1].
2-24 How Communication Takes Place and I/O Image Table Mapping Defaults Factory defaults are the values assigned when you: • first power up the system, and • no previous user-programmed stored settings have been applied Each I/O module has default values associated with it.
How Communication Takes Place and I/O Image Table Mapping 2-25 Module defaults for I/O size: Factory defaults (words) Real time setting (words) Description Input Output Input Output 1769-IR6 RTD/Resistance Input Module 8 0 6 0 1769-IF4XOF2 Combination Analog Module 8 0 6 0 1769-HSC High-Speed Counter Module 35 34 35 34 Factory defaults (for size) set I/O sizes to the maximum amount of I/O data for a module to provide maximum functionality.
2-26 How Communication Takes Place and I/O Image Table Mapping Notes: Publication 1769-UM001B-EN-P - October 2002
Chapter 3 Configuring Your Compact I/O Series A DeviceNet Adapter Read this chapter to configure your Series A DeviceNet adapter. Included is information about: • • • • Adding Your Series A DeviceNet Adapter Offline Configuring Your Compact I/O System Offline Using Banks of I/O Configuring Your Compact I/O System Online About RSNetworx RSNetworx for DeviceNet is the software tool used to configure your Compact I/O Series A DeviceNet adapter and its related modules.
3-2 Configuring Your Compact I/O Series A DeviceNet Adapter Configuring Your Compact I/O System Offline Now that you’ve added the 1769-ADN DeviceNet adapter offline, you’ll need to configure the adapter and all of the devices in the 1769 I/O system. Configuring Your Series A Adapter You’ll see this screen when you double-click on the 1769-ADN DeviceNet adapter icon. You can add a description, alter the node address, and view the device identity information.
Configuring Your Compact I/O Series A DeviceNet Adapter 3-3 Follow these guidelines when listing devices: • List devices in the order in which they reside in the bank, from left to right. Note: The Series A adapter must be in slot 0 of bank 1. • Only enter cables in the first bank they reside in. • Be sure to enter all devices in their proper location, including power supplies, cables, and the end cap. • Refer to the Configuration Rules for the Series A Adapter on page 3-7.
3-4 Configuring Your Compact I/O Series A DeviceNet Adapter 2. Continue to list your devices down the left column and continue at the top right column if necessary. Note: To limit the need to reconfigure, make sure you understand the Configuration Rules for the Series A Adapter on page 3-7. Notice that only I/O modules are assigned Slot numbers. 3. Once you’ve listed all of the devices for Bank 1, go on to Bank 2 if necessary.
Configuring Your Compact I/O Series A DeviceNet Adapter 3-5 4. Choose the Bank 2 Configuration tab. 5. List all of your devices in bank 2 following the same guidelines as for Bank 1. 6. If you have three banks, choose the Bank 3 Configuration tab and follow the same guidelines as for Bank 1 and/or Bank 2. 7. Make sure that the last bank of the node is an end cap/terminator (1769-ECR or 1769-ECL).
3-6 Configuring Your Compact I/O Series A DeviceNet Adapter relevant sections on pages 3-9 to 3-20 to configure each 1769 I/O module. 10. Once all of the I/O modules are configured, choose OK. 11. From the File menu, choose Save. 12. Go on-line. 13. Select the adapter you wish to modify and download your changes to make them go into affect.
Configuring Your Compact I/O Series A DeviceNet Adapter Using Banks of I/O 3-7 Configuration Rules for the Series A Adapter • The Series A adapter must be the first and left-most module in the system (the first module of Bank 1). • The Series a adapter can communicate with up to 30 modules in a system. • Each bank of I/O must have its own power supply. • A bank of I/O can have a maximum of 16 modules with a maximum of eight on either side of the power supply, depending upon module loading on the supply.
3-8 Configuring Your Compact I/O Series A DeviceNet Adapter Example Configurations 1769 I/O 1769 I/O 3 4 5 6 1769-CRRx 1769 I/O 2 1769 Power Supply 1 1769 I/O I/O Slot Number 1769 I/O Bank 1 1769 I/O 1769-ADN The following illustrations show examples of two valid system setups.
Configuring Your Compact I/O Series A DeviceNet Adapter Configuring Discrete Input Modules 3-9 Follow these guidelines to configure discrete input modules. 1. From the Bank Configuration tab, click on the slot number of the input module you would like to configure. You’ll see a screen similar to this. 2. To change the input or output size, enter the new word value in the appropriate field. If you enter a non-valid number for a particular module, you will see a screen with a range of valid numbers. 3.
3-10 Configuring Your Compact I/O Series A DeviceNet Adapter 4. You may choose from the pull-down menu to change the electronic keying to exact match, compatible module, or disable keying. • Exact Match: The programmed module type (e.g. 1769-IA16) and the revision must match exactly with the actual module. • Compatible Module: The programmed module type must match the actual module, but the revision of the actual module can be equal or greater than the programmed revision.
Configuring Your Compact I/O Series A DeviceNet Adapter Configuring Discrete Output Modules 3-11 Follow these guidelines to configure discrete output modules. 1. From the Bank Configuration tab, click on the slot number of the output module you would like to configure. You’ll see a screen similar to this. 2. To change the input or output size, enter the new word value in the appropriate field. If you enter a non-valid number for a particular module, you will see a screen with a range of valid numbers.
3-12 Configuring Your Compact I/O Series A DeviceNet Adapter 3. To change the revision key, enter a new revision value in the field marked revision. Note: 0 is not a valid revision number. Refer to the Comparison Feature section on page 3-22 for an explanation on the use of this field. 4. You may choose from the pull-down menu to change the electronic keying to exact match, compatible module, or disable keying. • Exact Match: The programmed module type (e.g.
Configuring Your Compact I/O Series A DeviceNet Adapter 3-13 7. If desired, choose Data Description to view the definitions of each input and output word. 8. To remove specific words/functions, uncheck the appropriate box and choose OK. 9. To apply the specific words/functions, check the appropriate box and choose OK. 10. Once you’ve finished making your changes, you may choose OK from the I/O Module screen to return to the Bank Configuration screen.
3-14 Configuring Your Compact I/O Series A DeviceNet Adapter Configuring Analog Input Modules Follow these guidelines to configure analog input modules. 1. From the Bank Configuration tab, click on the slot number of the analog input module you would like to configure. You’ll see a screen similar to this. 2. To change the input or output size, enter the new word value in the appropriate field. If you enter a non-valid number for a particular module, you will see a screen with a range of valid numbers.
Configuring Your Compact I/O Series A DeviceNet Adapter 3-15 3. To change the revision key, enter a new revision value in the field marked revision. Note: 0 is not a valid revision number. Refer to the Comparison Feature section on page 3-22 for an explanation on the use of this field. 4. You may choose from the pull-down menu to change the electronic keying to exact match, compatible module, or disable keying. • Exact Match: The programmed module type (e.g.
3-16 Configuring Your Compact I/O Series A DeviceNet Adapter 8. If desired, choose Set for I/O Only to automatically modify the input/output sizes to real time size defaults and other configurations to their default values. 9. If desired, choose Data Description to view the definitions of each input and output word. 10. To remove specific words/functions, uncheck the appropriate box and choose OK. 11. To apply the specific words/functions, check the appropriate box and choose OK. 12.
Configuring Your Compact I/O Series A DeviceNet Adapter Configuring Analog Output Modules 3-17 Follow these guidelines to configure analog output modules. 1. From the Bank Configuration tab, click on the slot number of the analog output module you would like to configure. You’ll see a screen similar to this. 2. To change the input or output size, enter the new word value in the appropriate field.
3-18 Configuring Your Compact I/O Series A DeviceNet Adapter 3. To change the revision key, enter a new revision value in the field marked revision. Note: 0 is not a valid revision number. Refer to the Comparison Feature section on page 3-22 for an explanation on the use of this field. 4. You may choose from the pull-down menu to change the electronic keying to exact match, compatible module, or disable keying. • Exact Match: The programmed module type (e.g.
Configuring Your Compact I/O Series A DeviceNet Adapter 3-19 RSNetworx uses this information when it performs an audit of the configuration with regards to +24V requirements. Note: This parameter is not saved in the Series A 1769-ADN adapter. The default is that the 1769 power supply is supplying the +24V for this module any time you perform an upload from the 1769-ADN adapter. Therefore, when online refer to Auditing the Configuration on page 3-20. 9.
3-20 Configuring Your Compact I/O Series A DeviceNet Adapter Configuring Power Supplies, Cables, and End Cap Electronic keys for these devices are automatically set to Exact Match. No additional configuration is necessary. Completing Configuration After you’ve finished specifying the Series A adapter configuration and the individual device configurations (I/O modules, power supplies, cables, and end cap), choose Apply or OK to complete the offline configuration.
Configuring Your Compact I/O Series A DeviceNet Adapter Configuring Your Compact I/O System Online 3-21 If your 1769 I/O system physically exists, you’ll save time by configuring the Compact I/O system online. By configuring online, you simply upload the entire I/O layout including end caps, cables, and power supplies. Then, you only need to modify the configuration parameters for each I/O module and re-save (download) the final configuration back to the Series A 1769-ADN adapter.
3-22 Configuring Your Compact I/O Series A DeviceNet Adapter Comparison Feature The comparison feature regards matching. A match or mismatch is determined based on a comparison of the programmed devices (the devices stored in the adapter’s non-volatile memory) and the actual devices present on the 1769 bus. The electronic keying options (below) are applied on a position-by-position basis.
Configuring Your Compact I/O Series A DeviceNet Adapter 3-23 Uploading Configurations The first time you select a 1769-ADN from RSNetworx when online, the software will upload the configuration saved in the 1769-ADN. TIP You may upload the saved configuration from the 1769-ADN at any time when online by clicking the right mouse button. If there is a mismatch between the saved system keying configuration and the keys of the actual devices on the 1769 bus, you will see the following mismatch screen.
3-24 Configuring Your Compact I/O Series A DeviceNet Adapter Downloading Configurations When you complete a configuration online and choose Apply or OK, assuming the configuration passes the audit, RSNetworx downloads the configuration to the 1769-ADN. The 1769-ADN then performs a key check on the requested devices. Refer to the Comparison Feature on page 3-22.
Configuring Your Compact I/O Series A DeviceNet Adapter 3-25 Using the Clear Memory Function The Clear Memory feature is activated by choosing Reset Configuration and Upload Actual Devices under the Reset tab. This will return the 1769-ADN to the ‘No Adapter or I/O Configuration’ state (as if it never was configured for the 1769 modules) and cause the software to pull the configuration from the actual devices.
3-26 Configuring Your Compact I/O Series A DeviceNet Adapter Notes: Publication 1769-UM001B-EN-P - October 2002
Chapter 4 Configuring Your Compact I/O Series B DeviceNet Adapter Read this chapter to configure your Series B DeviceNet adapter. Included is information about: • • • • Adding Your Series B DeviceNet Adapter Offline Configuring Your Compact I/O System Offline Using Banks of I/O Configuring Your Compact I/O System Online About RSNetworx RSNetworx for DeviceNet, version 4.00, is the software tool used to configure your Compact I/O Series B DeviceNet adapter and its related modules.
4-2 Configuring Your Compact I/O Series B DeviceNet Adapter Configuring Your Compact I/O System Offline Now that you’ve added the Series B 1769-ADN DeviceNet adapter offline, you’ll need to configure the adapter and all of the devices in the 1769 I/O system. Configuring Your Series B Adapter You’ll see this screen when you double-click on the 1769-ADN DeviceNet adapter icon. You can add a description, alter the node address, and view the device identity information.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-3 Follow these guidelines when adding devices: • List devices in the order in which they reside in the bank, from left to right. Note: The Series B adapter must be in slot 0 of bank 1. • Only enter cables in the first bank they reside in. • Be sure to enter all devices in their proper location, including power supplies, cables, and the end cap. • Refer to the Configuration Rules for Series B Adapters on page 4-6.
4-4 Configuring Your Compact I/O Series B DeviceNet Adapter Follow these steps to assign banks to each module: a. Select the desired module and choose Properties. You’ll see a screen similar to this. b. Enter the bank number in the Bank field. TIP To save time, assign the bank numbers to the first (left-most) modules in each bank, starting with bank one. The software ripples the bank modification down the list when you choose OK. c. Choose OK.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-5 4. Make sure that the last bank of the node is an end cap/terminator (1769-ECR or 1769-ECL). For information on 1769 bus configuration rules, refer to Configuration Rules for Series B Adapters on page 4-6. 5. Choose Apply to be sure that your system passes the electrical audit. 6. After defining the devices on this 1769-ADN node, refer to the relevant sections on pages 4-9 to 4-25 to configure each 1769 I/O module. 7.
4-6 Configuring Your Compact I/O Series B DeviceNet Adapter Using Banks of I/O Configuration Rules for Series B Adapters • The Series B adapter must be the first and left-most module in the system (the first module of Bank 1). • The Series B adapter can communicate with up to 30 modules in a system. • Each bank of I/O must have its own power supply. • A bank of I/O can have a maximum of 16 modules with a maximum of eight on either side of the power supply, depending upon module loading on the supply.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-7 • The Series B adapter supports a maximum of 196-254 words (392-508 bytes) of output data distributed across all of the modules, depending on the number of modules present in the system. Use the following equation to calculate the maximum number of output words: Maximum Output Words = 256 - (Number of Output Modules) x 2 Where the "Number of Output Modules" is the number of output modules configured to have 1 or more words of output data.
4-8 Configuring Your Compact I/O Series B DeviceNet Adapter Example Configurations 1769 I/O 1769 I/O 3 4 5 6 1769-CRRx 1769 I/O 2 1769 Power Supply 1 1769 I/O I/O Slot Number 1769 I/O Bank 1 1769 I/O 1769-ADN The following illustrations show examples of two valid system setups.
Configuring Your Compact I/O Series B DeviceNet Adapter Configuring Discrete Input Modules 4-9 Follow these guidelines to configure discrete input modules. 1. From the Module Configuration tab, double-click on the input module you would like to configure. You’ll see a screen similar to this. 2. To assign the module to a different bank, enter the bank number in the Bank field. TIP To save time, assign the bank numbers to the first (left-most) modules in each bank, starting with bank one.
4-10 Configuring Your Compact I/O Series B DeviceNet Adapter 3. From the Advanced Parameters tab, you can configure editable parameters by selecting from the pull-down menus or directly typing in the value. You can configure the Input Data Size parameter to No Input Data or Input Data (1 Word). You can configure the Electronic Keying parameter to Disable Keying, Exact Match, or Compatible Module. • Exact Match: The programmed module type (e.g.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-11 5. From the EDS File tab, you can access the device’s configuration description file. Access to the EDS file is provided to enable you to determine which version of the device’s EDS file is installed on your system. The most up-to-date EDS file Allen-Bradley brand modules may be obtained at http://www.ab.com/networks/eds/ or by contacting your local Rockwell Automation representative.
4-12 Configuring Your Compact I/O Series B DeviceNet Adapter 7. When you have finished looking at the EDS file, close the Notepad window. 8. Choose OK to return to the Module Configuration tab. Configuring Discrete Output Modules Follow these guidelines to configure discrete output modules. 1. From the Module Configuration tab, double-click on the output module you would like to configure. You’ll see a screen similar to this.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-13 2. To assign the module to a different bank, enter the bank number in the Bank field. TIP To save time, assign the bank numbers to the first (left-most) modules in each bank, starting with bank one. The software ripples the bank modification down the list when you close the module’s property window. 3. From the Advanced Parameters tab, you can configure editable parameters by selecting from the pull-down menus or directly typing in the value.
4-14 Configuring Your Compact I/O Series B DeviceNet Adapter 4. From the Configuration Settings tab, double-click on the Program State or Fault State groups to configure them. You will see a screen similar to this one when you select a Program State group. You can configure the Program/Fault State to User-Defined Safe-State or Hold Last State. TIP Publication 1769-UM001B-EN-P - October 2002 When you uncheck the "Groups" box, you will see all of the module’s parameters in a single list.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-15 You will see a screen similar to this one when you select a Program Value or Fault Value group. You can configure the Program/Fault Value to On or Off. 5. Choose OK. 6. From the EDS File tab, you can access the device’s configuration description file. Access to the EDS file is provided to enable you to determine which version of the device’s EDS file is installed on your system.
4-16 Configuring Your Compact I/O Series B DeviceNet Adapter Changes to this file are not recommended except for users with appropriate training or under the guidance of Rockwell Automation, Inc. authorized technical support representative. 7. Choose View to see the EDS file. 8. When you have finished looking at the EDS file, close the Notepad window. 9. Choose OK to return to the Module Configuration tab.
Configuring Your Compact I/O Series B DeviceNet Adapter Configuring Analog Input Modules 4-17 Follow these guidelines to configure analog input modules. 1. From the Module Configuration tab, double-click on the input module you would like to configure. You’ll see a screen similar to this. 2. To assign the module to a different bank, enter the bank number in the Bank field. TIP To save time, assign the bank numbers to the first (left-most) modules in each bank, starting with bank one.
4-18 Configuring Your Compact I/O Series B DeviceNet Adapter 3. From the Advanced Parameters tab, you can configure editable parameters by selecting from the pull-down menus or directly typing in the value. You can configure the Input Data Size parameter to No Input Data or 1-6 Words. You can configure the Electronic Keying parameter to Disable Keying, Exact Match, or Compatible Module. • Exact Match: The programmed module type (e.g.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-19 4. From the Configuration Settings tab, double-click on a Channel to configure it. You will see a screen similar to this one. You can configure Channel 3 to Disable or Enable. You can configure Filter Frequency to 60Hz, 50Hz, 250Hz, or 500Hz. You can configure Input Type to (-10 to +10V dc), (0 to 5V dc), (0 to 10V dc), (4 to 20mA), or (1 to 5V dc).
4-20 Configuring Your Compact I/O Series B DeviceNet Adapter 6. From the EDS File tab, you can access the device’s configuration description file. Access to the EDS file is provided to enable you to determine which version of the device’s EDS file is installed on your system. The most up-to-date EDS file Allen-Bradley brand modules may be obtained at http://www.ab.com/networks/eds/ or by contacting your local Rockwell Automation representative.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-21 8. When you have finished looking at the EDS file, close the Notepad window. 9. Choose OK to return to the Module Configuration tab. Configuring Analog Output Modules Follow these guidelines to configure analog output modules. 1. From the Module Configuration tab, double-click on the output module you would like to configure. You’ll see a screen similar to this.
4-22 Configuring Your Compact I/O Series B DeviceNet Adapter 2. To assign the module to a different bank, enter the bank number in the Bank field. TIP To save time, assign the bank numbers to the first (left-most) modules in each bank, starting with bank one. The software ripples the bank modification down the list when you close the module’s property window. 3. From the Advanced Parameters tab, you can configure editable parameters by selecting from the pull-down menus or directly typing in the value.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-23 4. From the Configuration Settings tab, double-click on a Channel to configure it. You will see a screen similar to this one. You can configure Channel 0 to Disable or Enable. You can configure Communication Failure parameter to Leave Outputs in Program Mode or Change Outputs to Fault Mode. You can configure the Output Range parameter to (-10 to +10V dc), (0 to 5V dc), (0 to 10V dc), (4 to 20mA), or (1 to 5V dc).
4-24 Configuring Your Compact I/O Series B DeviceNet Adapter 6. From the EDS File tab, you can access the device’s configuration description file. Access to the EDS file is provided to enable you to determine which version of the device’s EDS file is installed on your system. The most up-to-date EDS file Allen-Bradley brand modules may be obtained at http://www.ab.com/networks/eds/ or by contacting your local Rockwell Automation representative.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-25 8. When you have finished looking at the EDS file, close the Notepad window. 9. Choose OK to return to the Module Configuration tab. Configuring Power Supplies, Cables, and End Cap Electronic keys for these devices are automatically set to Compatible. No additional configuration is necessary.
4-26 Configuring Your Compact I/O Series B DeviceNet Adapter Viewing the Mapping Summaries 1. To view the mapping summaries, choose the I/O Summary tab. This is a summary of the configured size and format of the I/O data for the 1769-ADN. 2. To change the I/O messaging type, select Polled, COS (Change of State) or Cyclic from the I/O Type field. 3. Double-click on the module to make any changes to the byte size. 4. Choose OK.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-27 Viewing the Transactions The Transactions tab allows you to send services supported by this device. The "Clear/Reset Memory" transaction returns the adapter’s and all module’s configurations to the factory defaults (i.e. empty). This operation cannot be undone. To return all configuration to the factory defaults, check the "Clear/Reset Memory" box and choose Execute.
4-28 Configuring Your Compact I/O Series B DeviceNet Adapter Apply/OK Button When you choose Apply or OK, the software downloads the configuration of the desired devices to the 1769-ADN if the key check on the system keying configuration has passed.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-29 Comparison Feature The comparison feature regards matching. A match or mismatch is determined based on a comparison of the programmed devices (the devices stored in the adapter’s non-volatile memory) and the actual devices present on the 1769 bus. The electronic keying options (below) are applied on a position-by-position basis.
4-30 Configuring Your Compact I/O Series B DeviceNet Adapter Uploading Configurations The first time you select a 1769-ADN from RSNetworx when online, the software will upload the configuration saved in the 1769-ADN. TIP You may upload the saved configuration from the 1769-ADN at any time when online by clicking the right mouse button. If there is a mismatch between the saved system keying configuration and the keys of the actual devices on the 1769 bus, you will see the following mismatch screen.
Configuring Your Compact I/O Series B DeviceNet Adapter 4-31 Downloading Configurations When you complete a configuration online and choose Apply or OK, assuming the configuration passes the audit, RSNetworx downloads the configuration to the 1769-ADN. The 1769-ADN then performs a key check on the requested devices. Refer to the Comparison Feature on page 4-29.
4-32 Configuring Your Compact I/O Series B DeviceNet Adapter Configuring Your Adapter for Quick Connect Operation Quick Connect is a recently introduced DeviceNet feature that reduces the amount of time that slave devices (in this case, your 1769 DeviceNet adapter) take to go from their powered-down state to a state where they are ready to accept I/O connections.
Configuring Your Compact I/O Series B DeviceNet Adapter Configured 1769-ADN Powerup Behavior 4-33 On powerup, the 1769-ADN, with a previous valid configuration, will compare the saved system keying configuration with the actual devices to determine if all of the keys match the actual devices (as defined in the Comparison Feature section on page 4-29). If they match, the 1769-ADN will complete the configuration of all I/O modules and then wait for a DeviceNet master/scanner to make a connection.
4-34 Configuring Your Compact I/O Series B DeviceNet Adapter Notes: Publication 1769-UM001B-EN-P - October 2002
Chapter 5 Troubleshooting with the Indicators Read this chapter to familiarize yourself with the diagnostic indicators and their meanings.
5-2 Troubleshooting with the Indicators LED Indication Meaning Network Status (NS) OFF Flashing GRN/OFF Solid GRN Flashing RED/OFF Solid RED No DeviceNet power or no network access On-line but not connected On-line and connected Connection time-out Critical network failure I/O Status (IO) OFF Flashing GRN/OFF Solid GRN Flashing RED/OFF Solid RED No power or outputs off Idle/program mode - one or more I/O modules in Idle Mode Device operational - all I/O modules in Run Mode Recoverable fault - one or
Chapter 6 Application Examples 1747-SDN Application Example The following application example details a 1747-SDN DeviceNet scanner controlling 1769 Compact I/O via DeviceNet and the 1769-ADN DeviceNet Adapter.
6-2 Application Examples Configuring the 1769-ADN DeviceNet Adapter Start RSNetworx for DeviceNet. At this point, you could configure your network devices offline and download these configuration files to the network devices. Instead, we will go online to configure our network. Refer to chapter 3 for information on configuring your DeviceNet system offline.
Application Examples 6-3 You’ll see this screen with your network devices. Note that this example has the 1747-SDN at node address 00, the 1769-ADN at node address 30, and the 1784-PCD at node address 62. These node address assignments are arbitrary and each device could be assigned any unique address from 00 to 63. To begin configuring your DeviceNet network you’ll configure the Compact I/O system. Double-click on the 1769-ADN icon. You’ll see this screen.
6-4 Application Examples Choose the Module Configuration tab. Choose Yes when asked if you want to upload. You’ll see this screen. The I/O Module Mismatch screen indicates that configuration has not yet been downloaded to the 1769-ADN. Choose Resolve Mismatch. You’ll see this screen. Notice that the 1769 system configuration software is now completely filled in with the actual I/O modules, power supplies, cable, and end cap. You can view the second bank by choosing the I/O Bank 2 Configuration tab.
Application Examples 6-5 Next, you’ll want to configure the individual I/O modules. When you choose the Slot button next to each I/O module, you’ll see a screen allowing you to view and modify the I/O data size, module keying, and choose the state of each output (provided the module is an output module) in the event that the SLC processor is placed in the Program or Fault mode. Modules requiring configuration, like analog I/O modules, must be configured by choosing the Slot button.
6-6 Application Examples Configuring the 1747-SDN To configure the 1747-SDN DeviceNet scanner to exchange I/O data with the 1769-ADN, double-click on the 1747-SDN. You’ll see this screen. The General tab supplies information about the scanner. Choose the Module tab and choose Upload on the Scanner Configuration screen. Once the upload is complete you’ll return to the Module tab. You should accept the defaults except for the 1747-SDN slot number.
Application Examples 6-7 When you choose Edit I/O Parameters, you’ll see this screen. Polled connection is the default1. You could choose to enable a Change of State/Cyclic connection, but we won’t be using that in this example. Refer to Chapter 2 of this document for more information. Rx (receive) and Tx (transmit) sizes default to the Total Input and Output bytes from the 1769-ADN summary page. For this example, 52 is the Rx size and 18 is the Tx size. Choose the Every Scan poll rate.
6-8 Application Examples Choose OK to accept the Polled configuration. You’ll now see the 1747-SDN Scanner Module screen. Choose the Input tab and you’ll see this screen. From this screen, you can map the input data received from the 1769-ADN into the input image table of the SLC 5/04 processor or to the M1 file. For this example, we’ll map the data into the input image table. To map the data into the input image table, click on the 1769-ADN so that it is highlighted. Now choose AutoMap.
Application Examples 6-9 Note that words O:3.1 through O:3.9 are mapped. These nine words correspond to the 18 bytes we entered into the 1747-SDN scanner’s scanlist/Edit I/O Parameters screen (which originally came from the 1769-ADN adapter’s Summary screen). We chose to map the output data to the SLC 5/04 processor’s output image rather than the M0 file. If you prefer to map to the M0 file, choose M file instead of Discrete. Choose Apply. Choose Yes to download your configuration to the 1747-SDN.
6-10 Application Examples Input Image Publication 1769-UM001B-EN-P - October 2002 I:3.0 1747-SDN Status I:3.1 1769-ADN Status Word 0 I:3.2 1769-ADN Status Word 1 I:3.3 Slot 1 Input Card, Input Data (1769-IA16) I:3.4 Slot 2 Output Card, Output Echo Data (1769-OW8) I:3.5 Slot 3 Input Card, Input Data (1769-IA16) I:3.6 Slot 4 Output Card, Output Echo Data (1769-OW8) I:3.7 Slot 5 Combo Card, Input Data (1769-IQ6XOW4) I:3.8 Slot 5 Combo Card, Output Echo Data (1769-IQ6XOW4) I:3.
Application Examples 6-11 Output Image 1756-DNB Application Example O:3.0 1747-SDN Control, including the RUN/IDLE bit (0) O:3.1 Slot 2 Output Card, Output Data (1769-OW8) O:3.2 Slot 4 Output Card, Output Data (1769-OW8) O:3.3 Slot 5 Combo Card, Output Data (1769-IQ6XOW4) O:3.4 Slot 6 Combo Card, Output Data (1769-IQ6XOW4) O:3.5 Slot 8 Output Card, Output Data (1769-OV16) O:3.6 Slot 10 Analog Output Card, Output Data 0 (1769-OF2) O:3.
6-12 Application Examples Configuring the Logix5550TM Controller System Configure your Logix5550 system by selecting the 1756-DNB module under I/O configuration in RSLogix 5000 programming software. For more information on configuring your controller or writing the controller program, refer to your ControlLogix documentation. The following sections will guide you through configuring your 1756-DNB module to produce output data to the 1769-ADN and consume input data from the 1769-ADN.
Application Examples 6-13 From the Network pull-down menu, choose Online or click on the online icon in the toolbar. You’ll see a Browse Network screen where you must select your communication path (previously configured in RSLinx for going online with your DeviceNet network). For this example, we’re using a notebook computer with a 1784-PCD card. Click on the 1784-PCD and choose OK to the subsequent warning message. You’ll see this screen with your network devices.
6-14 Application Examples To begin configuring your DeviceNet network, you’ll configure the Compact I/O system. Double-click on the 1769-ADN icon. You’ll see this screen. Choose the Module Configuration tab. Choose Yes when asked if you want to upload. You’ll see this screen. The I/O Module Mismatch screen indicates that configuration has not yet been downloaded to the 1769-ADN. Choose Resolve Mismatch.
Application Examples 6-15 You’ll see this screen. Notice that the 1769 system configuration software is now completely filled in with the actual I/O modules, power supplies, cable, and end cap. You can view the second bank by choosing the I/O Bank 2 Configuration tab. This layout matches the Hardware Setup on page 6-1. Next, you’ll want to configure the individual I/O modules.
6-16 Application Examples Choose the I/O Summary tab for the 1769-ADN DeviceNet adapter. You’ll see this screen. This is a summary of your 1769 system. Note the Total Input and Output Bytes as you’ll need this information when configuring the 1756-DNB scanner. Choose Apply. This will download your configuration to the 1769-ADN. Then choose OK to close the adapter’s window and return to the network screen.
Application Examples 6-17 The General tab supplies information about the scanner. Choose the Module tab and choose Upload on the Scanner Configuration screen. Once the upload is complete you’ll return to the Module tab. You should accept the defaults except for the 1756-DNB slot number. For this example, the slot number for the 1756-DNB in its ControlLogix chassis is 1 (the default). After modifying the chassis slot number, choose Download to Scanner.
6-18 Application Examples Choose OK to accept the Polled configuration. You’ll now see the 1756-DNB Scanner Module screen. Choose the Input tab and you’ll see this screen. From this screen, you can map the input data received from the 1769-ADN into the input tag of the Logix5550 controller or 1:I.Data.0 through 1:I.Data.12 (these are DINTs, so the total number of 16-bit words is 26 or 52 bytes). To map the data into the input image table, click on the 1769-ADN so that it is highlighted.
Application Examples 6-19 DINT 1:O.CommandRegister is used for control information to the scanner. Bit 1:O.CommandRegister.RUN is the RUN/IDLE bit which must be set to a logical 1 to place the 1756-DNB into the Run mode when the controller is in the Run mode. 1:O.Data.0 is the first actual output address. There is no offset for the output data as there was for input data. Note that words 1:O.Data.0 through 1:O.Data.4L are mapped. These 4.
6-20 Application Examples Slot 1 Input Tag Map 1:I.Data0L 1769-ADN Status Word 0 1:I.Data.0H 1769-ADN Status Word 1 1:I.Data.1L Slot 1 Input Card, Input Data (1769-IA16) 1:I.Data.1H Slot 2 Output Card, Output Echo Data (1769-OW8) 1:I.Data.2L Slot 3 Input Card, Input Data (1769-IA16) 1:I.Data.2H Slot 4 Output Card, Output Echo Data (1769-OW8) 1:I.Data.3L Slot 5 Combo Card, Input Data (1769-IQ6XOW4) 1:I.Data.3H Slot 5 Combo Card, Output Echo Data (1769-IQ6XOW4) 1:I.Data.
Application Examples 6-21 Output Image 1:O.Data.0L Slot 2 Output Card, Output Data (1769-OW8) 1:O.Data.0H Slot 4 Output Card, Output Data (1769-OW8) 1:O.Data.1L Slot 5 Combo Card, Output Data (1769-IQ6XOW4) 1:O.Data.1H Slot 6 Combo Card, Output Data (1769-IQ6XOW4) 1:O.Data.2L Slot 8 Output Card, Output Data (1769-OV16) 1:O.Data.2H Slot 10 Analog Output Card, Output Data 0 (1769-OF2) 1:O.Data.3L Slot 10 Analog Output Card, Output Data 1 (1769-OF2) 1:O.Data.
6-22 Application Examples 1769-SDN Application Example This example uses the 1769-SDN scanner module with a MicroLogix 1500 controller. MicroLogix 1500 Controllers The MicroLogix 1500 programmable controller has two different processors that are compatible with the 1769-SDN scanner module. The 1764-LSP and 1764-LRP processors can use the scanner as a DeviceNet master and own DeviceNet slave devices.
Application Examples RSLogix 500 I/O Configuration 6-23 One of the advanced features of RSLogix 500 is the ability to have the programming software establish a communications 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. This section will illustrate how to read which I/O modules are attached to the controller, and manually configure them. We will then configure the scanner.
6-24 Application Examples Starting the Project 1. Open RSLogix 500. 2. Select File. 3. New. 4. Choose MicroLogix 1500 LRP series C. 5. The screen capture below should match what you see on your computer. In this example the name for this application is “TEMP”. In the TEMP window you see everything associated with the application. Within the Controller folder you will see I/O Configuration. 6. Double click I/O Configuration.
Application Examples 6-25 I/O Configuration Screen The I/O configuration screen shows each of the controllers 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 through 16 are for Compact I/O expansion modules (referred to as local I/O, because they are physically attached to the controller). Slots 9 through 16 are only available using a Series C processor with a Series B base unit(1).
6-26 Application Examples Read I/O Configuration The next screen that appears is a communications dialog that allows you to select a communication path using RSLinx to the MicroLogix controller. If you have previously connected to a controller, the communications driver that you used before will be the active driver. This dialog screen provides the ability to change the driver or perform a Who Active across a network to locate the specific MicroLogix controller.
Application Examples 6-27 1769-SDN Scanner Module Configuration To configure a specific module, simply double-click on the module. To configure the scanner in this example, double-click on the module in slot 1. Input Words This is the number of input words the controller assigns to the module. The first 66 words (0 to 65) are required by the scanner for status. DeviceNet slave input data words start at slot word 66.
6-28 Application Examples Changing the 1769-SDN Configuration Changing (adding or removing) the amount of data the controller has assigned to the scanner is done in the expansion module configuration screen. From within RSLogix 500, 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.
Application Examples 6-29 The configuration screen for the scanner is shown below. Ignore Configuration Error Checking (enabling) this box instructs the module to ignore I/O size mismatches. If this is checked and the input/output scanlist configured by RSNetWorx (DeviceNet side of the 1769-SDN) does NOT match the amount of I/O data assigned by the controller (0 to 180 words), the module will not generate an error.
6-30 Application Examples PCCC Messaging PCCC stands for “Programmable Controller Communications Commands”. PCCC provides point to point and master/slave communications between devices. PCCC is an open protocol that is built into all Allen-Bradley controllers, and many other Allen-Bradley and third-party products. PCCC messaging has been used for many years on DH-485, DH+ and Ethernet networks, and for point-to-point communications between Allen-Bradley controllers.
Application Examples 6-31 To perform program upload/download using RSLogix 500, select Comms. From the drop-down menu, select System Comms. System Comms will generate an RSLinx screen similar to the example below. In this example, the DeviceNet interface is a 1770-KFD module. Selecting the 1770-KFD driver will show the devices on the DeviceNet network. In this example, upload/download can be performed with the devices at nodes 5, 6, 7 and 32. Node 32 is a 1769-SDN.
6-32 Application Examples Configuring a Local DeviceNet Message This section describes how to configure a local message using the scanner and a MicroLogix 1500 1764-LRP processor. Message Setup Screen Rung 0 shows a standard RSLogix 500 message (MSG) instruction preceded by conditional logic. 1. Access the message setup screen by double-clicking Setup Screen. 2. The RSLogix 500 Message Setup Screen appears.
Application Examples 6-33 “This Controller” Parameters Channel The 1764-LRP 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 also supports backplane communications through the Expansion Communication Port (ECP) as illustrated below. When ECP is chosen, you are able to select which slot position (1 to 16) the scanner resides in.
6-34 Application Examples Communication Command The 1764-LRP processor supports the six standard types of communications commands (same as all other MicroLogix 1200 and 1500 controllers) and CIP Generic. When any of these six standard commands are chosen, you can initiate standard messages to destination devices connected to DeviceNet products that support PCCC messaging (including MicroLogix and SLC controllers using 1761-NET-DNI’s, other MicroLogix 1500 controllers using 1769-SDN scanner modules, etc.
Application Examples 6-35 CIP Generic CIP stands for “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 DeviceNet. All DeviceNet devices are compliant with CIP messaging. The MicroLogix 1500 1764-LRP processor (Series C) has an enhanced message instruction that provides simple, easy to use CIP messaging.
6-36 Application Examples 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 DeviceNet is byte based, you must enter the number of bytes that will be received and sent.
Application Examples 6-37 Target Device 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 (see MSG Instruction Error Codes on page 6-39). 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. If you need to message to a device on DeviceNet, select Network Device.
6-38 Application Examples Local Node address This is the target device’s DeviceNet node number. Service DeviceNet 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 allows you to enter specific service code parameters.
Application Examples MSG Instruction Error Codes 6-39 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 subelement #18 that you can monitor from your programming software. Table 6.1 1769-SDN Module Error Code Error Code Description E0H Expansion I/O Communication Module Error.
6-40 Application Examples Notes: Publication 1769-UM001B-EN-P - October 2002
Appendix A Specifications Read this appendix to learn about the 1769-ADN specifications. 1769-ADN Specifications Series A Adapters General Specifications Specification Dimensions Value 118mm (height) x 87mm (depth) x 50mm (width) height including mounting tabs is 138mm 4.65in (height) x 3.43in (depth) x 1.97in (width) height including mounting tabs is 5.43in Approximate Shipping Weight 280g (0.
A-2 Specifications Series A Adapters Input/Output Specifications Specification Value Bus Current Draw (Maximum) 450mA at 5V dc (2.25W) Heat Dissipation 4.7W maximum I/O Capacity 30 modules Communication Rate 125k bit/s 250k bit/s 500k bit/s Indicators Module status - red/grn Network status - red/grn I/O status - red/grn Diagnostic status- red/grn DeviceNet Power Requirements DeviceNet Cable 24V dc (+4%) @ 90mA maximum, N.E.C. Class 2 Allen-Bradley part no. 1485C-P1-Cxxx.
Specifications A-3 Series B Adapters Firmware General Specifications Specification Value Dimensions 118mm (height) x 87mm (depth) x 50mm (width) height including mounting tabs is 138mm 4.65in (height) x 3.43in (depth) x 1.97in (width) height including mounting tabs is 5.43in Approximate Shipping Weight (With Carton) 280g (0.
A-4 Specifications Specification Value Enclosure Type Rating None (open-style) Certifications (When Product is Marked) c-UL-us CE1 C-Tick1 ODVA 1 Publication 1769-UM001B-EN-P - October 2002 UL Listed for Class I, Division 2 Group A,B,C,D Hazardous Locations, certified for U.S. and Canada European Union 89/336/EEC EMC Directive, compliant with: - EN 50082-2; Industrial Immunity - EN 61326; Meas./Control/Lab.
Specifications A-5 Series B Adapters Input/Output Specifications Specification Value Bus Current Draw (Maximum) Series A Series B 450mA at 5V dc (2.25W) 500mA at 5V dc (2.5W) Heat Dissipation 4.7W maximum I/O Capacity 30 modules Communication Rate 125k bit/s 250k bit/s 500k bit/s Indicators Module status Network status I/O status Diagnostic status DeviceNet Power Requirements 24V dc (+4%) @ 90mA maximum, N.E.C. Class 2 DeviceNet Cable Allen-Bradley part no. 1485C-P1-Cxxx.
A-6 Specifications Notes: Publication 1769-UM001B-EN-P - October 2002
Appendix B Explicit Messaging Application Examples 1756-DNB Explicit Messaging Application Example The following explicit messaging application example details a 1756-DNB DeviceNet scanner controlling 1769 Compact I/O via DeviceNet and the 1769-ADN DeviceNet Adapter.
B-2 Explicit Messaging Application Examples Use a “Single Parameter Read” MSG instruction for the Get 1769-ADN Status message, where one word of status information is read from the 1769-ADN. The user program consists of a single rung containing a MSG instruction to accomplish the Get 1769-ADN Status.
Explicit Messaging Application Examples B-3 The following screen is the Communications tab for the MSG instruction above. You only need to enter the path on this screen. “DNET” refers to the module on the 1756 backplane to which the message is sent. “2” is the DeviceNet port on the 1756-DNB. “19” is the DeviceNet address of the 1769-ADN.
B-4 Explicit Messaging Application Examples Get 1769 I/O Module Status Use a “CIP Generic” MSG instruction to send the Get 1769 I/O Module Status explicit message from a Logix5550 controller via a 1756-DNB scanner on DeviceNet. You’ll see in the ladder logic example to follow, a CIP Generic message is sent to the 1756-DNB scanner and ultimately to the 1769-ADN and the 1769 I/O module in slot 10.
Explicit Messaging Application Examples B-5 The following ladder logic program is an example of the MSG logic needed to initiate an explicit message to the scanner/adapter. This MSG instruction logic is specifically for the Get 1769 I/O Module Status message. Assume the 1756-DNB scanner is in slot 1 and the Logix5550 controller is in slot 0. The following screen is the Communications tab for the MSG instruction above. You only need to enter the path on this screen.
B-6 Explicit Messaging Application Examples The status word written to the tag specified in the destination field of the MSG instruction is defined as follows: Bit Description 0 0 = No module error detected 1 = Module detected error present 1 0 = Communication on bus OK 1 = Communication Fault on bus 2 0 = Module is not configured 1 = Module is configured 3-7 Reserved, set to 0 Refer to the Troubleshooting information in Chapter 4 for additional information on Recoverable and Uncoverable, Major
Explicit Messaging Application Examples B-7 The following correlates the CIP Generic message terminology with DeviceNet command terminology and illustrates the values needed specifically for the Get 1769 I/O Configuration Size message: Values (Hexadecimal) DeviceNet Terminology CIP Generic Terminology e Service Service Code 30c Class2 10 (decimal) Instance3 Object ID 17 Attribute Object Attribute 1 Object Type 4 1 Service specifies the type of request being delivered.
B-8 Explicit Messaging Application Examples The following screen is the Communications tab for the MSG instruction above. The reply to this message, when successful, will be one word of data containing the word length of the configuration file for the 1769 I/O module to which the message was sent. This data will be stored in the Logix5550 controller at the tag specified in the “Destination” field for the message instruction.
Explicit Messaging Application Examples B-9 The following correlates the CIP Generic message terminology with DeviceNet command terminology and illustrates the values needed specifically for the Get 1769 I/O Configuration Size message: Values (Hexadecimal) DeviceNet Terminology CIP Generic Terminology 10 Service Service Code 30c Class2 10 (decimal) Instance3 Object ID 1a Attribute Object Attribute 8304 First word of the 1769-OF2 configuration file5 8304 Second word of the 1769-OF2 configu
B-10 Explicit Messaging Application Examples The following ladder logic program is an example of the MSG logic needed to initiate an explicit message to the scanner/adapter. This MSG instruction logic is specifically for the Set 1769 I/O Module Configuration message. Assume the 1756-DNB scanner is in slot 1 and the Logix5550 controller is in slot 0. The following screen is the Communications tab for the MSG instruction above. You only need to enter the path on this screen.
Explicit Messaging Application Examples B-11 Save 1769 I/O Module Configuration This command is extremely important when modifying the configuration of any 1769 I/O module in a 1769 I/O system. When a Set 1769 I/O Module Configuration message is sent to an I/O module with an explicit message and there are no errors, the module immediately begins using the new configuration parameters.
B-12 Explicit Messaging Application Examples The following ladder logic program is an example of the MSG logic needed to initiate an explicit message to the scanner/adapter. This MSG instruction logic is specifically for the Save 1769 I/O Module Configuration message. Assume the 1756-DNB scanner is in slot 1 and the Logix5550 controller is in slot 0. The following screen is the Communications tab for the MSG instruction above. You only need to enter the path on this screen.
Explicit Messaging Application Examples B-13 Get 1769 I/O Module Configuration This command allows you to get the specified I/O module’s configuration so that you may verify the configuration of any 1769 I/O module. The MSG instruction will read 8 configuration words from the 1769-OF2 module in this example. The first 6 words contain the configuration data for the module, while the last 2 words are always 0.
B-14 Explicit Messaging Application Examples The following ladder logic program is an example of the MSG logic needed to initiate an explicit message to the scanner/adapter. This MSG instruction logic is specifically for the Get 1769 I/O Module Configuration message. Assume the 1756-DNB scanner is in slot 1 and the Logix5550 controller is in slot 0. The following screen is the Communications tab for the MSG instruction above. You only need to enter the path on this screen.
Explicit Messaging Application Examples 1747-SDN Explicit Messaging Application Example B-15 The following explicit messaging application example details a 1747-SDN DeviceNet scanner controlling 1769 Compact I/O via DeviceNet and the 1769-ADN DeviceNet Adapter.
B-16 Explicit Messaging Application Examples Following each command reply, the user program must MOVe a command value of 4 hexadecimal to the appropriate M0 file word to clear the previous reply from its buffer, making it ready for the next command.
Explicit Messaging Application Examples B-17 The following ladder logic program is an example of the logic needed to initiate an explicit message to the scanner/adapter and how to obtain the reply. This logic is specifically for the Get 1769-ADN Status message. Assume the 1747-SDN scanner is in slot 3 of the processor chassis.
B-18 Explicit Messaging Application Examples The actual status word in the reply, i.e.
Explicit Messaging Application Examples B-19 The following illustrates the Get 1769 Module Status command and the command reply: Command (Hexadecimal) Description (High Byte/Low Byte) 0101 TXID1/Command2 0006 Port #3/Byte Count4 0E13 Service5/Mac ID6 030C Class7 00xx Instance8 000C Attribute9 Reply (Hexadecimal) Description (High Byte/Low Byte) 0101 TXID1/Status 0001 Port #3/Byte Count4 8E13 Service5/Mac ID6 xxxx Status Word from Adapter 1 TXID (Transmission ID) is used by the sca
B-20 Explicit Messaging Application Examples The following ladder logic program is an example of the logic needed to initiate an explicit message to the scanner/adapter/1769 I/O module and how to obtain the reply. This logic is specifically for the Get 1769 I/O Module Status command. Assume the 1747-SDN scanner is in slot 3 of the processor chassis and the 1769-OF2 module that we are reading status from is in slot 10 of the 1769-ADN remote system.
Explicit Messaging Application Examples B-21 The actual status word from the 1769 I/O module is the fourth word of the reply, is defined as follows: Bit Description 0 0 = No module error detected 1 = Module detected error present 1 0 = Communication on bus ok 1 = Communication fault on bus 2 0 = Module is not configured 1 = Module is configured 3-7 Reserved, set to 0 Publication 1769-UM001B-EN-P - October 2002
B-22 Explicit Messaging Application Examples Get 1769 I/O Module Configuration Size 1769 I/O modules should be configured in RSNetworx for DeviceNet when your DeviceNet system is configured. We’ll describe how to modify 1769 I/O module configuration parameters while the system is running. Modifying I/O module configuration parameters dynamically is not a common practice, but for some applications it may be necessary.
Explicit Messaging Application Examples B-23 Set 1769 I/O Module Configuration The length of this command is determined by the size of the configuration file for the 1769 I/O module we will configure. In this case, from the previous section, we read the configuration size for the 1769-OF2 as 8 words, the length of this command is 14 words.
B-24 Explicit Messaging Application Examples Error Reply (Hexadecimal) Description (High Byte/Low Byte) 0101 TXID1/Command2 0002 Port #3/Byte Count4 9413 Service5/Mac ID6 xxxx Bad Status for the Configuration Command 1 TXID (Transmission ID) is used by the scanner to track the transaction to completion and returns the same value with the reply. To properly track commands with their replies, this value should be incremented for each new command sent. TXID size is one byte.
Explicit Messaging Application Examples B-25 Should a configuration error occur, you will receive DeviceNet Error Codes. The error code is a two-byte field, where the low byte is the General Error Code and the high bit is the Additional Error Code. The following is a list of possible DeviceNet Error Codes: Error Code (Hexadecimal) Description of Error 00 Success Service was successfully performed by the object specified.
B-26 Explicit Messaging Application Examples Publication 1769-UM001B-EN-P - October 2002 Error Code (Hexadecimal) Description of Error 16 Object does not exist - The object specified does not exist in the device. 17 Reserved by DeviceNet 18 No stored attribute data - The attribute data of this object was not saved prior to the requested service. 19 Store operation failure - The attribute data of this object was not saved due to a failure during the attempt.
Explicit Messaging Application Examples B-27 If the Extended Error Code is FF hexadecimal, the responding object has no additional information to specify.
B-28 Explicit Messaging Application Examples The following table illustrates the Save 1769 I/O Module Configuration command and the command reply: Command (Hexadecimal) Description (High Byte/Low Byte) 0101 TXID1/Command2 0004 Port #3/Byte Count4 1613 Service5/Mac ID6 000F Class7 0000 Instance8 Reply (Hexadecimal) Description (High Byte/Low Byte) 0101 TXID1/Status 0000 Port #3/Byte Count4 9613 Service5/Mac ID6 1 TXID (Transmission ID) is used by the scanner to track the transaction to
Explicit Messaging Application Examples B-29 The following table illustrates the Get 1769 I/O Module Configuration command and the command reply: Command (Hexadecimal) Description (High Byte/Low Byte) 0101 TXID1/Command2 0006 Port #3/Byte Count4 0E13 Service5/Mac ID6 030C Class7 000A Instance8 001A Attribute9 Reply (Hexadecimal) Description (High Byte/Low Byte) 0101 TXID1/Status 0010 Port #3/Byte Count4 (10 hexadecimal = 16 decimal) 8E13 Service5/Mac ID6 8304 First word of the 1769-
B-30 Explicit Messaging Application Examples Ladder Logic Example Program The following ladder program is an example of the logic needed to initiate explicit messages to the scanner/adapter/1769 I/O modules and how to obtain the replies. Assume the 1747-SDN is in slot 3 and the 1769-OF2 module is in 0A hexadecimal (10 decimal). A copy of Data Table File N11 follows the ladder program to show the location of the commands.
Explicit Messaging Application Examples B-31 Data Table File N11 (Shown in Hexadecimal Radix) 0 1 2 3 4 5 6 7 8 9 N11:0 101 6 E13 30C A 17 0 0 0 0 N11:10 101 16 1013 30C A 1A 8304 8304 1862 1862 N11:20 1862 1862 0 0 0 0 0 0 0 0 N11:30 101 6 E13 30C A 1A 0 0 0 0 N11:40 4 0 0 0 0 101 4 1613 F 0 N11:50 101 2 8E13 8 0 0 0 0 0 0 The following configuration information applies to these modules: • 1769-OA8 • 1769-IQ6XOW4 • 1769-OB16 •
B-32 Explicit Messaging Application Examples Notes: Publication 1769-UM001B-EN-P - October 2002
Appendix C 1769-ADN Throughput Characteristics Read this appendix to learn about the 1769-ADN throughput characteristics. Series A Adapters About Adapter Throughput Characteristics The following calculations provide a baseline for a 2-node network, a scanner, and a 1769-ADN. These calculations do not incorporate the impact of additional nodes on the network.
C-2 1769-ADN Throughput Characteristics Note: The following equations represent the 1769-ADN turn-around time using a discrete input (1769-IQ16) and output (1769-OV16) pair wired in a loop-back fashion. For this configuration, the settling/filter time of the two modules is 8.6ms on average1. For other I/O modules, consult the appropriate product installation instructions to determine the appropriate filter times to use.
1769-ADN Throughput Characteristics Quick Connect Performance C-3 The Quick Connect performance depends on: • the start-up time of the power supplies in the adapter system. • the number of modules in the system. • the type of modules in the system. The typical time for adapter system to go from power applied to ready to accept an I/O connection request is from 1.4s to 3.0s. Use the following table as a guide when selecting your power supplies: Catalog Number Typical Startup Time (ms) 1769-PA2 621.
C-4 1769-ADN Throughput Characteristics Quick Connect Limitations The 1769-HSC is not compatible with the 1769 adapter’s Quick Connection operation. The 1769-HSC does not respond quickly enough to adapter requests after startup. In general, modules that require longer than 650ms after power is applied to respond to the adapter will not be compatible with the adapter’s Quick Connect mode of operation.
Appendix D Differences Between Series A and B DeviceNet Adapters About the Differences The following list details the differences/enhancements between DeviceNet Series A and B adapters: • Series B adapters (that have their Mac ID switches set to 64-99) support the recovery of nodes that fail the Dup Mac test via RSNetWorx Faulted Address Recovery Wizard. • Series B adapters, along with the new configuration applet within RSNetWorx (version 4.
D-2 Differences Between Series A and B DeviceNet Adapters Notes: Publication 1769-UM001B-EN-P - October 2002
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 it back to us, visit us online at www.ab.com/manuals, or email us at RADocumentComments@ra.rockwell.com Pub. Title/Type Compact™ I/O 1769-ADN DeviceNet Adapter Cat. No. 1769-ADN Pub. No. 1769-UM001B-EN-P Pub. Date October 2002 Part No. 957555-75 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.
Index Numerics 1747-SDN application example 6-1, B-1, B-15 configuring SLC system 6-1 hardware setup 6-1 A Adapter adding to network 3-1, 4-1 configuring 1-9 1769 bus 3-2, 4-2 description 1-1 grounding 1-7 input status word 2-2 mounting 1-4 panel 1-4 using modules as template 1-5 spacing 1-4 replacing 1-6 specifications A-1, A-2 general A-1, A-3 input/output A-2, A-5 Adapter, performance C-1 Adding adapter to network 3-1, 4-1 Analog input modules configuring 3-14, 4-17 Analog output modules configuring 3-1
2 D Defaults 2-24 Output Array 2-21 DeviceNet wiring 1-7 Diagnostic indicators 5-1 DIN rail mounting 1-6 Disable keying 3-22, 4-29 Discrete input modules configuring 3-9, 4-9 Discrete output modules configuring 3-11, 4-12 Documentation related 2 Download configurations 3-24, 4-31 E EDS 4-11, 4-15, 4-20, 4-24 Electrostatic discharge 1-2 End cap configuring 3-20, 4-25 error general error bit 2-22 invalid output bit 2-21 Exact Match 3-22, 4-29 Example configurations 3-8, 4-8 F Field wiring connections 1-7
3 M Mapping data into image table 2-4 Mapping summaries 3-20, 4-26 Match exact 3-22, 4-29 Memory,clear 3-25 Module description 1-1 installation 1-2 mounting 1-4 Modules analog input configuring 3-14, 4-17 analog output configuring 3-17, 4-21 configuring discrete input 3-9, 4-9 discrete output 3-11, 4-12 Mounting adapter and I/O module 1-4 Mounting adapter and I/O module DIN rail 1-6 panel 1-4 spacing 1-4 N Network adding adapter 3-1, 4-1 O OK 3-21, 4-28 Online features 3-21, 4-27 Output Off Mask 2-21 Out
4 W Wiring DeviceNet 1-7 field connections 1-7 Word input status 2-2 Publication 1769-UM001B-EN-P - October 2002
5 Publication 1769-UM001B-EN-P - October 2002
Back Cover Publication 1769-UM001B-EN-P - October 2002 1 Supersedes Publication 1769-UM001A-US-P - May 2000 PN 957555-75 Copyright © 2002 Rockwell Automation. All rights reserved. Printed in the U.S.A.
