User manual ALLEN-BRADLEY DEVICENET MODULES IN LOGIX5000 CONTROL SYSTEMS

[. . . ] DeviceNet Modules in Logix5000TM Control Systems 1734-ADN, 1734-ADNX, 1734-PDN, 1756-DNB, 1769-SDN, 1784-PCIDS, 1788-CN2DN, 1788-DNBO, 1788-EN2DN, 1794-ADN User Manual Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1. 1 available from your local Rockwell Automation sales office or online at http://www. ab. com/manuals/gi) describes some important differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable. In no event will Rockwell Automation, Inc. [. . . ] Type the class, instance, and attribute for the parameter. 4. Type the new value in hexadecimal format. 5. To read the parameter, choose Get Single Attribute. 6. To change how output data is displayed, select the size and format. Publication DNET-UM004A-EN-P - March 2004 7-16 Control a Device Enter Message Logic To access a parameter of a device (get or set the parameter), configure the MSG instruction as CIP Generic. Change the current limit of the drive To configure the MSG instruction: Step: Define the Source or Destination Data Enter and Configure the MSG Instruction Set the Communication Path See page: 7-17 7-18 7-19 Publication DNET-UM004A-EN-P - March 2004 Control a Device 7-17 Define the Source or Destination Data tag that controls the instruction · Scope ­ controller · Data type ­ MESSAGE · The tag cannot be part of an array or a user-defined data type. source or destination for the data that the instruction sets or gets · Scope ­ controller · Data type ­ In general, use the DINT data type, even when you set or get less than 4 bytes. · Value ­ Make sure the source value stays within the minimum and maximum values for the parameter that you are setting. number of bytes (only if setting a value) In general: · Use the DINT data type for the source or destination tag, even when you set or get less than 4 bytes. · Make sure the source value stays within the minimum and maximum values for the parameter that you are setting. When setting a value, the CIP Generic MSG instruction takes only the specified number of bits from the source tag. MySource_1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 For example, if Source Length = 1 byte, then the CIP Generic MSG instruction sends the first byte of MySource_1. Publication DNET-UM004A-EN-P - March 2004 7-18 Control a Device To increase the efficiency of your logic, minimize the use of SINT or INT data types. Whenever possible, use the DINT data type for integers. · A Logix5000 controller typically compares or manipulates values as 32-bit values (DINTs or REALs). · The controller typically converts a SINT or INT value to a DINT or REAL value before it uses the value. · If the destination is a SINT or INT tag, the controller typically converts the value back to a SINT or INT value. · The conversion to or from SINTs or INTs occurs automatically with no extra programming. But it takes extra execution time and memory. Enter and Configure the MSG Instruction 1. Enter the condition for the data transfer. Type the class, instance, and attribute for the parameter, in hex. 5. Type the class, instance, and attribute for the parameter, in hex. Publication DNET-UM004A-EN-P - March 2004 Control a Device 7-19 Set the Communication Path The communication path specifies the route to the device. A communication path follows this format: scanner_name, 2, device_address Where: scanner_name device_address Is: Name of the scanner in the I/O Configuration folder of the controller. Address of the device on the DeviceNet network. For example: If the name of the scanner is MyScanner and the device is at address 3, then the path is: MyScanner, 2, 3 To set the path: 1. Click the Browse button and select the scanner. Close the dialog box. Publication DNET-UM004A-EN-P - March 2004 7-20 Control a Device Typically, a CIP generic MSG instruction requires no connection to transfer its data. This type of message: CIP data table read or write PLC2, PLC3, PLC5, or SLC (all types) Using this communication method: CIP CIP CIP with Source ID DH+ CIP generic block-transfer read or write (1) Uses a connection: yes no no yes your choice(1) yes CIP na You can connect CIP generic messages, but for most applications we recommend you leave CIP generic messages unconnected. For more information on programming MSG instructions, see the Logix5000 Controller General Instructions Reference Manual, publication 1756-RM003. Publication DNET-UM004A-EN-P - March 2004 Chapter 8 Interlock and Share Inputs How to Use This Chapter The chapter describe how to interlock and share inputs over a DeviceNet network. DeviceNet network Interlocking Controller scanner A scanners (controllers) exchange data with each other Controller scanner B Sharing Inputs DeviceNet network device Controller scanner A input data goes to both scanners (controllers) Controller scanner B For this information: Interlock Share Inputs Page: 8-1 8-5 Interlock To set up an interlock between 2 controllers over a DeviceNet network: Step: Choose a Master Controller Determine How Much Data to Exchange Enable Slave Mode for the Slave Scanner Map the Slave Mode Data Add the Slave to the Scan List of the Master Map the Data of the Slave Place Both Scanners In Run Mode Page: 8-2 8-2 8-3 8-4 8-4 8-5 8-5 1 Publication DNET-UM004A-EN-P - March 2004 8-2 Interlock and Share Inputs Choose a Master Controller To interlock, choose a controller to serve as the master. The other controller/controllers become a slave/slaves to the master. [. . . ] Select the device and choose Advanced. 2. For the first map entry, specify the first bit of the data. Specify the first bit of the data for the next map entry for this device. Close when you are done. Publication DNET-UM004A-EN-P - March 2004 Index Numerics 1734 I/O module automatically address 15-7 LEDs 15-14 set address 15-5 1734-232ASC data map 15-31 1734-ADN assign address 15-4 configure 15-8 LEDs 15-14 set address 15-6 use 15-2 1734-ADNX assign address 15-4 configure 15-8 LEDs 15-14 set address 15-6 use 15-2 1734D LEDs 15-17 set address 15-6 1734-IA2 data map 15-19 1734-IB2 data map 15-19 1734-IB4 data map 15-19 1734-IE2C data map 15-23 1734-IE2V data map 15-24 1734-IJ data map 15-26 1734-IK data map 15-26 1734-IM2 data map 15-27 1734-IR2 data map 15-27 1734-IT2I data map 15-28 1734-IV2 data map 15-20 1734-IV4 data map 15-20 1734-OA2 data map 15-20 1734-OB2E data map 15-21, 15-22 1734-OB2Edata map 15-21 1734-OB2EP data map 15-21 1734-OB4E data map 15-21 1734-OE2C data map 15-25 1734-OE2V data map 15-25 1734-OV2E data map 15-22 1734-OV4E data map 15-22 1734-OW2 data map 15-23, 15-30 1734-OX2 data map 15-23 1734-PDN assign address 15-4 LEDs 15-13 set address 15-5 use 15-2 1734-SSI data map 15-30 1734-VHSC24 data map 15-29 1734-VHSC5 data map 15-30 1756-DNB I/O limits 1-11 LEDs 12-3 set address 5-4 use 1-5 1769-SDN I/O limits 1-11 LEDs 12-1 set address 5-4 use 1-5 1770-KFD configure driver 3-5 1784-PCC configure driver 3-4 1784-PCD configure driver 3-5 1784-PCIDS address data 7-9 data alignment 2-11, 6-12 I/O limits 1-11 LEDs 12-11 map data 1-12 memory organization 1-12 set address 5-10 use 1-5 1788-CN2DN I/O limits 1-11 LEDs 12-5 set address 5-5 use 1-5 1788-DNB I/O limits 1-11 use 1-5 1788-DNBO LEDs 12-7 set address 5-5 1788-EN2DN disable autobaud 5-6 I/O limits 1-11 LEDs 12-8 set address 5-6 set IP address 5-8 use 1-5 1794-ADN address on DeviceNet 14-3 configure offline 14-3 LEDs 14-5 set address 14-4 use 14-1 A Publication DNET-UM004A-EN-P - March 2004 2 Index address 1794-ADN 14-3 assign 1-13 assign for Point I/O 15-4 automatic recovery 13-1 device data 7-7 device replacement 13-1 options for setting 5-2 set via software 5-3 specify offline 2-6 ADR See automatic device recovery advanced mapping configure A-2 use A-1 alias tags use 7-10 alignment set option 2-11, 6-12 auto-address recovery use 13-1 autobaud use 1-9 automap alignment options 2-11, 6-12 use 2-12, 6-13 automatic device recovery configure 13-3 use 13-1 autoscan allocation size 4-12 enable 4-7 firmware requirements 4-1 overview 4-2 when to use 4-1 command register use 7-12 communication card select 3-2 communication error device state conflict 14-4, 15-13 computer connect to network 3-2 configuration recovery use 13-1 configure 1734-ADN 15-8 1734-ADNX 15-8 automatic device recovery 13-3 change of state 11-7 cyclic 11-7 device 2-5, 6-6 driver 3-3 I/O parameters 11-6 interscan delay 11-6 message 7-16 network offline 2-1 network online 6-1 poll 11-8 shared inputs 8-5 strobed 11-7 connect computer 3-2 ControlNet bridge options 1-6 configure 1784-PCC driver 3-4 COS See change of state cyclic configure 11-7 overview 11-3 B background poll use 11-3 baud rate cable limits 1-9 options for setting 1-9 set via software 5-3 bridge across networks 1-6, 3-2 D data maps 1734-232ASC 15-31 1734-IA2 15-19 1734-IB2 15-19 1734-IB4 15-19 1734-IE2C 15-23 1734-IE2V 15-24 1734-IJ 15-26 1734-IK 15-26 1734-IM2 15-27 1734-IR2 15-27 1734-IT2I 15-28 1734-IV2 15-20 1734-IV4 15-20 C change of state configure 11-7 overview 11-3 class instance editor use 7-15 Publication DNET-UM004A-EN-P - March 2004 Index 3 1734-OA2 15-20 1734-OB2E 15-21, 15-22 1734-OB2EP 15-21 1734-OB4E 15-21 1734-OE2C 15-25 1734-OE2V 15-25 1734-OV2E 15-22 1734-OV4E 15-22 1734-OW2 15-23, 15-30 1734-OX2 15-23 1734-SSI 15-30 1734-VHSC24 15-29 1734-VHSC5 15-30 default 15-18 DDE access parameter 10-1 device access via RSView software 10-1 add to scan list 2-13, 6-14 address data 7-7 advanced mapping A-1 assign memory location 2-14, 6-15 auto-address recovery 13-1 automate replacement 13-1 commission 5-3 configuration recovery 13-1 configure 2-5, 6-6 configure I/O parameters 11-6 configure offline 2-1 configure online 6-1 detect failure 7-11 download configuration 6-8 get or set parameter 7-15 get or set parameter via logic 7-13 I/O parameters 11-1, 11-3 set address via software 5-3 set baud rate via software 5-3 specify address offline 2-6 update options 11-3 upload configuration 6-7 device state conflict 14-4, 15-13 DeviceNet bridge options 1-6 cable limts 1-9 configure 1770-KFD driver 3-5 configure 1784-PCD driver 3-5 configure PanelView terminal 9-7 Flex I/O 14-1 run network 7-12 diagnostics detect failure of device 7-11 download device configuration 6-8 network configuration 2-17 scanner configuration 6-16 driver 1770-KFD 3-5 1784-PCC 3-4 1784-PCD 3-5 configure 3-3 EtherNet/IP 3-4 RS-232 3-4 E eds file interpret 7-14 error device state conflict 14-4, 15-13 error codes See status codes EtherNet/IP brigde options 1-6 configure driver 3-4 explicit client tags configure 9-19 explicit server tags access from controller 9-16 configure 9-15 plan 9-13 F Flex I/O on DeviceNet 14-1 scanner memory requirements 14-2 foreground to background poll ratio 11-3 G generate report 2-16, 6-17 I I/O data define for device 11-6 map specific value A-1 I/O memory advanced mapping A-1 assign devices 2-14, 6-15 assign slave mode data 8-4 assign slave scanner 8-5 autoscan 4-12 data alignment 2-11, 6-12 estimate 1-11 Publication DNET-UM004A-EN-P - March 2004 4 Index estimate for Flex I/O 14-2 estimate for Point I/O 15-3 limits 1-11 I/O parameters configure 11-6 options 11-3 overview 11-3 select for device 11-1 interlock set up 8-1 use 8-1 interscan delay configure 11-6 examples 11-2 overview 11-4 N network add devices to diagram 2-4 configuration file 2-3, 6-3 download configuration 2-17 go online 6-5 interscan delay 11-4 run 7-12 status information 12-13 tune 11-1 upload configuration 6-16 node See address node commissioning tool install 4-2 set address or baud rate 5-3 L LEDs 1734 I/O module 15-14 1734-ADN 15-14 1734-ADNX 15-14 1734D 15-17 1734-PDN 15-13 1756-DNB 12-3 1769-SDN 12-1 1784-PCIDS 12-11 1788-CN2DN 12-5 1788-DNBO 12-7 1788-EN2DN 12-8 1794-ADN 14-5 logic detect failed device O online go 6-5 OPC access parameter 10-1 P PanelView terminal add to scan list 9-9 address data 9-11 configure communication 9-7 configure explicit client tags 9-19 configure explicit server tags 9-15 configure I/O slave tags 9-4 explicit client overview 9-3 explicit server overview 9-3 plan explicit server tags 9-13 select communication method 9-2 send message 9-19 send message to 9-16 parameter determine class, instance, attribute numbers 7-14 path define for message 7-19 performance adjust 11-1 Point I/O on DeviceNet 15-2 scanner memory requirements 15-3 select adapter 15-2 PointBlock I/O as DeviceNet adapter 15-2 LEDs 15-17 7-11 M map advanced mapping A-1 device to memory 2-14, 6-15 message configure 7-16 path 7-19 send from PanelView terminal 9-19 send to PanelView terminal 9-16 use 7-13 mode scanner 7-12 MSG instruction See message multicast input data set up 8-5 use 8-1 Publication DNET-UM004A-EN-P - March 2004 Index 5 set address 15-6 poll change poll ratio 11-6 configure 11-8 overview 11-3 rate 11-3 ratio 11-3 R report generate 2-16, 6-17 RS-232 bridge options 1-6 configure driver 3-4 RSView software access device 10-1 S scan cycle examples 11-2 factors of performance 11-2 interscan delay 11-2, 11-4 scan list add shared input 8-6 add slave scanner 8-4 automap on add check box 2-12, 6-13 build 2-13, 6-14 build automatically 2-12, 6-13 I/O parameters 11-1, 11-3 overview 2-8, 6-9 set I/O parameters 11-6 scanner add PanelView terminal 9-9 add to project 7-5 adjust the status size 7-3 advanced mapping A-1 change interscan delay 11-6 change mode 7-12 change poll ratio 11-6 configure ADR 13-3 configure automatically 4-1 configure I/O parameters for device download configuration 6-16 enable auto-address recovery 13-6 enable slave mode 8-3 I/O maps 1-11 I/O memory 1-11 interscan delay 11-4 scan list 2-8, 6-9 select 1-5 slave mode 8-2 specify address offline 2-9 status information 12-13 upload configuration 6-10 select communication card 3-2 scanner 1-5 shared input add to scan list 8-6 use 8-1 slave mode enable for scanner 8-3 map data 8-4 use 8-2 SoftLogix5800 controller See 1784-PCIDS status adjust scanner status size 7-3 codes register 12-14 tags 12-13 status codes interpret 12-16 status register interpret 12-14 status tags interpret 12-15 use 12-13 strobed configure 11-7 overview 11-3 U upload device configuration 6-7 network 6-16 scanner configuration 6-10 11-6 configure offline 2-1 configure online 6-1 data alignment 2-11, 6-12 Publication DNET-UM004A-EN-P - March 2004 6 Index Publication DNET-UM004A-EN-P - March 2004 How Are We Doing? Your comments on our technical publications will help us serve you better in the future. [. . . ]