User manual

ManualsBrandsAllen-Bradley ManualsAdapter1734-ADN

DeviceNet

Modules in

Logix5000™

Control Systems

1734-ADN, 1734-ADNX, 1734-PDN,

1756-DNB, 1769-SDN, 1784-PCIDS,

1788-CN2DN, 1788-DNBO,

1788-EN2DN, 1794-ADN

User Manual

Summary of content (239 pages)

PAGE 1
DeviceNet Modules in Logix5000™ Control Systems 1734-ADN, 1734-ADNX, 1734-PDN, 1756-DNB, 1769-SDN, 1784-PCIDS, 1788-CN2DN, 1788-DNBO, 1788-EN2DN, 1794-ADN User Manual
PAGE 2
Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.ab.com/manuals/gi) describes some important differences between solid state equipment and hard-wired electromechanical devices.
PAGE 3
Preface About This Manual The manual is one of various Logix5000 manuals.
PAGE 4
Preface 2 Who Should Use this Manual This manual is for those who program or maintain industrial automation systems.
PAGE 5
Table of Contents Chapter 1 Before You Begin What This Manual Covers . . . . . . . . . . . . . . . . . Preliminary Actions . . . . . . . . . . . . . . . . . . . . . . Choose a Scanner . . . . . . . . . . . . . . . . . . . . . . . Bridging Across Networks . . . . . . . . . . . . . . . . . Choose a Baud Rate for the Network . . . . . . . . . If You Want to Use a Higher Baud Rate… . . Calculate Scanner Memory Requirements . . . . . . Check the I/O Limits of the Scanner . . . . . . .
PAGE 6
Table of Contents 2 Chapter 4 Automatically Configure a DeviceNet Network How To Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Determine If You Can Use AutoScan . . . . . . . . . . . . . . . . . 4-1 How AutoScan Effects Your Network. . . . . . . . . . . . . . . . . 4-2 Install the Node Commissioning Tool. . . . . . . . . . . . . . . . . 4-2 Connect Each Device to the Network. . . . . . . . . . . . . . . . . 4-3 Set the Address of a Scanner . . . . . . . . . . . . . . . . . . . .
PAGE 7
Table of Contents Upload the Current Configuration of the Scanner . . . Define the Properties of the Scanner. . . . . . . . . . . . . Set the Alignment Option . . . . . . . . . . . . . . . . . . . . . Clear or Set the Automap on Add Check Box . . . . . . Build the Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . Manually Assign Each Device to a Memory Location . Download the Configuration to the Scanner . . . . . . . Upload and Save the Network File. . . . . . . . . . . . . . . . .
PAGE 8
Table of Contents 4 Map the Input Data in the Second Scanner . . . . . . . . . . 8-7 Chapter 9 Communicate with a PanelView™ Using This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Choose Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Standard Terminal Choose an Communication Method . . . . . . . . . . . . . . . I/O Slave Communication . . . . . . . . . . . . . . . . . . . Explicit Server Communication . . . . . . . . . . . . . . . .
PAGE 9
Table of Contents Background Poll . . . . . . . . . . . . . . . . . . . . . . . . Interscan Delay . . . . . . . . . . . . . . . . . . . . . . . . . Change the Configuration of the Network . . . . . . . . Upload the Current Configuration of the Scanner Set the Interscan Delay and Poll Ratio. . . . . . . . . Set the I/O Parameters of a Device . . . . . . . . . . . Download the Configuration to the Scanner . . . . Save the Network File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
Table of Contents 6 Chapter 15 Using POINT™ I/O Modules on a DeviceNet Network Publication DNET-UM004A-EN-P - March 2004 How to Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . 15-1 Choose a Connecting Device . . . . . . . . . . . . . . . . . . . . . . . 15-2 Tally Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . 15-3 POINT I/O 1734-ADN or 1734-ADNX Adapter. . . . . . . . 15-3 POINT I/O 1734-PDN Interface . . . . . . . . . . . . . . . . . .
PAGE 11
Table of Contents 1734-IK Encoder/Counter Module. . . . . . . . . . . . 1734-IM2 Input Module . . . . . . . . . . . . . . . . . . . 1734-IR2 RTD Input Module . . . . . . . . . . . . . . . . 1734-IT2I Isolated Thermocouple Input Module . 1734-VHSC 24V dc High Speed Counter Module . 1734-VHSC 5V dc High Speed Counter Module . . 1734-SSI Synchronous Serial Interface Absolute Encoder Module . . . . . . . . . . . . . . . . . . . . . . . . 1734-232ASC ASCII Module . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
Table of Contents 8 Publication DNET-UM004A-EN-P - March 2004
PAGE 13
Chapter 1 Before You Begin What This Manual Covers This manual guides the development of a control system that uses a Logix5000™ controller and a DeviceNet™ network.
PAGE 14
1-2 Before You Begin This manual also provides a basic level of information to use the following devices on your DeviceNet network.
PAGE 15
Before You Begin Preliminary Actions 1-3 Before you configure and program your DeviceNet network, complete the following actions: ❑ 1. Choose whether to use a single network or several distributed networks. (For more information, see page 1-5.) ❑ single network controller scanner device device device device device ❑ several smaller distributed networks (subnets) linking device controller device device linking device device device device device ❑ 2. Choose a scanner.
PAGE 16
1-4 Before You Begin ❑ 5. Calculate how much scanner memory you need. (For more information, see page 1-11.) A. List the devices on your network. Device B. Record how many bytes each device sends to your control system (input data) and gets from your control system (output data).
PAGE 17
Before You Begin Choose a Scanner 1-5 The DeviceNet scanner connects a controller to the devices on a DeviceNet network. The scanner collects input data from the devices on the network… scanner module …and sends the data to the controller. controller Input Memory DINT DINT controller data DINT device device device Output Memory DINT DINT …and sends the data to the devices.
PAGE 18
1-6 Before You Begin To choose a scanner, use the following table: If you are using: And: Use this scanner: single network CompactLogix™ controller CompactLogix 1769-SDN ControlLogix® controller ControlLogix 1756-DNB DriveLogix™ controller DriveLogix and FlexLogix 1788-DNBO FlexLogix™ controller subnets Bridging Across Networks SoftLogix™ 5800 controller SoftLogix5800 1784-PCIDS EtherNet/IP main network EtherNet/IP to DeviceNet Linking Device 1788-EN2DN ControlNet main network ControlNet
PAGE 19
Before You Begin 1-7 Communication can bridge these networks:.
PAGE 20
1-8 Before You Begin This example RSLinx window shows how the DeviceNet bridge links to the EtherNet/IP network: EtherNet/IP network EtherNet/IP bridge in 1756 system DeviceNet bridge in same 1756 system DeviceNet network distributed DeviceNet devices Publication DNET-UM004A-EN-P - March 2004
PAGE 21
Before You Begin Choose a Baud Rate for the Network 1-9 The default baud rate for a DeviceNet network is 125K bits/s. This is the easiest baud rate to use and is usually sufficient. The 2 most common methods to set the baud rate of a device are: Method: Description: autobaud feature At power up, the device automatically sets its baud rate to the baud rate of the first device it hears on the network. It remains set until the device powers up again.
PAGE 22
1-10 Before You Begin If You Want to Use a Higher Baud Rate… The length of the trunkline and type of cable determines which baud rates you can use: Baud rate Maximum distance Cumulative drop line length flat cable thick cable thin cable 125K bit/s 420m (1378 ft) 500m (1640 ft) 100m (328 ft) 156 m (512 ft) 250K bit/s 200m (656 ft) 250m (820 ft) 100m (328 ft) 78m (256 ft) 500K bit/s 75m (246 ft) 100m (328 ft) 100m (328 ft) 39m (128 ft) If you change the baud rate of your network, make s
PAGE 23
Before You Begin Calculate Scanner Memory Requirements A Logix5000 scanner has fixed sections of memory for the input and output data of your network. Each device on your network requires either some input or output memory of the scanner. Some devices both send and receive data, so they need both input and output memory. The memory of a Logix5000 scanner is organized as an array of DINTs (4-byte elements).
PAGE 24
1-12 Before You Begin If You Are Using a SoftLogix5800 Controller The 1784-PCIDS scanner organizes its input and output memory in 16-bit increments. When you access the data in the controller, the data is packed into 32-bit increments (DINTs). Scanner Input Memory Controller Input Data 16 bits 16 bits 16 bits Scanner Output Memory Controller Output Data 16 bits 16 bits 16 bits A Logix5000 system is easier to program if you give each device its own DINT or DINTs within the controller.
PAGE 25
Before You Begin Assign an Address to Each Device 1-13 To communicate on the DeviceNet network, each device requires its own address. In general, a device can use any address between 0 to 63. However, we recommend that you follow these guidelines: Give this device: This address: Notes: scanner 0 If you have multiple scanners, give them the lowest addresses is sequence (0, 1…).
PAGE 26
1-14 Before You Begin Here’s an example: 1. Give address 0 to the scanner. 2. Give the lower addresses to devices with 15 bytes or more of input or output data. 3. Gaps in addresses are OK.
PAGE 27
Chapter 2 Configure Your Network Offline How to Use This Chapter To configure your DeviceNet network, you have the following options: If: Then configure your network: See: Any of the following conditions apply: offline This chapter online Chapter 6 • The network and devices are not yet installed. • You do not have access to the network. (I.e., You are off-site.) • You prefer to do most of the configuration before you get on-site with the network.
PAGE 28
2-2 Configure Your Network Offline To configure a DeviceNet network while offline: Before You Begin Step: Page: ❑ Before You Begin 2-2 ❑ Create a File for the Network 2-3 ❑ Draw Your Network 2-4 ❑ Configure Each Device 2-5 ❑ Configure the Scanner 2-8 ❑ Save the Network File 2-15 ❑ Generate an RSNetWorx Report 2-16 ❑ Download the Configuration to Network 2-17 Before you configure the network, make sure you have a list of the devices that you are putting on your network and the address f
PAGE 29
Configure Your Network Offline Create a File for the Network 2-3 RSNetWorx software stores information about the configuration of each device in a file on your computer. Step: See page: ❑ Create a DeviceNet Configuration File 2-3 ❑ Give the File a Descriptive Name 2-3 Create a DeviceNet Configuration File 1. Start RSNetWorx software. 2. Create a file. 3. Select DeviceNet Configuration. 4. Choose OK.
PAGE 30
2-4 Configure Your Network Offline Draw Your Network To configure a DeviceNet network, you use RSNetWorx software to build a graphical picture of your network. To build a graphical picture of your network, complete the following steps for each of your devices: graphical picture of your network 1. Browse the hardware list for the device. 2. If there is a [+] sign next to the device, click the [+] sign. 3. Double-click the major revision of the device.
PAGE 31
Configure Your Network Offline Configure Each Device 2-5 Typically, a DeviceNet device has a set of parameters that define the behavior of the device.
PAGE 32
2-6 Configure Your Network Offline Specify the Address of the Device When you are offline, the address on the diagram identifies a device. It does not set the device to that address. In chapter 5, you will set the address of each device. 1. Double-click the device. 2. Type or select the DeviceNet address for the device.
PAGE 33
Configure Your Network Offline 2-7 Configure the Parameters of the Device 1. Click the Parameters tab. 2. Set a parameter to the required value: • Select a new value. – or – • Click, type a new value, and press [Enter]. 3. Close the dialog box.
PAGE 34
2-8 Configure Your Network Offline Configure the Scanner To configure the scanner to communicate with the devices on your network, you set up a scan list in the scanner. Then you define memory locations for the data of each device. scan list – A list in the scanner that identifies the devices with which the scanner communicates. For each device in its scan list, the scanner sets aside input and/or output memory for the data of the device.
PAGE 35
Configure Your Network Offline 2-9 Specify the Address of the Scanner 1. Double-click the scanner. 2. Type or select the DeviceNet address for the scanner.
PAGE 36
2-10 Configure Your Network Offline Define the Properties of the Scanner 1. Click the Module tab 2. If this is a CompactLogix scanner (1769-SDN), choose CompactLogix. 3. If the scanner uses a slot number, type its slot number.
PAGE 37
Configure Your Network Offline 2-11 Set the Alignment Option TIP The alignment option you choose applies to both the input and output maps. 1. Click the Input tab. 2. Choose Options. 3. Choose DWord Align. If You Have a SoftLogix5800 Controller The SoftLogix5800 scanner 1784-PCIDS organizes its input and output memory in 16-bit words. For that scanner, choose Word Align.
PAGE 38
2-12 Configure Your Network Offline Clear or Set the Automap on Add Check Box As an option, RSNetWorx software can automatically assign the memory location for each device. Depending on how you want to organize the memory, you may or may not want to use this option. If you want to: Then: 1. Click the Scanlist tab leave gaps between devices Memory device at address 1 device at address 2 device at address 3 2.
PAGE 39
Configure Your Network Offline 2-13 Build the Scan List 1. You should be at the Scanlist tab 2. Add devices to the scan list. To add: Do this: devices one at a Select a device and click the > time button. all the devices at once Click the >> button. If you get the following warning for a device, see Set the I/O Parameters of a Device on page 11-6.
PAGE 40
2-14 Configure Your Network Offline Manually Assign Each Device to a Memory Location IMPORTANT If you used Automap on Add (page 2-12).as you built your scan list, then skip this section. Each device already has a memory location. 1. Click the Input tab. 2. Select the device. 3. Type the element number to which you want to assign the data. This is the starting point for the data. Larger data sizes wrap to several elements. For example, to start the data in …Data[3], type 3 in the Start DWord box. 4.
PAGE 41
Configure Your Network Offline 2-15 Close the Configuration of the Scanner Close the dialog box. Save the Network File After you configure each device on your network, including the scanner, save the file. Save the file.
PAGE 42
2-16 Configure Your Network Offline Generate an RSNetWorx Report An RSNetWorx report shows the following: • devices on your network • memory addresses of those devices in the scanner • configuration of each device The report is a very useful reference when you program your system. 1. File ⇒ Generate Report. 2. Entire network The report shows up as an HTML file.
PAGE 43
Configure Your Network Offline Download the Configuration to Network 2-17 After you configure the network offline, you must download the configuration to the network. Do this after the network and devices are installed and you have access to the network.
PAGE 44
2-18 Configure Your Network Offline Go Online to the Network When you go online to a DeviceNet network, RSNetWorx software looks at the network (browses) one time and shows you the devices on the network. • It does not read (upload) or change (download) the parameters of any of the devices. • The picture you see remains static. It does not show any changes since the last browse. 1. Go online. 2. Browse to the DeviceNet network. 3. Choose OK.
PAGE 45
Configure Your Network Offline 2-19 Download the Configuration to the Network IMPORTANT Make sure the scanner is in idle mode. To put the scanner in idle mode, either: • Turn off the …O.CommandRegister.Run bit of the scanner. - or • Place the controller in program/remote program mode. 1. Network ⇒ Download to Network. 2. Yes, download the entire network.
PAGE 46
2-20 Configure Your Network Offline Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 47
Chapter 3 Connect a Computer to the System How to Use This Chapter This chapter shows how to connect a computer to your system so you can: • configure the devices on the network • configure network parameters • upload, download, monitor, and program projects for Logix5000 controllers Some networks let you browse (bridge) to other networks in your system. This lets you connect to one network and access devices or controllers on other networks.
PAGE 48
3-2 Connect a Computer to the System Connect a Computer to a Network IMPORTANT To access a network, either: • connect directly to the network • connect to a different network and browse (bridge) to the desired network. This requires no additional programming.
PAGE 49
Connect a Computer to the System 3-3 Once you choose a network to which to connect: • Install the communication card, if required. • Determine any network parameters for the computer, such as a network address. • Connect the computer to the network with the correct cable. Configure a Driver for a Network To communicate over a specific network, configure a driver for the network. Add the Driver 1. Start RSLinx software. 2. Click the Configure Driver button. 3.
PAGE 50
3-4 Connect a Computer to the System RS-232 DF1 Devices Important: Make sure no other driver is configured for the COM port to which you connect the serial cable. 1. Choose the following: COM port that you are using. Logix 5550/CompactLogix. Auto-Configure 5. Wait for the auto-configuration to finish. Ethernet Devices Enter the IP address of the controller or communication module. 1784-PCC Use the address that the software picks. Or assign a specific address: A. Clear this check box. B.
PAGE 51
Connect a Computer to the System 3-5 1784-PCD 1. Use the default address of 62, if it is unused. 2. Select the baud rate for the network. 3. OK. 1770-KFD Important: Make sure no other driver is configured for the COM port to which you connect the serial cable. 1. Select the COM port to which you connected the 1770-KFD device. 2. Use the default address of 62, if it is unused. 3. Select the baud rate for the network. 4. OK.
PAGE 52
3-6 Connect a Computer to the System Make Sure the Driver Works 1. Check that the driver is running. 2. Close the dialog box. 3. Open the RSWho window. 4. Double-click the driver to see the network.
PAGE 53
Chapter 4 Automatically Configure a DeviceNet Network How To Use This Chapter Before you use this chapter: Connect your computer to the system. See chapter 4. Determine If You Can Use AutoScan This chapter provides a quick method for configuring a DeviceNet network. It uses the AutoScan feature to establish communication between the controller and your devices with minimal steps.
PAGE 54
4-2 Automatically Configure a DeviceNet Network How AutoScan Effects Your Network Consideration: As you use AutoScan, keep the following in mind: Description: 1. AutoScan clears the current configuration. With AutoScan, the scanner automatically sets up communication with the devices on your DeviceNet network. When you turn on the AutoScan option, the scanner removes any previous configuration that was done to the scanner. 2. AutoScan allocates a fixed memory size for each device.
PAGE 55
Automatically Configure a DeviceNet Network Connect Each Device to the Network Step: ❑ ❑ 4-3 As you connect your devices to the DeviceNet network, follow these guidelines: Details: 1. Assign an address to each device. 2. Connect the scanner and any network interface to the network.
PAGE 56
4-4 Automatically Configure a DeviceNet Network Set the Address of a Scanner ControlLogix Scanner 1756-DNB DeviceNet TM MOD/NET I/O OK 1. Connect the device to the network. (If disconnected or the network power is off, the pushbutton changes the baud rate.) 2. Turn on the power to the device. 3. Press and hold the manual configuration pushbutton until the device displays the desired address. When you release the button, the device resets to the new address. 4.
PAGE 57
Automatically Configure a DeviceNet Network 4-5 Set the Address and Baud Rate of a Device Via Software 1. Start the Node Commissioning tool. 2. Click Browse. 3. Check this box. 4. Browse to the DeviceNet network. 5. Type the current address for the device. Out of the box, a device uses address 63. 6. Click OK. 7. Type the new address for the device. 8. Select the baud rate for the device. 9. Apply the change. 10. Look for confirmation here.
PAGE 58
4-6 Automatically Configure a DeviceNet Network Add the Scanner to the RSLogix 5000 Project To access the data of your network, add the scanner to the I/O configuration of the controller. To add a scanner: Step: See page: ❑ Add the Scanner to the I/O Configuration Folder 4-6 ❑ Define the Properties of the Scanner 4-7 Add the Scanner to the I/O Configuration Folder 1. Right-click and choose New Module. 2. Choose the type of scanner. 3. Select the major revision of the scanner.
PAGE 59
Automatically Configure a DeviceNet Network 4-7 Define the Properties of the Scanner 1. Type a name for the scanner. 2. Type or select the slot number of the scanner. 3. Choose Finish. Turn On AutoScan To turn on AutoScan: Step: See page: ❑ Download the RSLogix 5000 Project and Go Online 4-7 ❑ Turn On AutoScan 4-8 Download the RSLogix 5000 Project and Go Online 1. Save your changes. 2. Download the project to the controller.
PAGE 60
4-8 Automatically Configure a DeviceNet Network Turn On AutoScan IMPORTANT In the following steps, you clear any existing configuration from the scanner and reconfigure its to communicate with the devices on your network. • In the controller, this may change the tag addresses of the devices. • If you have already programmed your logic, make sure that it still addresses the correct data. 1. Double-click the scanner. 2. Click the Scan List tab. 3. Select (check) this check box. 4. Choose OK.
PAGE 61
Automatically Configure a DeviceNet Network Access Device Data 4-9 When you add the scanner to the I/O configuration of the controller, RSLogix 5000 software automatically creates a set of tags for the input, output, and status data of the network: input data from the scanner output data for the scanner status data from the scanner The tags for your DeviceNet data follow this format: location :type .Data [dnet_address] .
PAGE 62
4-10 Automatically Configure a DeviceNet Network While you can use the input and output tags of the scanner directly in your logic, it is a lot easier to use alias tags. alias tag – a tag that represents another tag • Both tags share the same data. • When the data changes, both tags change. • An alias tag provides a descriptive name for data, such as DeviceNet input or output data. As an option, create tags that describe each device without pointing them to the actual addresses of the devices.
PAGE 63
Automatically Configure a DeviceNet Network Put the Scanner in Run Mode 4-11 To run the DeviceNet network: 1. Place the controller in run/remote run mode. 2. Set the following bit of the output structure for the scanner: To put the scanner in run mode, turn on this bit. If you want to: The set this bit: To: run the network …O.CommandRegister.Run 1 not run the network (idle mode) …O.CommandRegister.Run 0 fault the network …O.CommandRegister.Fault 1 not fault the network …O.CommandRegister.
PAGE 64
4-12 Automatically Configure a DeviceNet Network Additional Information About AutoScan Type of Connection that the Scanner Sets Up The type of update (connection) that the scanner sets up with each device depends on the device. The scanner chooses the first connection type that the device supports in this order: 1. change-of-state (COS) 2. polled 3. strobed 4. cyclic at 1000 ms The scanner tries to set up a change-of-state connection.
PAGE 65
Automatically Configure a DeviceNet Network Consideration: 4-13 Description: 1. The bytes/node value defines how much memory for each address. AutoScan lets you specify how much input and output memory to give to each address on your network. DINT For example, if you specify 2 DINTs (8 bytes) per address, the scanner sets aside 2 DINTs for each address. 0 device at address 0 1 2 The actual data for the device fills the portion that it needs and the rest remains unused.
PAGE 66
4-14 Automatically Configure a DeviceNet Network Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 67
Chapter 5 Connect Each Device to the Network Using This Chapter Before You Begin This chapter describes how to set the address of a device so it can communicate on your DeviceNet network.
PAGE 68
5-2 Connect Each Device to the Network Set the Address of a Device A DeviceNet device uses at least one of the following methods to set its address on the network: Method: Description: switches If a device has switches or another hardware mechanism to set its network address, use that mechanism. Keep in mind that a device typically reads the switches on power up. If you change the address, you usually have to cycle power to the device.
PAGE 69
Connect Each Device to the Network Set an Address with Software 5-3 To use RSNetWorx software to set the address of a device: 1. Choose Start ⇒ Programs ⇒ Rockwell Software ⇒ RSNetWorx ⇒ DeviceNet Node Commissioning Tool. 2. Click Browse. 3. Check this box. 4. Browse to the DeviceNet network. 5. Type the current address for the device. Out of the box, a device uses address 63. 6. Click OK. 7. Type the new address for the device. 8. Apply the change. 9. Look for confirmation here.
PAGE 70
5-4 Connect Each Device to the Network Procedures for Specific Devices The following sections show how to set the address of specific devices. For this device: See page: ControlLogix Scanner 1756-DNB 5-4 CompactLogix Scanner 1769-SDN 5-4 ControlNet to DeviceNet Linking Device 1788-CN2DN 5-5 DriveLogix and FlexLogix Scanner 1788-DNBO 5-5 EtherNet/IP to DeviceNet Linking Device 1788-EN2DN 5-6 SoftLogix5800 Scanner 1784-PCIDS 5-10 ControlLogix Scanner 1756-DNB DeviceNet TM MOD/NET I/O 1.
PAGE 71
Connect Each Device to the Network 5-5 ControlNet to DeviceNet Linking Device 1788-CN2DN 1. Set the DeviceNet address. (Switches shown set to node 26) 2 Do not use the PGM area. 2 4 4 0 0 PGM 6 6 8 MSD LSD 2. Set the ControlNet address. (Switches shown set to node 14) 2 4 8 6 2 4 8 6 0 0 MSD LSD 3. Connect the device to the DeviceNet and ControlNet networks. 4. Turn on power to the device. 5. Check the DeviceNet network status light.
PAGE 72
5-6 Connect Each Device to the Network EtherNet/IP to DeviceNet Linking Device 1788-EN2DN Set the DeviceNet Address The 1788-EN2DN device has no hardware mechanism to set its DeviceNet address. 1. Connect the device to the network. 2. Turn on the power to the device. 3. Use RSNetWorx software to set the address of the device. See Set an Address with Software on page 5-3. 4.
PAGE 73
Connect Each Device to the Network 5-7 Disable AutoBaud 1. Right-click the device and choose Class Instance Editor. 2. Select Set Single Attribute. 3. Type the object address: Class = 3 Instance = 1 Attribute = 64 4. Select Byte. 5. Type a value of 01. 6. Choose Execute. 7. Check that the execution was completed.
PAGE 74
5-8 Connect Each Device to the Network Set the IP Address with BootP/DHCP 7 8 2 6 3 5 4 4 5 3 6 2 7 1 ON 8 If the DIP switch = 0 (default), BootP/DHCP is enabled for the device. On power up, the device requests an IP address from a BootP/DHCP server. 1 ON 31421-M RSLinx software includes a BootP/DHCP server that lets you easily assign an IP configuration to an EtherNet/IP device such as the linking device. 1. Get the ethernet (MAC) address of the device.
PAGE 75
Connect Each Device to the Network 5-9 Turn Off BootP/DHCP If you leave BootP/DHCP enabled for the device, its IP configuration lasts only until the next power cycle. After the next power up, the device sends out a new request for an IP address from a BootP/DHCP server. To permanently assign the configuration to the device, disable BootP/DHCP. 1. Select the device. 2. Disable BootP/DHCP. 3. Check that the command was successful.
PAGE 76
5-10 Connect Each Device to the Network Optional—Set the IP Address with the Configuration DIP Switch The DIP switch on the end of the linking device lets you set the device to the following IP configuration. 7 8 2 6 3 5 4 4 5 3 6 2 7 1 ON 8 IP address 192.168.1.n where: n is the value of the DIP switch Subnet mask 255.255.255.0 Gateway address 0.0.0.0 (No gateway set) 1 ON 31421-M IMPORTANT The numbers on the switch are opposite the address value bit locations; i.e.
PAGE 77
Connect Each Device to the Network Make Sure Your Devices Are on the Network 5-11 Once you have assigned an address to each device, make sure that the devices are communicating on the network. 1. Start RSLinx software. 2. Click the RSWho button. 3. Expand a driver that lets you access the DeviceNet network. 4. Browse to the DeviceNet network. 5. Make sure you see all the devices that are connected to the DeviceNet network.
PAGE 78
5-12 Connect Each Device to the Network Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 79
Chapter 6 Configure Your Network Online How to Use This Chapter To configure your DeviceNet network, you have the following options: If: Then configure your network: See: Any of the following conditions apply: offline Chapter 2 online This chapter • The network and devices are not yet installed. • You do not have access to the network. (I.e., You are off-site.) • You prefer to do most of the configuration before you get on-site with the network.
PAGE 80
6-2 Configure Your Network Online To configure a DeviceNet network while online: Before You Begin Step: Page: ❑ Before You Begin 6-2 ❑ Create a File for the Network 6-3 ❑ Go Online to the Network 6-5 ❑ Configure Each Device 6-6 ❑ Configure the Scanner 6-9 ❑ Upload and Save the Network File 6-16 ❑ Generate an RSNetWorx Report 6-17 Before you configure the network, make sure you have a list of the devices that you are putting on your network and the address for each of them.
PAGE 81
Configure Your Network Online 6-3 To make sure that you can communicate with all your devices, use RSLinx software to show your DeviceNet network. 1. Start RSLinx software. 2. Click the RSWho button. 3. Expand a driver that lets you access the DeviceNet network. 4. Browse to the DeviceNet network. 5. Make sure you see all the devices that are connected to the DeviceNet network.
PAGE 82
6-4 Configure Your Network Online Create a DeviceNet Configuration File 1. Start RSNetWorx software. 2. Create a file. 3. Select DeviceNet Configuration. 4. Choose OK. Give the File a Descriptive Name Since the file stores the configuration of the network, give it a name that identifies this specific DeviceNet network. Save the file. As you work in RSNetWorx software, periodically save your changes to the file for the network.
PAGE 83
Configure Your Network Online Go Online to the Network 6-5 When you go online to a DeviceNet network, RSNetWorx software looks at the network (browses) one time and shows you the devices on the network. • It does not read (upload) or change (download) the parameters of any of the devices. • The picture you see remains static. It does not show any changes since the last browse. 1. Go online. 2. Browse to the DeviceNet network. 3. Choose OK.
PAGE 84
6-6 Configure Your Network Online Configure Each Device Typically, a DeviceNet device has a set of parameters that define the behavior of the device.
PAGE 85
Configure Your Network Online 6-7 Upload the Configuration of a Device 1. Double-click the device. 2. Click the Parameters tab. 3. Upload the configuration from the device.
PAGE 86
6-8 Configure Your Network Online Change and Download Parameters 1. Change a parameter: • Select a new value. – or – • Click, type a new value, and press [Enter]. 2. Apply the changes. 3. Download the changes. 4. Close the dialog box.
PAGE 87
Configure Your Network Online Configure the Scanner 6-9 To configure the scanner to communicate with the devices on your network, you set up a scan list in the scanner. Then you define memory locations for the data of each device. scan list – A list in the scanner that identifies the devices with which the scanner communicates. For each device in its scan list, the scanner sets aside input and/or output memory for the data of the device.
PAGE 88
6-10 Configure Your Network Online Upload the Current Configuration of the Scanner 1. Double-click the scanner. 2. Click the Module tab. 3. Upload the configuration from the scanner.
PAGE 89
Configure Your Network Online 6-11 Define the Properties of the Scanner 1. Click the Module tab 2. If this is a CompactLogix scanner (1769-SDN), choose CompactLogix. 3. If the scanner uses a slot number, type its slot number.
PAGE 90
6-12 Configure Your Network Online Set the Alignment Option TIP The alignment option you choose applies to both the input and output maps. 1. Click the Input tab. 2. Choose Options. 3. Choose DWord Align. If You Have a SoftLogix5800 Controller The SoftLogix5800 scanner 1784-PCIDS organizes its input and output memory in 16-bit words. For that scanner, choose Word Align.
PAGE 91
Configure Your Network Online 6-13 Clear or Set the Automap on Add Check Box As an option, RSNetWorx software can automatically assign the memory location for each device. Depending on how you want to organize the memory, you may or may not want to use this option. If you want to: Then: 1. Click the Scanlist tab leave gaps between devices Memory device at address 1 device at address 2 device at address 3 2.
PAGE 92
6-14 Configure Your Network Online Build the Scan List 1. You should be at the Scanlist tab 2. Add devices to the scan list. To add: Do this: devices one at a Select a device and click the > time button. all the devices at once Click the >> button. If you get the following warning for a device, see Set the I/O Parameters of a Device on page 11-6.
PAGE 93
Configure Your Network Online 6-15 Manually Assign Each Device to a Memory Location IMPORTANT If you used Automap on Add (page 6-13).as you built your scan list, then skip this section. Each device already has a memory location. 1. Click the Input tab. 2. Select the device. 3. Type the element number to which you want to assign the data. This is the starting point for the data. Larger data sizes wrap to several elements. For example, to start the data in …Data[3], type 3 in the Start DWord box. 4.
PAGE 94
6-16 Configure Your Network Online Download the Configuration to the Scanner Important: Make sure the scanner is in idle mode. To put the scanner in idle mode, either: • Turn off the …O.CommandRegister.Run bit of the scanner. - or • Place the controller in program/remote program mode. 1. Apply the changes, 2. Yes, download. 3. Close the dialog box. Upload and Save the Network File 1. Network ⇒ Upload from Network. 2. Yes, upload the entire network. 3. Save the file.
PAGE 95
Configure Your Network Online Generate an RSNetWorx Report 6-17 An RSNetWorx report shows the following: • devices on your network • memory addresses of those devices in the scanner • configuration of each device The report is a very useful reference when you program your system. 1. File ⇒ Generate Report. 2. Entire network The report shows up as an HTML file.
PAGE 96
6-18 Configure Your Network Online Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 97
Chapter 7 Control a Device How to Use This Chapter 1 Use this chapter to develop the logic that examines and controls your devices.
PAGE 98
7-2 Control a Device Before You Use This Chapter Before you use this chapter, get the following information: RSNetWorx Report for Your Network Data Map for Each of Your Devices Publication DNET-UM004A-EN-P - March 2004
PAGE 99
Control a Device Add the Scanner to the I/O Configuration of the Controller 7-3 To access the data of your network, add the scanner to the I/O configuration of the controller.
PAGE 100
7-4 Control a Device Table 7.1 Set the status size for a scanner If you want this information: count of I/O scans Set the Status Which gives you: Size to (DINTs): Member: ScanCounter DINT indication that a device has failed: • There is 1 bit for each address on the DeviceNet network (0 -63). • The position of a bit = address of a device. • If a bit = 1, then the device at that address has failed.
PAGE 101
Control a Device 7-5 Add the Scanner to the I/O Configuration Folder CompactLogix scanner ControlLogix, FlexLogix, and SoftLogix5800 scanners 1. Right-click and choose New Module. EtherNet/IP to DeviceNet linking device ControlNet to DeviceNet linking device 2. Choose the type of scanner. 3. Select the major revision of the scanner.
PAGE 102
7-6 Control a Device Define the Properties of the Scanner 1. Specify the general properties (name, slot, sizes, etc.). 2. Choose Next. 3. Choose Next. 4. Choose Browse and find the RSNetWorx configuration file for the network (.dnt file). The default path for the file is …\Program Files\Rockwell Software\RSNetWorxII\Networks. 5. Choose Finish.
PAGE 103
Control a Device Determine the Address of DeviceNet Data 7-7 When you add the scanner to the I/O configuration of the controller, RSLogix 5000 software automatically creates a set of tags for the input, output, and status data of the network: input data from the scanner output data for the scanner status data from the scanner The tags for your DeviceNet data follow this format: The scanner memory uses this format: slot type .Data [element] Which is this tag in the controller .
PAGE 104
7-8 Control a Device To determine the tag name (address) for DeviceNet data: 1. On the report for the network, find the memory address for the input or output data of the device. 2. Find the corresponding tag in the controller-scoped tags of the controller. 3. Find the required data within the controller tag. Use the data map for the device as a reference. Local:2:I.
PAGE 105
Control a Device 7-9 If You Have a SoftLogix5800 Controller The SoftLogix5800 scanner 1784-PCIDS organizes input and output memory in 16-bit words. It uses the following address format: word.
PAGE 106
7-10 Control a Device Program Your Logic With Alias Tags While you can use the input and output tags of the scanner directly in your logic, it is a lot easier to use alias tags. alias tag – a tag that represents another tag • Both tags share the same data. • When the data changes, both tags change. • An alias tag provides a descriptive name for data, such as DeviceNet input or output data. As an option, create tags that describe each device without pointing them to the actual addresses of the devices.
PAGE 107
Control a Device Determine If a Device Has Failed 7-11 If a DeviceNet device stops communicating (device failure, cable break, etc.), the tag for the device stays at its last value. To make sure that your input data is valid, we recommend that you buffer the input data and examine the device failure register. Indication that a device has failed. • There is 1 bit for each address on the DeviceNet network. • If a bit = 1, then the device at that address has failed.
PAGE 108
7-12 Control a Device Place the Scanner in Run Mode To put the scanner in run mode, turn on this bit. To run the DeviceNet network: 1. Set the following bit of the output structure for the scanner: If you want to: The set this bit: To: run the network …O.CommandRegister.Run 1 not run the network (idle mode) …O.CommandRegister.Run 0 fault the network …O.CommandRegister.Fault 1 not fault the network …O.CommandRegister.Fault 0 disable the network …O.CommandRegister.
PAGE 109
Control a Device When to Use a MSG Instruction 7-13 If you want to set or get a parameter based on conditions in your logic, use a Message (MSG) instruction in ladder logic to access the parameter. controller Logic in the controller triggers the read or write of data. scanner MSG DeviceNet network device parameter 1 parameter 2 parameter 3 … … … Some parameters do not require ongoing updates. For example, initializing configuration parameters may occur only when the controller goes to run mode.
PAGE 110
7-14 Control a Device Determine the Configuration of the Parameter To get or set a parameter, find the following information about the parameter: Item: Value: class # (hex) instance # (hex) attribute # (hex) number of bytes (size) minimum value maximum value decimal places (Some devices assume a specific number of decimal places in a value.
PAGE 111
Control a Device Test the Parameter 7-15 A simple way to make sure that you have the correct configuration for a parameter (data size, values, etc.) is to use the Class Instance editor in RSNetWorx software. 1. In RSNetWorx software, go online to your DeviceNet network. 2. Right-click the device and choose Class Instance Editor. 3. Type the class, instance, and attribute for the parameter. 4. To change the parameter: a. Choose Set Single Attribute. b. Select the number of bytes. c.
PAGE 112
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.
PAGE 113
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.
PAGE 114
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.
PAGE 115
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: Is: scanner_name Name of the scanner in the I/O Configuration folder of the controller. device_address 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 Communication tab.
PAGE 116
7-20 Control a Device Typically, a CIP generic MSG instruction requires no connection to transfer its data. This type of message: Using this communication method: Uses a connection: CIP data table read or write CIP yes PLC2, PLC3, PLC5, or SLC (all types) CIP no CIP with Source ID no DH+ yes CIP generic CIP your choice(1) block-transfer read or write na yes (1) You can connect CIP generic messages, but for most applications we recommend you leave CIP generic messages unconnected.
PAGE 117
Chapter 8 Interlock and Share Inputs How to Use This Chapter The chapter describe how to interlock and share inputs over a DeviceNet network.
PAGE 118
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. This is simply defines the relationship between the controllers. The scanners of each controller still scans and controls its own devices, if desired.
PAGE 119
Interlock and Share Inputs 8-3 Enable Slave Mode for the Slave Scanner 1. In RSNetWorx software, open the properties for the slave scanner. 2. Choose Slave Mode. 3. Enable Slave Mode. 4. Define the I/O parameters.
PAGE 120
8-4 Interlock and Share Inputs Map the Slave Mode Data 1. Map the slave mode data to the input memory of the slave scanner. This is the data that the scanner (controller) gets from the master. 2. Repeat for the data that the slave scanner (controller) sends to the master. Add the Slave to the Scan List of the Master 1. In RSNetWorx software, open the properties for the master scanner. 2. Add the slave to the scan list.
PAGE 121
Interlock and Share Inputs 8-5 Map the Data of the Slave 1. Map the slave scanner to the input memory of the master scanner. This is the data that the scanner (controller) gets from the slave. 2. Repeat for the data that the master scanner (controller) sends to the slave. Place Both Scanners In Run Mode To exchange data, place both scanners in run mode. See Place the Scanner in Run Mode on page 7-12.
PAGE 122
8-6 Interlock and Share Inputs Add the Input to the Second Scanner 1. In RSNetWorx software, display the scan list for the second scanner. 2. In the Available Devices list, right-click and choose Shared Inputs. 3. Add the input to the scan list.
PAGE 123
Interlock and Share Inputs 8-7 Map the Input Data in the Second Scanner Map the input data to the input memory of the second scanner.
PAGE 124
8-8 Interlock and Share Inputs Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 125
Chapter 9 Communicate with a PanelView™ Standard Terminal Using This Chapter Choose Data Types This chapter describes how to configure and program communication with a PanelView Standard terminal on a DeviceNet network.
PAGE 126
9-2 Communicate with a PanelView™ Standard Terminal Choose an Communication Method You have 3 options to send data to/from a PanelView terminal: If you want to: Then use this method: communicate with the PanelView terminal using the reqular I/O communication of the the DeviceNet network I/O slave Notes • Easiest to use—requires no additional programming. • Use this as your first choice. • Higher priority on the network than explicit server and explicit client updates.
PAGE 127
Communicate with a PanelView™ Standard Terminal 9-3 Explicit Server Communication Explicit Server Controller executes a MSG instruction that gets or sets data in the PanelView terminal. • 14 assembly instances are available for explicit - server transfers. • Instance #s are 3 to 16. • You define an instance as either input data (I) or output data (O) but not both. • Each instance provides 64 words of either input or output data for the terminal.
PAGE 128
9-4 Communicate with a PanelView™ Standard Terminal Plan and Configure I/O Slave Tags Like the other DeviceNet devices, I/O slave tags use space in the input and output maps of the scanner. The scanner gets/sets the data on each scan of the DeviceNet network. A PanelView terminal gives you 2 blocks of 16-bit words (assembly instances) for I/O slave tags: Assembly instance 1 stores the data for write tags. It gives input data to the controller. Assembly instance 2 stores the data for read tags.
PAGE 129
Communicate with a PanelView™ Standard Terminal 9-5 Use a Word/Bit Format for Each Tag Each I/O slave tag requires a specific address in the corresponding assembly instance.
PAGE 130
9-6 Communicate with a PanelView™ Standard Terminal Configure an I/O Slave Tag 1. Type a descriptive name for the tag. 2. Select the data type for the tag. 3. Let the scanner update the data. 4. Assign an address for the tag within the input or output assembly.
PAGE 131
Communicate with a PanelView™ Standard Terminal Set Up the Terminal on the Network 9-7 To configure a PanelView terminal for communication on a DeviceNet network, complete the following steps in PanelBuilder32 software: Step: See page: ❑ Set the Protocol 9-7 ❑ Set the Network Address and I/O Sizes 9-8 Set the Protocol 1. Double-click Terminal Setup 2. Select DeviceNet. 3. Close the dialog box.
PAGE 132
9-8 Communicate with a PanelView™ Standard Terminal Set the Network Address and I/O Sizes 1. Double-click Communication Setup 2. Type the address of the PanelView terminal 3. Type the number of input words and output words that you will use (64 max. each). 4. Close the dialog box. 5. Close the dialog box.
PAGE 133
Communicate with a PanelView™ Standard Terminal Configure the Scanner to Update I/O Slave Tags 9-9 To access I/O slave tags, map the data to the input and output maps of the scanner. Step: See page: ❑ Add the Terminal to the Scan List 9-9 ❑ Edit I/O Parameters 9-10 ❑ Map Input and Output Data 9-10 Add the Terminal to the Scan List 1. Click the Scanlist tab 2. Clear the Automap on Add check box. 3. Add the terminal to the scan list. 4. Choose OK.
PAGE 134
9-10 Communicate with a PanelView™ Standard Terminal Edit I/O Parameters 1. Select the terminal. 2. Choose Edit I/O Parameters. 3. Type the input and output sizes in bytes. Make sure each number is 2 times the number you entered in the communication set-up of the terminal (1 word = 2 bytes). 5. Close the dialog box. Map Input and Output Data 1. Click the Input tab. 4. Set the alignment option (typically DWord align). 2. Select the terminal. 5. Choose AutoMap. 3.
PAGE 135
Communicate with a PanelView™ Standard Terminal Address I/O Slave Tags in the RSLogix 5000 Project 9-11 To find the data for an I/O slave tag in your RSLogix 5000 project, get the following information: • report for the network • address for the tag in the PanelView terminal 1. On the report for the network, find the memory address for the PanelView terminal. 2. Find the corresponding tag in the controller-scoped tags of the controller. 3. Find the data within the controller tag.
PAGE 136
9-12 Communicate with a PanelView™ Standard Terminal DeviceNet tags use this format: The scanner memory uses this format: Which is this tag in the controller: slot:type.Data[element].bit location:type.Data[element].
PAGE 137
Communicate with a PanelView™ Standard Terminal Plan and Configure Explicit Server Tags 9-13 Explicit server tags are similar to I/O tags except that the controller initiates the communication with the terminal. Explicit server tags do not show up on the input and output maps of the scanner.
PAGE 138
9-14 Communicate with a PanelView™ Standard Terminal Determine how you will use each assembly instance: Instance number: Input (write) or output (read): Instance number: 1 input 9 2 output 10 3 11 4 12 5 13 6 14 7 15 8 16 Input (write) or output (read): For Integers, Skip Every Other Word Logix5000 controllers use 32-bit integers (DINTs). To make your programming easier, lay out your PanelView tags as follows: Word 1. For bit-level tags, set aside an even number of words. 2.
PAGE 139
Communicate with a PanelView™ Standard Terminal 9-15 Configure an Explicit Server Tag 1. Type a descriptive name for the tag. 2. Select the data type for the tag. 3. Let the controller initiate the update. 4. Select the assembly instance for the tag. 5. Assign an address for the tag within the assembly instance.
PAGE 140
9-16 Communicate with a PanelView™ Standard Terminal Program the Controller to Get/Set Explicit Server Tags To let the controller read/write data from/to an explicit server tag: Step: See page: ❑ Create an Array for the Assembly Instance 9-16 ❑ Enter and Configure the MSG Instruction 9-17 ❑ Set the Communication Path 9-18 Create an Array for the Assembly Instance For each assembly instance that you use for explicit server tags, create an array in the RSLogix 5000 project for the data.
PAGE 141
Communicate with a PanelView™ Standard Terminal 9-17 Enter and Configure the MSG Instruction 1. Enter a condition for the data transfer, such as the DN bit of a timer. 2. Enter a MSG instruction. 3. Select CIP Generic. 4. To send output data, type/select: a. Set Attribute Single b. Array that has the data c. Number of bytes that you have addressed in the PanelView instance (words x 2). d. Class = 4 e. Instance = assembly instance of the data in the PanelView terminal. Convert it to hex. f.
PAGE 142
9-18 Communicate with a PanelView™ Standard Terminal Set the Communication Path The communication path specifies the route to the PanelView terminal. A communication path follows this format: scanner_name,2,device_address Where: Is: scanner_name Name of the scanner in the I/O Configuration folder of the controller. device_address Address of the device on the DeviceNet network. To set the path: 1. Click the Communication tab. 2. Click the Browse button and select the scanner. 3.
PAGE 143
Communicate with a PanelView™ Standard Terminal Configure Explicit Client Tags 9-19 Use an explicit client tag to let the PanelView terminal get or set a parameter of another device on the DeviceNet network.
PAGE 144
9-20 Communicate with a PanelView™ Standard Terminal Determine the Configuration of the Parameter To get or set a parameter, find the following information about the parameter: Item: Value: class # (hex) instance # (hex) attribute # (hex) number of bytes (size) minimum value maximum value decimal places (Some devices assume a specific number of decimal places in a value.
PAGE 145
Communicate with a PanelView™ Standard Terminal 9-21 Configure an Explicit Client Tag 1. Type a descriptive name for the tag. 2. Select the data type for the tag. 3. Let the PanelView terminal initiate the update. 4. Type the address of the device. 5. If the PanelView terminal sets the parameter, check this box. 6. Type the number of bytes in the parameter. 7. Type the class, instance, and attribute numbers for the parameter.
PAGE 146
9-22 Communicate with a PanelView™ Standard Terminal Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 147
Chapter 10 Communicate with an RSView® Project Using This Chapter This chapter describes how use an RSView project to get or set a parameter of a DeviceNet device. My RSView Screen IMPORTANT Once you add a device to the scan list of a scanner, HMI software such as RSView cannot write to (set) some parameters. Once this device is in the scan list of the scanner, an RSView project cannot set this parameter.
PAGE 148
10-2 Communicate with an RSView® Project To access the DeviceNet network, either connect the computer with the RSView application to any of the following networks: • same DeviceNet network as the desired device • EtherNet/IP or ControlNet network and bridge communication to the DeviceNet network – Avoid bridging through a CompactLogix, FlexLogix, or DriveLogix controller. They have limited resources for bridging. – For those controllers, use the I/O tags in the controller, if possible.
PAGE 149
Communicate with an RSView® Project Create a Topic for the Device 10-3 Use RSLinx software to create a topic for the DeviceNet device that you want to access. 1. In RSLinx software, browse to the device that you want to access. 2. Right-click the device and choose Configure New DDE/OPC Topic. 3. Type a name for the topic. 4. To change how often RSLinx software updates the tag, click the Data Collection tab and type a new poll period. 5. Choose Done. 6. Yes—update the topic.
PAGE 150
10-4 Communicate with an RSView® Project Create a Node In the RSView project, create a node for your RSLinx topics: 1. Open the list of nodes for the project. 2. Choose OPC Server. 3. Type a name for the node. 4. Select RSLinx OPC Server. 5. Accept.
PAGE 151
Communicate with an RSView® Project Create a Tag for the Parameter 10-5 In the RSView project, create a tag for the parameter: 1. Type the name for the tag. 2. Select the type of data. 3. Select Device. 4. Select the node that contains the topic for the device. 5. Open the address browser. 6. Browse to offline list of tags for the topic (device). 7. Select the parameter and choose OK.
PAGE 152
10-6 Communicate with an RSView® Project Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 153
Chapter 11 Tune the Performance of a DeviceNet Network Using This Chapter This chapter shows how to improve the performance of your network. As you configure and program your network, use the default settings whenever possible. Once your network is running, determine if you need to improve performance. To improve the performance of your network, consider the following: If: Then: a specific device requires a faster update Change the I/O parameters of the device to change of state (COS).
PAGE 154
11-2 Tune the Performance of a DeviceNet Network Factors that Effect Performance The following example shows how different I/O or network parameters effect the performance of the network. Scan Cycle Polled update P1 Pr1 3 data at address 3 changes P2 Pr2 P3 Pr3 P4 Pr4 P5 Pr5 scanner gets the data P1 Px – Scanner sends data to a polled device. Prx – Polled device sends input data to scanner.
PAGE 155
Tune the Performance of a DeviceNet Network 11-3 I/O Parameters of Each Device The type of connection (message) that you configure for a device determines when data transfers between the device and the scanner. • Each device has a default connection type. This is a good starting point. • Some devices may not offer all connection (message) types. The following table describes the different types of connections (messages) that you can configure for a device.
PAGE 156
11-4 Tune the Performance of a DeviceNet Network The following diagram show the effect of a change to the poll ratio: I/O scan poll ratio = 1 I/O scan poll ratio = 2 IMPORTANT background poll background poll background poll background poll background poll ↓ ↓ ↓ ↓ ↓ scan scan scan scan scan background poll background poll background poll ↓ ↓ ↓ scan scan scan scan scan Keep the (foreground to background poll ratio) x (interscan delay) ≤ 75 ms (default expected packet value).
PAGE 157
Tune the Performance of a DeviceNet Network Change the Configuration of the Network 11-5 To change the configuration of the network, use RSNetWorx software to perform the following: Step: See page: ❑ Upload the Current Configuration of the Scanner 11-5 ❑ Set the Interscan Delay and Poll Ratio 11-6 ❑ Set the I/O Parameters of a Device 11-6 ❑ Download the Configuration to the Scanner 11-8 ❑ Save the Network File 11-9 Upload the Current Configuration of the Scanner 1. Start RSNetWorx software.
PAGE 158
11-6 Tune the Performance of a DeviceNet Network Set the Interscan Delay and Poll Ratio Change these values only if needed. 1. Type or select the time for the interscan delay. 2. Type or select the poll ratio. Set the I/O Parameters of a Device 1. Click the Scanlist tab 2. Select the device. 3. Choose Edit I/O Parameters. 4.
PAGE 159
Tune the Performance of a DeviceNet Network 11-7 Change of State or Cyclic Transfer 1. Check this box. 2. Choose Change of State or Cyclic. 3. Type or select the number of bytes that the device sends to the controller. 4. Type or select the number of bytes that the controller sends to the device. 5. For a cyclic update, type the period of the update. 6. Close the dialog box. Strobed Transfer 1. Check this box. 2. Type or select the number of bytes that the device sends to the controller. 3.
PAGE 160
11-8 Tune the Performance of a DeviceNet Network Polled Transfer 1. Check this box. 2. Type or select the number of bytes that the device sends to the controller. 3. Type or select the number of bytes that the controller sends to the device. 4. Choose whether to poll the device every scan or in the background. 5. Close the dialog box. Download the Configuration to the Scanner 1. Apply the changes, 2. Yes, download. 3. Close the dialog box.
PAGE 161
Tune the Performance of a DeviceNet Network 11-9 Save the Network File After you make a change to your network, upload the entire network and save the file. This makes sure that the offline configuration file matches the network. 1. Network ⇒ Upload from Network. 2. Yes, upload the entire network. 3. Save the file.
PAGE 162
11-10 Tune the Performance of a DeviceNet Network Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 163
Chapter 12 Troubleshoot a DeviceNet Network Using This Chapter A DeviceNet network gives you the following status information: For this information: Front Display See page: Front Display 12-1 Status Tags in the Controller 12-13 Status Codes 12-16 To interpret the display or status indicators of a device: For this information: See page: CompactLogix Scanner 1769-SDN 12-1 ControlLogix Scanner 1756-DNB 12-3 ControlNet to DeviceNet Linking Device 1788-CN2DN 12-5 DriveLogix and FlexLogix Sca
PAGE 164
12-2 Troubleshoot a DeviceNet Network Module status indicator: State: Description: Recommended Action off No power applied to module. Apply power. flashing green No MicroLogix or CompactLogix controller is present. solid green Device is OK. None. flashing red Recoverable Fault - Memory has been erased or is being programmed. Complete flash update or start a new update. solid red Unrecoverable fault 1. 2. 3. 4. Make sure module connectors are properly seated. Cycle power to the controller.
PAGE 165
Troubleshoot a DeviceNet Network 12-3 ControlLogix Scanner 1756-DNB DeviceNet TM MOD/NET I/O OK 4-Character display: Display: Description: A#xx Address of this device, where: xx is the address. IDLE Device is in idle mode. AUTO The AutoScan option is on and the device is in idle mode. RUN Device is in run mode. No Network Power The DeviceNet cable is not supplying power to the communication port. Network Disabled Controller has set the device to the disabled mode.
PAGE 166
12-4 Troubleshoot a DeviceNet Network Module/Network (Mod/NET) status indicator State off Description: Recommended Action • The device has not completed the Dup_MAC_ID test. Make sure the device has power. • The device may not have power. solid green Device is OK and is communicating with other devices on the None. network. flashing green Device is OK but is not communicating with other devices on the network.
PAGE 167
Troubleshoot a DeviceNet Network 12-5 ControlNet to DeviceNet Linking Device 1788-CN2DN DeviceNet Network Status indicator State: off Description: Recommended Action • Device is not online. • No network power. • The device may not be powered. 1. If the module (MS) indicator is off, turn on power to the device. 2. Make sure the DeviceNet cable is supplying power to the communication port. flashing green Device is OK but is not communicating with other devices on the network.
PAGE 168
12-6 Troubleshoot a DeviceNet Network Module Status indicator State Description Recommended Action off No power. Turn on power to the device. flashing green The device is not configured and is in a standby state. Configure the device. solid green Normal operation None. solid red Device has an unrecoverable fault. flashing red 1. Cycle power to the device. 2. Replace the device • Recoverable fault. • Clear the fault. • DNet Data Rate or DNet Node Address switches are set in the PGM range.
PAGE 169
Troubleshoot a DeviceNet Network 12-7 DriveLogix and FlexLogix Scanner 1788-DNBO N Module status (MS) indicator State: Description: Recommended Action off No power applied to device. Turn on power to the controller. solid green Device is OK. None. flashing green Device either needs commissioning or is in the standby state. Make sure the device is correctly configured. flashing red Recoverable fault. Make sure the scan list of the device matches the configuration of the network.
PAGE 170
12-8 Troubleshoot a DeviceNet Network I/O status indicator State: Description: Recommended Action off Device is not online. Check network power. solid green Device is in run mode, outputs are under control, and inputs are being consumed. None. flashing green Device is in idle mode, outputs are not under control, and inputs are being consumed. To control outputs, place the device in run mode.
PAGE 171
Troubleshoot a DeviceNet Network 12-9 Ethernet (Network Status) status indicator State Description Recommended Action off Device has no IP address. Give the device an IP address. solid green Device has at least 1 connection on the EtherNet/IP network. None. flashing green Device has no connections on the EtherNet/IP network. solid red The module’s IP address is already in use by another module. Change the IP address.
PAGE 172
12-10 Troubleshoot a DeviceNet Network I/O Status indicator State Description Recommended Action flashing green Device is in idle mode To control outputs, place the device in run mode. solid green Device is in run mode None. solid orange Device is powering up. None. flashing red/green A fault has been detected. Clear the fault. off There are no devices in the scan list. If the device is supposed to communicate with other devices, add those devices to the scan list of this device.
PAGE 173
Troubleshoot a DeviceNet Network 12-11 SoftLogix5800 Scanner 1784-PCIDS The physical device has the following status lights: I/O status indicator State: Description: off All inputs and outputs are inactive. green S Allen-Bradley 1784-PCIDS Scanner • One or more inputs are active and producing data, and no inputs are faulted. flashing green I/O • One or more outputs are active and under control, and no outputs are faulted.
PAGE 174
12-12 Troubleshoot a DeviceNet Network Network (NET) status indicator State: off Description: Recommended Action • Device is not online. If the module (MS) indicator is off, turn on power to the • The device has not completed the Dup_MAC_ID test. controller. • The device may not be powered. flashing green Device is OK but is not communicating with other devices on the network. solid green Device is OK and is communicating with other devices on the None. network.
PAGE 175
Troubleshoot a DeviceNet Network Status Tags in the Controller 12-13 Tags in the controller give you several levels of information about your DeviceNet network. individual bits that show the general status and health of the scanner and network detailed information about each device on your network In the example above, the tags start with Local:2.
PAGE 176
12-14 Troubleshoot a DeviceNet Network Status Register The members of the status register (…I.
PAGE 177
Troubleshoot a DeviceNet Network 12-15 Status Tags The members of the Status tags (…S…), give you the following information: If you want this information: Check this member: Member: Data Type count of I/O scans ScanCounter DINT indication that a device is not communicating on the network: • There is 1 bit for each address on the DeviceNet network (0 -63). • The position of a bit = address of a device. • If a bit = 1, then the device at that address has failed.
PAGE 178
12-16 Troubleshoot a DeviceNet Network Status Codes Status codes give you detailed information about the status or error of the scanner or another device on the network. • The status tags for the scanner give you the status codes. Refer to Status Tags on page 12-15. • Some scanners also show status codes on the front of the scanner. Use the following table to interpret status codes. Status code (decimal) Description Action 65 The AutoScan option is on and the device is in idle mode. None.
PAGE 179
Troubleshoot a DeviceNet Network Status code (decimal) 12-17 Description Action 81 Controller has set the scanner to the faulted mode. See if the following bit of the command register for the scanner is on: …O.CommandRegister.Fault 82 Error detected in sequence of fragmented I/O messages from device. • Check scan list device to make sure that its input and output data sizes are correct. • Check the configuration of the device.
PAGE 180
12-18 Troubleshoot a DeviceNet Network Status code (decimal) 97 Description Controller has set the scanner to the halted mode. Action 1. See if the following bit of the command register for the scanner is on: …O.CommandRegister.HaltScanner 2. Cycle power to the scanner. 98 General firmware error. Replace device. 99 System failure. Replace device.
PAGE 181
Chapter 13 Automate the Replacement of a Failed Device How to Use This Chapter How to Automate the Replacement of a Failed Device This chapter describes how to reduce the time it takes to replace a failed device: For this information: See page: How to Automate the Replacement of a Failed Device 13-1 Set Up Automatic Device Recovery 13-3 To reduce system downtime if a device fails, use the Automatic Device Recovery (ADR) option.
PAGE 182
13-2 Automate the Replacement of a Failed Device You configure ADR on a device-by-device basis.
PAGE 183
Automate the Replacement of a Failed Device Set Up Automatic Device Recovery 13-3 To set up ADR for a device: Step: See page: ❑ Choose an Electronic Key Level for a Device 13-3 ❑ Update the Network Configuration File 13-4 ❑ Define the Electronic Key 13-5 ❑ Enable Auto-Address Recovery for the Scanner 13-6 ❑ Set the ADR Settings for the Device 13-6 ❑ Download the Changes to the Scanner 13-7 ❑ Upload and Save the Network File 13-7 Choose an Electronic Key Level for a Device Use the electron
PAGE 184
13-4 Automate the Replacement of a Failed Device Update the Network Configuration File When you set up ADR for a device, RSNetWorx reads the configuration for the device from the configuration file and stores it in the scanner. Before you set up ADR for a device, make sure the configuration file is up-to-date. 1. Go online. 2. Configure the devices. 3. Right-click and upload the entire network. 4. Save the network configuration.
PAGE 185
Automate the Replacement of a Failed Device 13-5 Define the Electronic Key 1. Double-click the scanner. 2. Click the Scanlist tab. 3. Select the device. 4. Check those items that must match before a replacement device receives the configuration/address of the selected device.
PAGE 186
13-6 Automate the Replacement of a Failed Device Enable Auto-Address Recovery for the Scanner 1. Click the ADR tab. 2. Enable auto-address recovery. 3. Yes—enable auto-address recover. Set the ADR Settings for the Device 1. Select the device. 2. Send the configuration of the device from the configuration file to the scanner. 3. Select the ADR settings for the device.
PAGE 187
Automate the Replacement of a Failed Device 13-7 Download the Changes to the Scanner 1. Apply the changes, 2. Yes, download. 3. Close the dialog box. Upload and Save the Network File 1. Network ⇒ Uploade from Network. 2. Yes, upload the entire network. 3. Save the file.
PAGE 188
13-8 Automate the Replacement of a Failed Device Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 189
Chapter 14 Using FLEX™ I/O Modules on a DeviceNet Network How to Use This Chapter This chapter provides basic information on how to use a Flex I/O adapter 1794-ADN to connect the following I/O modules to a DeviceNet network: • • • • 1793 FLEX I/O 1794 FLEX Ex I/O 1797 1203-FM1 To use the Flex I/O adapter 1794-ADN: 1 Step: Page: ❑ Tally Memory Requirements 14-2 ❑ Assign an Address to the Adapter 14-3 ❑ If You Configure the Adapter Offline 14-3 ❑ Set the Address of the Adapter 14-4 ❑ If You
PAGE 190
14-2 Using FLEX™ I/O Modules on a DeviceNet Network Tally Memory Requirements The Flex I/O adapter 1794-ADN packs the data of its I/O modules into a contiguous block of input or output bytes. By default, the modules share DINT elements in the scanner. To determine the amount of scanner memory required for your adapter and its I/O modules 1. Add the input bytes of each module + 2 bytes for the adapter. 2. Add the output bytes of each module (0 for the adapter).
PAGE 191
Using FLEX™ I/O Modules on a DeviceNet Network Assign an Address to the Adapter 14-3 Assign 1 address for the 1794-ADN and all the modules that you connect to it. DeviceNet network 4 A D N If You Configure the Adapter Offline offline configuration I/ I/ I/ O O O If you configure the Flex I/O adapter offline, check the I/O sizes of each module. For Flex I/O, RSNetWorx software uses offline I/O sizes that are different from the default values of the modules.
PAGE 192
14-4 Using FLEX™ I/O Modules on a DeviceNet Network Set the Address of the Adapter To set the address of the Flex I/O adapter 1794-ADN: 1. 2. 3. 4. To change the address, press the button above or below a number. Connect the adapter to the network. Turn on power to the adapter. Check the Mode/Net STATUS light.
PAGE 193
Using FLEX™ I/O Modules on a DeviceNet Network Interpret the Status Indicators 14-5 The Flex I/O adapter 1794-ADN has the following status indicators. Power status indicator State: Description: On Power applied to module OFF No power applied to module. Check power wiring to adapter module.
PAGE 194
14-6 Using FLEX™ I/O Modules on a DeviceNet Network Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 195
Chapter 15 Using POINT™ I/O Modules on a DeviceNet Network How to Use This Chapter POINT I/O Interface 1734-PDN This chapter provides basic information on how to use a POINT I/O modules on a DeviceNet network.
PAGE 196
15-2 Using POINT™ I/O Modules on a DeviceNet Network Choose a Connecting Device POINT I/O Interface 1734-PDN To choose the device that connects your POINT I/O modules to the DeviceNet network, consider the following: • total number of devices on the network • type of devices on the network • topology and length of the network • current requirements of the POINT I/O modules POINT I/O Adapter 1734-ADN POINT I/O Adapter 1734-ADNX POINTBlock I/O Module 1734D main DeviceNet network P D N 1 2 3 4 P O I
PAGE 197
Using POINT™ I/O Modules on a DeviceNet Network Tally Memory Requirements POINT I/O modules connect to an adapter or interface module. To tally their memory requirements: 4 P O I N T I/ O For this module: See page: POINT I/O 1734-ADN or 1734-ADNX Adapter 15-3 POINT I/O 1734-PDN Interface 15-4 POINT I/O 1734-ADN or 1734-ADNX Adapter subnet A D N 15-3 The ADN/ADNX adapter creates a small network (subnet) out of the modules and devices that are connected to it.
PAGE 198
15-4 Using POINT™ I/O Modules on a DeviceNet Network POINT I/O 1734-PDN Interface 1 2 3 P D N P O I N T I/ O P O I N T I/ O Each POINT I/O module gets its own address on the network and requires scanner memory: P O I N T I/ O 1. Add each POINT I/O module to your main tally. 2. Make sure to convert the input or output size of each module to DINTs of scanner memory. 3. Leave the PDN interface out of the tally.
PAGE 199
Using POINT™ I/O Modules on a DeviceNet Network Set the Address of a Module 15-5 The following sections show how to set the address of specific devices. For this device: See page: POINT I/O Interface 1734-PDN 15-5 POINT I/O Module 1734 15-5 POINT I/O Adapter 1734-ADN and 1734-ADNX 15-6 POINTBlock I/O Module 1734D 15-6 POINT I/O Interface 1734-PDN The 1734-PDN module does not use an address on the network.
PAGE 200
15-6 Using POINT™ I/O Modules on a DeviceNet Network POINT I/O Adapter 1734-ADN and 1734-ADNX 1. 2. 3. 4. Adapter Status DeviceNet Status PointBus Status To change the address, press the button above or below a number. Connect the adapter to the network. Turn on power to the adapter. Check the DeviceNet Status light.
PAGE 201
Using POINT™ I/O Modules on a DeviceNet Network Automatically Sequence Point I/O Addresses 15-7 If you connect Point I/O modules to a 1734-PDN interface, use the left-hand module to set the addresses of the modules to its right in the group: 1. Set the address of the left-most I/O module. Refer to Set an Address with Software on page 5-3. 1 63 63 P D N P O I N T I/ O P O I N T I/ O P O I N T I/ O 2. When you configure the left-most I/O module, set Sequential AutoAddress = Sequential Address.
PAGE 202
15-8 Using POINT™ I/O Modules on a DeviceNet Network Configure a Point I/O Adapter The POINT I/O adapter (1734-ADN or 1734-ADNX) functions as follows: On the main DeviceNet network, the 1734-ADN or 1734-ADNX device is an adapter. On the subnet, the 1734-ADN or 1734-ADNX device is the scanner.
PAGE 203
Using POINT™ I/O Modules on a DeviceNet Network 15-9 Upload the Configuration of the ADN/ADNX Adapter 1. Double-click the adapter. 2. Click the Parameters tab. 3. Upload the configuration from the device.
PAGE 204
15-10 Using POINT™ I/O Modules on a DeviceNet Network Configure the Adapter to Execute an Auto Start The Auto Start Mode parameter, does a one-time configuration of the subnet. If you add devices to the subnet after you execute auto start, execute auto start again. 1. For the Auto Start parameter, select Map Data To DWord Boundaries. 2. Apply the change. 3. Download the change.
PAGE 205
Using POINT™ I/O Modules on a DeviceNet Network 15-11 Create a File for the Subnet 1. Start another instance of RSNetWorx software. 2. Create a file. 3. Select DeviceNet Configuration. 4. Choose OK. Access the Subnet 1. Go online. 2. Browse to the Subnet. 3. Choose OK. The message is telling you that the software is not going to read or change the parameters of the devices. You do that in the next step.
PAGE 206
15-12 Using POINT™ I/O Modules on a DeviceNet Network Upload the Subnet Configuration and Save It to a File 1. Right-click and upload the entire network. 2. Save the file and give it a name that identifies it as the ADN or ADNX subnet configuration. 3. Close this instance of RSNetWorx software. Specify the Subnet File in the Configuration of the Adapter After you configure the subnet, define it as the associated network for the adapter.
PAGE 207
Using POINT™ I/O Modules on a DeviceNet Network If You Change the Configuration of the Adapter 15-13 Before you make an online change to a POINT I/O adapter 1734-ADN/1734-ADNX that effects the size of its input or output data, remove the adapter from the scan list of the scanner. Otherwise, RSNetWorx software responds with the following error: Device state conflict. For example, adding or removing an I/O module to/from the adapter changes the I/O data of the adapter. To add or remove a module: 1.
PAGE 208
15-14 Using POINT™ I/O Modules on a DeviceNet Network POINT I/O Module 1734 Module Status Module Status indicator Network Status NODE: 24VDC Sink Input 0 1 2 State Description off No power applied to device green Device operating normally flashing green Device needs commissioning due to configuration missing, incomplete or incorrect. flashing red Recoverable fault.
PAGE 209
Using POINT™ I/O Modules on a DeviceNet Network State Description Recommended Action flashing red Recoverable fault Make sure the adapter does not need a FLASH update solid red Unrecoverable fault may require device replacement Replace the adapter flashing red/green Device is in self-test Wait for self-test to finish 15-15 DeviceNet Status indicator State Description Recommended Action off Device is not online Check adapter status indicator to determine if more time is needed to complete
PAGE 210
15-16 Using POINT™ I/O Modules on a DeviceNet Network System Power indicator State Description off Any of the following: green Recommended Action • Not active • Check adapter configuration • Field power is OFF • Turn field power ON • DC-DC converter problem • Check DC-DC converter Any of the following: None • System power ON • DC-DC converter active (5V) Field Power indicator State Description off Any of the following: • Not active Recommended Action • Check adapter configuration • Turn
PAGE 211
Using POINT™ I/O Modules on a DeviceNet Network 15-17 POINTBlock I/O Module 1734D Module Status indicator State Description off No power applied to device green Device operating normally flashing green Device needs commissioning due to configuration missing, incomplete or incorrect. flashing red Recoverable fault.
PAGE 212
15-18 Using POINT™ I/O Modules on a DeviceNet Network Interpret POINT I/O Data (Data Maps) I/O messages are sent to (consumed) and received from (produced) the POINT I/O modules. These messages are mapped into the processor’s memory. This appendix lists the default data maps for 1734 POINT I/O and 1734-POINTBlock modules.
PAGE 213
Using POINT™ I/O Modules on a DeviceNet Network 15-19 1734-IA2 Input Module Message size: 1 Byte 7 6 5 4 3 2 Produces (scanner Rx) Consumes (scanner Tx) 1 0 Ch1 Ch0 1 0 Ch1 Ch0 No consumed data Where: Ch0 = channel 0, Ch1 = channel 1; 0 = off, 1 = on 1734-IB2 Sink Input Module Message size: 1 Byte 7 6 5 4 3 2 Produces (scanner Rx) Consumes (scanner Tx) No consumed data Where: Ch0 = channel 0, Ch1 = channel 1; 0 = OFF 1 = ON 1734-IB4 Sink Input Module Message size: 1 Byte 7 6 5
PAGE 214
15-20 Using POINT™ I/O Modules on a DeviceNet Network 1734-IV2 Source Input Module Message size: 1 Byte 7 6 5 4 3 2 Produces (scanner Rx) Consumes (scanner Tx) 1 0 Ch1 Ch0 No consumed data Where: Ch0 = input channel 0 data Ch1 = input channel 1 data 1734-IV4 Source Input Module Message size: 1 Byte 7 6 5 4 Produces (scanner Rx) Consumes (scanner Tx) 3 2 1 0 Ch3 Ch1 Ch1 Ch0 No consumed data Where: Ch0 = input channel 0 Ch1 = input channel 1 Ch2 = input channel 2 Ch3 = input chann
PAGE 215
Using POINT™ I/O Modules on a DeviceNet Network 15-21 1734-OB2E Electronically Protected Output Module Message size: 1 Byte 7 6 5 Produces (scanner Rx) 4 3 2 Not used 1 0 Ch1 Ch0 1 0 Ch1 Ch0 Channel status Where: 0 = no error 1 = error Message size: 1 Byte 7 6 5 Consumes (scanner Tx) 4 3 2 Not used Channel state Where: 0 = OFF 1 = ON 1734-OB2EP Protected Output Module Message size: 1 Byte 7 6 5 Produces (scanner Rx) 4 3 2 Not used 1 0 Ch1 Ch0 1 0 Ch1 Ch0 Channel
PAGE 216
15-22 Using POINT™ I/O Modules on a DeviceNet Network Message size: 1 Byte 7 6 Consumes (scanner Tx) 5 4 Not used 3 2 1 0 Ch3 Ch2 Ch1 Ch0 Channel state Where: 0 = Off 1 = On 1734-OV2E Protected Sink Output Module Message size: 1 Byte 7 Produces (scanner Rx) 6 5 4 3 2 Not used 1 0 Ch1 Ch0 1 0 Ch1 Ch0 Channel status Where:0 = no error 1 = error Message size: 1 Byte 7 Consumes (scanner Tx) 6 5 4 3 2 Not used Channel state Where:0 = OFF 1 = ON 1734-OV4E Protected Sink
PAGE 217
Using POINT™ I/O Modules on a DeviceNet Network 15-23 1734-OW2 Relay Sink/Source Output Module Message size: 1 Byte 7 6 5 4 Consumes (scanner Tx) 3 2 Not used 1 0 Ch1 Ch0 1 0 Ch1 Ch0 Channel state Where: 0 = OFF 1 = ON 1734-OX2 Relay Output Module Message size: 1 Byte 7 6 5 4 Consumes (scanner Tx) 3 2 Not used Channel state Where: 0 = NO contact OFF, NC contact ON1 = NO contact ON, NC contact OFF 1734-IE2C Analog Current Input Module Message size: 6 Bytes 15 Produces (scanner R
PAGE 218
15-24 Using POINT™ I/O Modules on a DeviceNet Network Channel Status Table 15.
PAGE 219
Using POINT™ I/O Modules on a DeviceNet Network 15-25 1734-OE2C Analog Current Output Module Message size: 4 bytes 15 14 Consumes (Tx) 13 12 11 10 09 08 07 06 05 04 03 02 Output Channel 0 High Byte Output Channel 0 Low Byte Output Channel 1 High Byte Output Channel 1 Low Byte 01 00 01 00 CM CF Message size: 2 Bytes 15 14 Produces (Rx) 13 12 11 10 09 08 07 06 High Byte - Channel 1 Status Not used HCA LCA 05 04 03 02 Low Byte - Channel 0 Status CM CF Not used HC
PAGE 220
15-26 Using POINT™ I/O Modules on a DeviceNet Network 1734-IJ Encoder/Counter Module Message size: 6 Bytes 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 0 0 ZS BS AS C1 C0 ZD 0 Produces (scanner Rx) Channel 0 value of present counter state (LSW) Channel 0 value of present counter state (MSW) PE EF NR 0 0 0 0 Where:PE = Programming error EF = EEPROM fault status NR = Not ready status bit ZS = Z input status BS = B input status AS = A input status C = Stored data count ZD =
PAGE 221
Using POINT™ I/O Modules on a DeviceNet Network 15-27 1734-IM2 Input Module Message size: 1 Byte 7 6 5 4 3 2 Produces (Rx) Consumes (Tx) 1 0 Ch1 Ch0 No consumed data Where: Ch0 = channel 0, ICh1 = channel 1; 0 = off, 1 = on 1734-IR2 RTD Input Module Message size: 6 Bytes 15 14 13 12 11 10 09 08 07 06 05 04 Produces (scanner Rx) Input Channel 0 - High Byte Input Channel 0 - Low Byte Input Channel 1 - High Byte Input Channel 1 - Low Byte Status Byte for Channel 1 Status Byte fo
PAGE 222
15-28 Using POINT™ I/O Modules on a DeviceNet Network 1734-IT2I Isolated Thermocouple Input Module Message size: 8 Bytes 15 14 13 12 11 10 09 08 07 06 05 04 Produces (scanner Rx) Input Channel 0 - High Byte Input Channel 0 - Low Byte Input Channel 1 - High Byte Input Channel 1 - Low Byte Status Byte for Channel 1 Status Byte for Channel 0 OR UR HHA L HA LA LA OR UR CM CF OR UR HHA L LA Cold Junction Temperature (Selectable: Channel 0, Channel 1, or Average of both Channel 0 a
PAGE 223
Using POINT™ I/O Modules on a DeviceNet Network 15-29 1734-VHSC 24V dc High Speed Counter Module Message size: 6 Bytes 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 OS 0 ZS BS AS C1 C0 ZD 0 Produces (scanner Rx) Channel 0 value of present counter state (LSW) Channel 0 value of present counter state (MSW) PE EF NR 0 FS FS OS Where:PE = Programming error EF = EEPROM fault status NR = Not ready status bit FS = Output fault status bit - bit 10 for output 0, bit 11 for output
PAGE 224
15-30 Using POINT™ I/O Modules on a DeviceNet Network 1734-VHSC 5V dc High Speed Counter Module Message size: 6 Bytes 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 OS 0 ZS BS AS C1 C0 ZD 0 Produces (scanner Rx) Channel 0 value of present counter state (LSW) Channel 0 value of present counter state (MSW) PE EF NR 0 FS FS OS Where:PE = Programming error EF = EEPROM fault status NR = Not ready status bit FS = Output fault status bit - bit 10 for output 0, bit 11 for output 1
PAGE 225
Using POINT™ I/O Modules on a DeviceNet Network 15-31 1734-232ASC ASCII Module Default Receive Data Assembly Format (Default Mode) Byte 1 Byte 2 Rx Transaction ID Byte Status Byte Byte 3 Reserved Byte 4 Length Byte 5-23 ASCII Data Byte 24 (Terminator) Default Transmit Data Assembly Format (Default Mode) Byte 1 Reserved Byte 2 TX Transaction ID Byte Byte 3 Reserved Byte 4 Length Byte 5-23 ASCII Data Byte 24 (Terminator) Publication DNET-UM004A-EN-P - March 2004
PAGE 226
15-32 Using POINT™ I/O Modules on a DeviceNet Network Notes: Publication DNET-UM004A-EN-P - March 2004
PAGE 227
Appendix A Give a Value Its Own Memory Location When to Use This Appendix Sometimes, an input or output value for a device may end up encapsulated within a larger tag. For example, a speed value may end up as the upper 16 bits of a DINT element in the scanner. To access the value, you would have to use additional programming. 2:I.
PAGE 228
A-2 Give a Value Its Own Memory Location Give a Value Its Own Memory Location To give a value its own DINT in the input or output memory of the scanner: 1. Select the device and choose Advanced. 2. For the first map entry, specify the first bit of the data. a. type of connection b. starting byte of the data c. starting bit of the data 3. Specify the map location for the data. a. element number in the map b. starting bit c. number of bits 4. Apply the mapping. 5. Select the next map number. 6.
PAGE 229
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 d
PAGE 230
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
PAGE 231
Index 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 configur
PAGE 232
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
PAGE 233
Index 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 ad
PAGE 234
6 Index Publication DNET-UM004A-EN-P - March 2004
PAGE 235
How Are We Doing? Your comments on our technical publications will help us serve you better in the future. Thank you for taking the time to provide us feedback. You can complete this form and mail (or fax) it back to us or email us at RADocumentComments@ra.rockwell.com Pub. Title/Type DeviceNet Modules in Logix5000™ Control Systems Cat. No. 1734-ADN, 1734-ADNX, 1734-PDN, 1756-DNB, 1769-SDN, 1784-PCIDS, 1788-CN2DN, 1788-DNBO, 1788-EN2DN, 1794-ADN Pub. No. DNET-UM004A-EN-P Pub. Date March 2004 Part No.
PAGE 236
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.
PAGE 237
ControlNet is a trademark of ControlNet International, Ltd. DeviceNet is a trademark of the Open DeviceNet Vendor Association. Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
PAGE 238
Rockwell Automation Support Rockwell Automation provides technical information on the web to assist you in using our products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
PAGE 239
DeviceNet Modules in Logix5000™ Control Systems User Manual