ControlNet Modules in Logix5000 Control Systems 1734-ACNR, 1756-CN2, 1756-CN2R, 1756-CNB, 1756-CNBR, 1769-L32C, 1769-L35CR, 1784-PCC, 1784-PCIC, 1784-PCICS, 1784-PKTCS, 1788-CNC, 1788-CNCR, 1788-CNF, 1788-CNFR, 1794-ACN15, 1794-ACNR15, 1797-ACNR15 User Manual
Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature) describes some important differences between solid state equipment and hard-wired electromechanical devices.
Summary of Changes Introduction This release of this document contains updated information. Changes are designated by change bars in margin, as shown to the right. New and Revised Information The table below lists the new information included in this release of the ControlNet Modules in Logix5000 Control Systems user manual.
Summary of Changes 2 Notes: Publication CNET-UM001C-EN-P - November 2005
Preface Purpose of This Manual This manual describes how you can use ControlNet with your Logix5000 controller. With this manual, you can learn how to communicate between your controller and various devices on the ControlNet network.
Preface 2 Information This Manuals Contains Publication CNET-UM001C-EN-P - November 2005 This table describes the information available in this manual.
Preface Related Documentation 3 This table lists ControlNet products and documentation that may be valuable as you program your application.
Preface 4 Notes: Publication CNET-UM001C-EN-P - November 2005
Table of Contents Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Summary of Changes Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Changes-1 New and Revised Information . . . . . . . . . . . . . Summary of Changes-1 Preface Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Use This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . Information This Manuals Contains . . . .
Table of Contents 2 Schedule the Network Offline . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Schedule the Network Online . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 Reschedule a ControlNet Network That Has Previously Been Scheduled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23 Chapter 4 Control I/O Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Set Up the Hardware . . . . . . . . . . .
Table of Contents 3 Message Type to Configure a MSG to Logix5000 Controller . . 6-8 Message Type to Configure a MSG to an SLC 500 Processor . . 6-9 Message Type to Configure a MSG to a PLC-5 Processor . . . 6-10 Communicate with PLC-5 or SLC 500 Processors . . . . . . . . . . . . . 6-12 Initiate MSGs from PLC-5 Processors to Logix5000 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12 Map Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 4 1794-ACN15 and 1794-ACNR15 ControlNet FLEX I/O Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21 1797-ACNR15 ControlNet FLEX Ex Redundant Media I/O Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23 Appendix A Connection Use Over ControlNet Use This Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ControlNet Connections . . . . . . .
Table of Contents 5 Use Redundant Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-17 Application Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20 General Wiring Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21 Order Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23 General Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 6 Publication CNET-UM001C-EN-P - November 2005
Chapter 1 About the Logix5000 ControlNet Communication Modules Use This Chapter This chapter introduces the Logix5000 ControlNet communication modules and describes how you can use these modules in a control system: For This Information See Page Choose a ControlNet Communication Module 1-1 1756-CN2, 1756-CN2R Overview 1-3 1756-CNB, 1756-CNBR Overview 1-4 1769-L32C, 1769-L35CR Overview 1-4 1784-PCC Overview 1-5 1784-PCIC, 1784-PCICS, 1784-PKTCS Overview 1-5 1788-CNC, 1788-CNCR, 1788-CNF, 17
1-2 About the Logix5000 ControlNet Communication Modules This table describes the ControlNet communication modules’ functionality. Table 1.
About the Logix5000 ControlNet Communication Modules 1-3 ControlLogix ControlNet communication modules bridge ControlNet links to route messages to devices on other networks. The modules also monitor and control I/O modules located remotely from the ControlLogix controller. 1756-CN2, 1756-CN2R Overview The 1756-CN2 and 1756-CN2R modules are supported in the following software: • RSLogix 5000 software version 15.
1-4 About the Logix5000 ControlNet Communication Modules ControlLogix ControlNet communication modules bridge ControlNet links to route messages to devices on other networks. The modules also monitor and control I/O modules located remotely from the ControlLogix controller. 1756-CNB, 1756-CNBR Overview This module provides: • adapter functionality for remote ControlLogix I/O modules. • messaging data for configuration and programming information, operator interfaces, upload/download.
About the Logix5000 ControlNet Communication Modules 1-5 The 1784-PCC communication interface cards are personal computer memory card international association (PCMCIA) interface cards that enable laptop computers to communicate directly with other ControlNet products. These cards support: 1784-PCC Overview 43678 • messaging data for configuration and programming information, operator interfaces, upload/download. • unscheduled messaging communication with other ControlNet nodes.
1-6 About the Logix5000 ControlNet Communication Modules The ControlNet communication card links the FlexLogix controller and PowerFlex 700S with DriveLogix controller to other devices on a ControlNet network. The ControlNet communication card also provides access for the FlexLogix controller to monitor and control I/O modules located remotely from the controller on the ControlNet network.
About the Logix5000 ControlNet Communication Modules 1-7 The 1797-ACNR15 modules operate as adapters for FLEX Ex I/O modules on a ControlNet network in an intrinsically safe environment. This module supports: 1797-ACNR15 Overview • control of I/O within its chassis–you can connect up to 8 FLEX Ex I/O modules to one 1797-ACNR15 module. • unscheduled messaging data for configuration. 41411 • control of individual I/O modules by different controllers. • redundant media.
1-8 About the Logix5000 ControlNet Communication Modules Use the ControlNet Communication Modules in a Control System This figure shows how the different ControlNet modules can fit into a control system. Figure 1.1 ControlNet Modules and the Control System Relationship PC Running SoftLogix5800 Controller with 1784-PCICS Card ControlLogix controller with 1756-CN2(R) or 1756-CNB(R) module as the scanner.
About the Logix5000 ControlNet Communication Modules Bridge Across Networks 1-9 Some ControlNet modules support the ability to bridge or route communication to and from different networks, depending on the capabilities of the platform and communication devices. With unscheduled communication, you have a bridge when you have a connection between communication devices on two separate networks.
1-10 About the Logix5000 ControlNet Communication Modules In this example, a workstation configures a drive on a DeviceNet network. The workstation bridges from ControlNet to DeviceNet to reach the drive. Figure 1.
About the Logix5000 ControlNet Communication Modules 1-11 Keep in mind that you can only bridge messages across networks. You cannot bridge I/O connections from one network to another. IMPORTANT The CompactLogix and FlexLogix controllers’ performance degrades significantly if you use the controller as a bridge. Bridging over the FlexLogix controller should be targeted toward applications that are not real time dependent, for example RSLogix 5000 software program downloads.
1-12 About the Logix5000 ControlNet Communication Modules This table lists the possible bridges between communication networks. Table 1.
Chapter 2 Connect a Computer to the ControlNet Network Use This Chapter Read this chapter for: • 1784-PCC, 1784-PCIC, 1784-PCICS, 1784-PKTCS cards This chapter describes how to configure a personal computer to operate on a ControlNet network.
2-2 Connect a Computer to the ControlNet Network Connect a Computer to Any Network To access a network, either: • connect directly to the network or • connect to a different network and browse (bridge) to the desired network. This requires no additional programming.
Connect a Computer to the ControlNet Network Configure the ControlNet Communication Driver in the RSLinx Software 2-3 To configure the ControlNet communication driver for the personal computer (programming workstation): IMPORTANT Do not use these steps to configure a ControlNet communication driver for any application that uses a SoftLogix5800 controller. With the SoftLogix5800 controller, you can configure a ControlNet communication driver via the SoftLogix5800 Chassis Monitor.
2-4 Connect a Computer to the ControlNet Network 3. Name the new ControlNet driver. A. Name the driver. This example shows the default name AB_PCIC-1. B. Click OK. 4. After you create the driver, configure it to correspond to the ControlNet module within your computer. A. If multiple cards are located in your computer, choose the correct one. B. Make sure you use the correct Network Address. C. Click OK. The appearance of this screen varies widely depending on the type of card used.
Connect a Computer to the ControlNet Network Connect a SoftLogix Controller to ControlNet 2-5 The SoftLogix5800 controller is a soft control solution that runs in a Microsoft Windows NT, Windows 2000, or Windows XP environment. When using this controller, you must install the SoftLogix5800 Chassis monitor–a virtual chassis that takes the place of hardware chassis used with other Logix5000 controllers.
2-6 Connect a Computer to the ControlNet Network 4. Configure the card. A. Specify the node address on the ControlNet network. B. Enter the label name for the card (this is the name you wrote on the label of the card to help you identify the card from others in the same computer). C. Click Finish. You can specify any slot number greater than 0 for the communication card. RSLinx software resides in slot 0.
Chapter 3 Configure a ControlNet Module Use This Chapter Read this chapter for: • 1756-CN2, 1756-CN2R modules • 1756-CNB, 1756-CNBR modules • 1769-L32C, 1769-L35CR controllers • 1784-PCIC, 1784-PCICS, • • • 1784-PKTCS cards 1788-CNx cards 1794-ACN15, 1794-ACNR15 adapters 1797-ACNR15 adapter This chapter describes how to configure a ControlNet communication module to operate on a ControlNet network.
3-2 Configure a ControlNet Module Set Up Your Computer to Connect to ControlNet You connect your personal computer to the ControlNet network via an RSLinx ControlNet software communication driver. You use the ControlNet communication driver to: • upload and download controller projects using RSLogix 5000 software. • schedule the ControlNet network via RSNetWorx for ControlNet software.
Configure a ControlNet Module 3-3 Add a Local ControlNet Module After you have started RSLogix 5000 software and created a controller project, you can add ControlNet communication modules. A local ControlNet module is a module that resides in the same chassis as the controller. IMPORTANT When you create a new RSLogix 5000 project with the CompactLogix 1769-L32C or 1769-L35CR controller, the Controller Organizer creates a ControlNet port in the local chassis.
3-4 Configure a ControlNet Module This table lists the ControlNet communication modules available locally such as in the local chassis, computer, or controller with each Logix5000 controller. Table 3.
Configure a ControlNet Module 3-5 F. Inhibit the module, if necessary. Initially, do you want the module to communicate with the controller? Then Yes Leave the box unchecked No Check the box(1) (1) When you test this portion of the system, clear the check box. F. Click Finish. G. Determine if you want a major fault on the controller if the connection to the local communication module fails in Run Mode.
3-6 Configure a ControlNet Module This table describes the keying options available in RSLogix 5000 software. Table 3.
Configure a ControlNet Module 3-7 Add a Remote ControlNet Module After you have added the local ControlNet communication module, you must add remote ControlNet communication modules. A remote ControlNet module is a module that resides in a separate chassis from the controller. 1. Select a New Module for the I/O Configuration. A. Right-click on the local communication module. B. Select New Module. 2. Select the module type from the Select Module Type pop-up.
3-8 Configure a ControlNet Module 3. Configure the remote ControlNet communication module. IMPORTANT The example below shows configuration for a 1756-CNB module. However, depending on the remote module-type such as a 1734, 1756, 1769, 1784, 1788, or 1794, there are differences in how to configure a remote ControlNet communication module. If you need help configuring a specific module, use online help in RSLogix 5000 software. A. Name the remote module. B. Select the remote module’s Node. C.
Configure a ControlNet Module 3-9 Communication Format The communication format determines: • what configuration options are available - for example, if the module uses None, then you do not have to configure an RPI rate on the next screen. • what type of data is transferred between the owner-controller and I/O connected via the communication module. • what tags are generated when configuration is complete.
3-10 Configure a ControlNet Module Download the Project to the Logix5000 Controller IMPORTANT Before you your RSLogix5000 project configuration to your ControlNet Communication modules, consider whether you will schedule the ControlNet network offline or online. • If you are going to schedule the network offline, complete the steps beginning in the section Schedule the Network Offline before downloading configuration.
Configure a ControlNet Module 3-11 3. Use the Who Active pop-up screen to download the project to the controller. A. Expand the tree until you find the correct driver. B. Select the controller to which you need to download configuration. In this example, the Logix5550 controller is connected via an RS-232 DF1 device. C. Click Download. The window above uses a previously configured driver for the communication path to the controller.
3-12 Configure a ControlNet Module Use RSNetWorx for ControlNet Software You must use RSNetWorx for ControlNet software to schedule the network before the configured I/O devices in your application will become active. You must also reschedule the network if a change is made to an existing network that was already scheduled. Schedule a ControlNet Network for the First Time RSNetWorx software stores information in keeper devices.
Configure a ControlNet Module 3-13 Schedule the Network Offline The following instructions assume that: • your RSLogix 5000 project uses 1 controller and 1 network. We recommend that you use only one (1) 1756-CN2 or 1756-CNB module in the local chassis when scheduling the network offline. • your RSLogix 5000 project is complete but has not been downloaded to the controller. If your network has already been scheduled and you made a change to it, you must reschedule it.
3-14 Configure a ControlNet Module 2. On the RSNetWorx tab, name the new ControlNet file. A. Click on the RSNetWorx tab. B. Type the name of the new ControlNet file. C. Click Apply. 3. Because this is the first time you are scheduling the network, the file does not exist. When RSLogix 5000 software prompts you to create the new file, click Yes. Click Yes. This step creates the file that RSNetWorx for ControlNet software uses offline to browse and schedule network. 4.
Configure a ControlNet Module 3-15 5. The RSNetWorx for ControlNet software starts and creates a schedule that includes the devices in your RSLogix 5000 project. When the software prompts you to Optimize and re-write schedule for all connections, click OK. Click OK. Because you selected the Schedule the Network option in a previous step, RSNetWorx for ControlNet software automatically enables and disables edits before and after creating the schedule for the network respectively. 6.
3-16 Configure a ControlNet Module 8. Configure the network parameters as needed. A. Configure the network parameters. B. Click OK. The table Network Parameters for Scheduling the Network Offline describes the parameters used on this screen.
Configure a ControlNet Module 3-17 Table 3.4 Network Parameters for Scheduling the Network Offline Parameter Description Network Update Time (ms) The smallest user-configurable repetitive time cycle in milliseconds at which data can be sent on ControlNet. Max. Scheduled Address This is the node with the highest network address that can use scheduled time on a ControlNet link. I/O data is transferred during scheduled time. RSNetWorx for ControlNet software sets this value.
3-18 Configure a ControlNet Module 10. Save the file. A. Select Optimize and re-write schedule for all connections. B. Click OK. 11. Return to your RSLogix 5000 project to: a. save the project again. b. download configuration, as described in the section Download the Project to the Logix5000 Controller.
Configure a ControlNet Module 3-19 Schedule the Network Online The following instructions assume that all keepers are unconfigured or do not conflict with the current network. If your network has already been scheduled and you made a change to it, you must reschedule it. Refer to the section Reschedule a ControlNet Network That Has Previously Been Scheduled for more information. 1. Start RSNetWorx for ControlNet software. 2. Create a new ControlNet file. Click File > New. 3.
3-20 Configure a ControlNet Module 5. Select a communication path to the ControlNet network. A. Expand the tree to find your communication path. B. Select your communication path. C. Click OK. The window above uses a previously configured communication path to the controller. In this example, the computer is connected to the ControlNet network via a 1784-PCIC card. The driver was previously configured via RSLinx software, as described in the chapter Connect a Computer to the ControlNet Network. 6.
Configure a ControlNet Module 3-21 8. Access the network properties. A. Click Network. B. Click Properties. 9. Configure the network parameters. A. Configure the network parameters. B. Click OK. The table Network Parameters for Scheduling the Network Online describes the parameters used on this screen.
3-22 Configure a ControlNet Module Table 3.5 Network Parameters for Scheduling the Network Online Parameter Description Network Update Time (ms) The smallest user-configurable repetitive time cycle in milliseconds at which data can be sent on ControlNet. Max. Scheduled Address This is the node with the highest network address that can use scheduled time on a ControlNet link. I/O data is transferred during scheduled time.RSNetWorx for ControlNet software sets this value.
Configure a ControlNet Module 3-23 Reschedule a ControlNet Network That Has Previously Been Scheduled If you change a network that has already been scheduled, you must reschedule the network for the changes to take effect. For example, if you add I/O to an existing ControlNet network, you must reschedule the network for the I/O to become active. 1. Start RSNetWorx for ControlNet software. 2. Open the ControlNet file that matches the existing network. A. Click File. B. Click Open. C. Select the file. D.
3-24 Configure a ControlNet Module 4. Enable edits on the file. When you enable edits, the RSNetWorx for ControlNet software reads data in the ControlNet modules and builds a schedule for the network. Click Enable Edits. 5. Save the file. This will schedule and activate the network. A. Select Optimize and re-write schedule for all connections. B. Click OK. IMPORTANT It is always preferable to optimize connections. However, in some cases involving multiple controllers, the Merge changes...
Chapter 4 Control I/O Use This Chapter Read this chapter for: • 1756-CN2, 1756-CN2R modules • 1756-CNB, 1756-CNBR modules • 1769-L32C, 1769-L35CR controllers • 1784-PCICS, 1784-PKTCS cards • 1788-CNx cards • 1794-ACN15, -ACNR15 adapters • 1797-ACNR15 adapter This chapter describes how a controller controls distributed I/O over ControlNet. The controller requires a communication module to connect to the network. Distributed I/O modules require an adapter to connect to the network.
4-2 Control I/O Set Up the Hardware In this example, the Logix5000 controller uses a ControlNet communication module in the local chassis to connect to the ControlNet network. The distributed (remote) I/O has a ControlNet adapter to connect it to the ControlNet network. Data Local Chassis Logix5000 Controller With ControlNet Communication Module Distributed I/O ControlNet Adapter With I/O Modules Programming Terminal 43611 Make sure: • all wiring and cabling is properly connected.
Control I/O Select a Communication Format 4-3 When you configure a remote ControlNet communication module or an I/O module, you select a communication format. The communication format you choose determines the data structure for the tags that are associated with the module. Many I/O modules support different formats. Each format uses a different data structure.
4-4 Control I/O For I/O modules the available communication formats depend on the module type. This table describes the different communication formats for general module types. Table 4.
Control I/O 4-5 Direct or Rack Optimized Connection Logix5000 controllers use connections to transmit I/O data. These connections can be direct connections or rack optimized connections. This Term Means Direct Connection A direct connection is a real-time, data transfer link between the controller and an I/O module–analog or digital. This connection enables your controller to collect more data from an I/O module.
4-6 Control I/O Direct Connections for I/O Modules In this example, assume that each distributed I/O module is configured for a direct connection to the controller. Controller with ControlNet Communication Module ControlNet Network I/O I/O ControlNet Adapter with Digital I/O Modules I/O I/O I/O I/O ControlNet Adapter with Analog I/O Modules ControlNet Adapter with Digital I/O Modules This table calculates the connections in this example. Table 4.
Control I/O 4-7 Rack Optimized Connections for I/O Modules In this example, assume that each digital I/O module is configured for a rack optimized connection to the controller. Analog modules must be configured for direct connections.
4-8 Control I/O Ownership In a Logix5000 system, modules multicast data. This means that multiple controllers can receive the same data at the same time from a single module. When you choose a communication format, you have to choose whether to establish an owner or listen-only relationship with the module. Owner Controller The controller that creates the primary configuration and communication connection to a module.
Control I/O 4-9 Choose the Type of Ownership for a Module Table 4.
4-10 Control I/O Add Local and Remote ControlNet Modules Before you can connect to and control distributed I/O, you must add local and remote ControlNet communication modules. The type of distributed I/O determines your choice of a remote ControlNet adapter. For more information, see the table Choose the Appropriate Remote Adapter. Table 4.
Control I/O 4-11 To communicate with the I/O modules in your system, you add bridge, adapter, and I/O modules to the I/O Configuration folder of the controller. Within the I/O Configuration folder, you organize the modules into a hierarchy (tree/branch, parent/child). Add Distributed I/O For a Typical Distributed I/O Network Controller Local Communication Module Remote Adapter I/O Module Device You Build the I/O Configuration in This Order A. Add the local communication module (bridge). B.
4-12 Control I/O 3. Configure the distributed I/O module. Depending on the distributed I/O type, the configuration screens differ. The example below shows screen for a 1794-IB16XOB16P/A digital combo module. For more information on configuring distributed I/O modules over ControlNet, see the modules’ individual technical documentation and the RSLogix 5000 software online help. To Do This Use the module’s default configuration.
Control I/O 4-13 Table 4.8 Distributed I/O Formats Access Distributed I/O If You Select This Format For The Remote Adapter Select This Format For The Distributed I/O Module Rack Optimization Rack Optimization None an appropriate direct-connection format I/O information is presented as a structure of multiple fields that depend on the specific features of the I/O module. The name of the structure is based on the location of the I/O module in the system.
4-14 Control I/O I/O information is available in the Controller Tags portion of your RSLogix 5000 project. You can monitor or edit the tags. The example screens below show how to access the Controller Tags and some sample tags. Double-click on the Controller Tags portion of your RSLogix 5000 project. The screen above contains a tag named: Remote_FLEX_CNET_adapter:1:C.
Control I/O 4-15 The example below shows an I/O tree configured with a remote FLEX I/O adapter and four remote FLEX I/O modules. EXAMPLE Example 1 Example 2 Example 3 Example 4 Example 5 The table Example Tag Names describes some of the tag names that appear for these modules. The tags listed are not a complete list of the tags created for each module type.
4-16 Control I/O Table 4.9 Example Tag Names Example Module Example Tag Names (automatically created by the software) Example 1 remote 1794-ACN15 adapter “FLEX_adapter” FLEX_adapter:I FLEX_adapter:I.SlotStatusBits FLEX_adapter:I.Data FLEX_adapter:O FLEX_adapter:O.Data Example 2 remote 1794-IA16 FLEX_adapter:0:C FLEX_adapter:0:C.Config FLEX_adapter:0:C.
Control I/O Validate Connections 4-17 Verify that the controller can communicate with the devices that you have just configured. Do these steps: 1. Determine if communications has been established with the devices. a. If a ! is NOT over the I/O Configuration folder, the controller can communicate with the device. Connections are valid. b. If a ! is over the I/O Configuration folder, the controller cannot communicate with the device. Go to step 2. 2. Identify any faults.
4-18 Control I/O 3. Identify the fault code. If multiple faults appear on the screen, as shown above, identify the fault at the module that is highest in the I/O tree. A. Right-click on the fault module. B. Click Properties. C. Click on the Connection tab. D. Identify the code for the fault. E. Use the Help button to access the online help and determine what the fault codes mean. For more information on fault codes, see step 4 on page 4-19.
Control I/O 4-19 4. If necessary, get the definition of the fault code from the online help. A. Click Help. B. Click Contents C. Click on the Index tab. D. Type module faults. E. When the list of module fault codes appears, select the range for the code you just identified. F. Click Display. 5. Follow the recommendations for your fault code. 6. Return to the step: Determine if communications has been established with the devices.
4-20 Control I/O Notes: Publication CNET-UM001C-EN-P - November 2005
Chapter 5 Produce and Consume Tags (Interlock Controllers) Use This Chapter Read this chapter for: • 1756-CN2, 1756-CN2R modules • 1756-CNB, 1756-CNBR modules • 1769-L32C, 1769-L35CR controllers • 1784-PCICS, 1784-PKTCS cards • 1788-CNx cards This chapter describes how to interlock (produce and consume tags) controllers via a ControlNet network.
5-2 Produce and Consume Tags (Interlock Controllers) Set Up the Hardware Chassis #1 Logix5000 Controller with ControlNet Communication Module In this example, the controller in the first chassis produces a tag that is consumed by the controller in the second chassis.
Produce and Consume Tags (Interlock Controllers) 5-3 • the communication driver (such as., AB-PCICS-1) is configured for the programming workstation. TIP Determine Connections for Produced and Consumed Tags If you are only sharing tags between ControlLogix controllers (the controllers are not controlling any I/O modules), you can set the communication format of the 1756-CN2(R) or the 1756-CNB(R) module in the remote chassis to None. This reduces connection usage and network traffic.
5-4 Produce and Consume Tags (Interlock Controllers) This table describes each produced or consumed tag and the number of connections used. Table 5.
Produce and Consume Tags (Interlock Controllers) Organize Tags for Produced or Consumed Data 5-5 This table describes the guideline to follow as you organize your tags for produced or consumed data (shared data). Table 5.2 Guidelines for Produced or Consumed Data Tags Guideline Details Create the tags at the controller scope. You can only produce and consume controller-scoped tags. Produce and consume specific tags.
5-6 Produce and Consume Tags (Interlock Controllers) Guideline Details Combine data that goes to the same controller. If you are producing several tags for the same controller: • Group the data into one or more user-defined data types. (This uses less connections than producing each tag separately.) • Group the data according to similar update intervals. (To conserve network bandwidth, use a greater RPI for less critical data.
Produce and Consume Tags (Interlock Controllers) Produce a Tag 5-7 A Logix5000 controller can only produce controller-scoped user-created tags in the local controller’s tag structure. The Logix5000 controllers cannot produce I/O tags or tags aliased to I/O tags. Follow the steps below to produce a tag: 1. Open the RSLogix 5000 project that contains the tag that you want to produce. IMPORTANT You can only create produced tags when your RSLogix 5000 project is offline. 2.
5-8 Produce and Consume Tags (Interlock Controllers) 4. Access the tag properties. A. Right-click on the new tag name. B. Click on Edit Tag Properties. 5. Change the tag properties as needed. A. Choose the Produced Tag Type. B. Make sure the Data Type is one that the controller can produce A controller cannot produce a tag using the MSG [or INT] Data Type. C. Click on the Connection tab. D. Adjust the number of consumers.
Produce and Consume Tags (Interlock Controllers) Consume a Tag 5-9 Logix5000 controllers can only consume controller-scoped user-created tags from another controller’s tag structure. The Logix5000 controllers cannot consume I/O tags or tags aliased to I/O tags. Follow the steps below to consume a tag: IMPORTANT You can only create consumed tags when your RSLogix 5000 project is offline. 1. Open the RSLogix 5000 project that contains the controller that you want to consume the produced tag. 2.
5-10 Produce and Consume Tags (Interlock Controllers) 5. Access the tag properties. A. Right-click on the new tag name. B. Click on Edit Tag Properties. 6. Change the tag properties as needed. A. Choose the Consumed Tag Type. B. Make sure the Data Type and Data Style matches the Type and Style in the tag created in step 5 on page 5-8. C. Click on the Connection tab. D. Choose the Producer, the producing controller, from the pull-down menu.
Produce and Consume Tags (Interlock Controllers) 5-11 7. Use RSNetWorx for ControlNet software to schedule the network. IMPORTANT Your Logix5000 controller can consume a tag that was produced by any device that interfaces to ControlNet. However, when a non-Logix controller such as a PC using a 1784-PKTCS card, produces the tag that a Logix controller consumes, you must perform additional tasks in RSNetWorx for ControlNet.
5-12 Produce and Consume Tags (Interlock Controllers) Additional Steps for a PLC-5C or ControlNet Scanner Card Some devices connect to the ControlNet network via a ControlNet scanner and can use produced and consumed tags to share scheduled data with Logix5000 controllers. For example, you can connect a real-time control application, such as a Visual Basic application, to ControlNet through a 1784-PKTCS scanner card to exchange data with Logix5000 controllers.
Produce and Consume Tags (Interlock Controllers) 5-13 Use RSNetWorx to Produce a Tag from a ControlNet Scanner Use the RSNetWorx Scanlist Configuration tool to configure a ControlNet scanner to produce tags. In the example used for the following steps, a 2711P-RN15S ControlNet Scanner module located in a PanelView Plus terminal produces a tag for a ControlLogix controller to consume. 1. Open the RSNetWorx for ControlNet file for your project. 2. Go online. A. Click Network. B. Click Online. 3.
5-14 Produce and Consume Tags (Interlock Controllers) 5. Insert a Target for Connections on the ControlNet scanner that is producing the tag. A. Right-click on the ControlNet scanner device. B. Click Insert Target for Connections.... 6. When the Insert Target for Connections pop-up menu appears, make sure it is configured correctly. A. Choose Send Data. B. Make sure the Produce Buffer ID equals the Remote Data, the tag name or instance value for the consumed tag in RSLogix 5000 software. C.
Produce and Consume Tags (Interlock Controllers) 5-15 Use RSNetWorx to Consume a Tag by a ControlNet Scanner You must use the RSNetWorx Scanlist Configuration tool to configure a ControlNet scanner to consume tags. In the example used for the following steps, a 2711P-RN15S ControlNet Scanner module located in a PanelView Plus terminal consumes a tag produced by a ControlLogix controller. 1. Open the RSNetWorx for ControlNet file for your project. 2. Go online. A. Click Network. B. Click Online. 3.
5-16 Produce and Consume Tags (Interlock Controllers) 5. Insert a connection to the Logix5000 controller that will consume the tag that the ControlNet scanner produces. A. Right-click on the Logix5000 controller. B. Click Insert Connection. 6. When the Connection Properties pop-up menu appears, make sure the Connection tab is configured correctly. A. Choose Receive Data. B. Type Tag in the Name field. C.
Produce and Consume Tags (Interlock Controllers) 5-17 When you are using a PLC-5C controller or a ControlNet scanner to consume tags, keep the following in mind about the Input Size field: • If the scanner is consuming a DINT, in the Input Size field, enter two times the number of DINTs you need to read from the produced tag. For example, if the produced tag contains 10 DINTs, enter 20 for the Input size; the input size must be an even number.
5-18 Produce and Consume Tags (Interlock Controllers) The following example shows how to re-construct a REAL (floating point value) in the PLC-5C controller EXAMPLE Re-construct a floating point value. This example takes two consumed integers that were originally a produced REAL, reverses the order of the integers and assembles them into a floating point value equal to the original REAL. The two MOV instructions reverse the order of the integers and move them to a new location.
Chapter 6 Peer-to-Peer Messaging Use This Chapter Read this chapter for: • 1756-CN2, 1756-CN2R modules • 1756-CNB, 1756-CNBR modules • 1769-L32C, 1769-L35CR controllers • 1784-PCIC, 1784-PCICS, 1784-PKTCS cards • 1788-CNx cards This chapter describes how to use MSG instructions to send data to and receive data from other modules on a ControlNet network.
6-2 Peer-to-Peer Messaging Set Up the Hardware In this example, the controller in the local chassis sends a message (using a MSG instruction) to another module (which can be a controller) on the ControlNet network.
Peer-to-Peer Messaging 6-3 The destination for the message can be any of the following: • PLCs, SLC or Logix5000 controllers on ControlNet or other networks • I/O modules, such as ControlLogix analog module configuration data on ControlNet or other networks IMPORTANT The 1769-L32C and 1769-L35CR controllers can produce and consume tags over ControlNet to other Logix5000 controllers.
6-4 Peer-to-Peer Messaging Guidelines for MSG Instructions Guideline 1. For each MSG instruction, create a control tag. This table describes guidelines to use when working with message instructions. Table 6.1 Guidelines for MSG Instructions Details Each MSG instruction requires its own control tag. This tag contains control elements for messages, for example: DN and EN, error codes and information to execute the message such as destination path and number of words to transfer.
Peer-to-Peer Messaging Determine Connections for Messages 6-5 Messages transfer data to other modules, such as other controllers, I/O modules or operator interfaces. Each message uses one connection, regardless of how many modules are in the message path. To conserve connections, you can configure one message to read from or write to multiple modules.
6-6 Peer-to-Peer Messaging To send or receive data from a ControlNet module via a message, you must program a MSG instruction in the local controller’s logic. If the target module is configured in the I/O Configuration folder of the controller, you can browse to select the module. Otherwise, you can manually enter the message path in the MSG instruction.
Peer-to-Peer Messaging 6-7 Enter a Message Use relay ladder logic to enter a MSG instruction. Click MSG instruction. EXAMPLE to configure the Enter a MSG instruction If user_bit and count_messages.EN = 0 (MSG instruction is not already enabled), then execute a MSG instruction that sends data to another controller. TIP We recommend an XIO of the MSG control block tag.en, for example: the count_messages.
6-8 Peer-to-Peer Messaging 2. On the Configuration tab, specify the type of MSG instruction: A. Choose a Message Type. B. Depending on the Message Type, you have additional parameters to configure. For more information on how to configure the various Message types, see the tables Message Type to Configure a MSG to Logix5000 Controller, Message Type to Configure a MSG to an SLC 500 Processor, and Message Type to Configure a MSG to a PLC-5 Processor.
Peer-to-Peer Messaging 6-9 Table 6.5 Message Type to Configure a MSG to Logix5000 Controller If You Want To For This Item Type or Select write (send) the data Message Type CIP Data Table Write Source Tag first element of the tag (controller-scoped) in this controller that contains the data Number of Elements number of elements to transfer Destination Element first element of the tag for the data in the other controller Message Type to Configure a MSG to an SLC 500 Processor Table 6.
6-10 Peer-to-Peer Messaging Message Type to Configure a MSG to a PLC-5 Processor Table 6.
Peer-to-Peer Messaging EXAMPLE 6-11 Communication path from a Logix5000 controller to a PLC5 controller over a ControlNet network ControlNet Network Node Address = 1 Node Address = 7 5 5 5 0 C N 2 Message PLC5-C Path = 1, 1, 2, 1 Where Indicates 1 connection to the backplane in local chassis 1 slot number of 1756-CN2 module in local chassis 2 connection to port 2 of the 1756-CN2 module (get on ControlNet) 1 node address of remote PLC5 Publication CNET-UM001C-EN-P - November 2005
6-12 Peer-to-Peer Messaging Communicate with PLC-5 or SLC 500 Processors If the message is to a PLC-5 or SLC 500 processor and it reads or writes integers (not REALs), use a buffer of INTs in the message. • Logix5000 controllers execute more efficiently and use less memory when working with 32-bit integers (DINTs). • PLC-5 and SLC 500 processors require 16-bit integers. • Use an INT buffer in the message and move the data to or from DINTs as needed.
Peer-to-Peer Messaging 6-13 Figure 6.1 Configure the Message A. Select either a PLC5 Typed Read or PLC5 Typed Write for the Communication Command. B. Type the starting address of the data in the PLC-5 controller. C. Type the number of elements to read or write. D. Select Port Number 2 for ControlNet. E. Type, in quotation marks, the tag name of the Logix5000 tag.
6-14 Peer-to-Peer Messaging Map Tags A Logix5000 controller stores tag names on the controller so that other devices can read or write data without having to know physical memory locations. Many products only understand PLC/SLC data tables formatting, so the Logix5000 controller offers a PLC/SLC mapping function that lets you map Logix tag names to memory locations.
Peer-to-Peer Messaging 6-15 Follow these steps to map tags: 1. If the RSLogix 5000 project is online, go offline. You can only map tags when the project is offline. 2. Access the PLC/SLC Mapping screen. A. Click Logic. B. Click Map PLC/SLC Messages. 3. Configure the PLC/SLC Mapping as needed. A. Type the File Number. B. Type the corresponding Tag Name from the RSLogix 5000 project. When mapping tags: • Do not use file numbers 0, 1, and 2.
6-16 Peer-to-Peer Messaging Stagger the Messages As you add messages to your project, you may have to coordinate the execution of the messages. To avoid errors and assure that each message is processed, follow these rules: Rule 1 Enable no more than 16 messages at one time (including block transfers).
Peer-to-Peer Messaging 6-17 Route a ControlNet Message To send a message from a PLC-5C controller to a PLC-5C controller on a different ControlNet network: IMPORTANT This section uses RSLogix 5 software, revision 3.x or greater and PLC-5C Series C/Revision M, Series D/Revision C, Series E/Revision B, Series F/Revision A or greater 1. Open the RSLogix 5 project for the PLC-5 controller that sends the message. 2. Display the set-up screen for the message. Double-click on Set up Screen. 3.
6-18 Peer-to-Peer Messaging 4. Configure the MultiHop tab. A. Click on the MultiHop tab. B. Type the ControlNet node number of the 1756-CN2 module that is on the same ControlNet network as the controller that sends the message. C. Type the slot number of the 1756-CN2 module that is on the other network. 5. Select the ControlLogix backplane row. 6. Press Insert to add a hop. 7. Configure the new hop. A. Select 1756-CN2 or 1756-CNB. B.
Chapter 7 Communicate with PanelView and RSView Products Use This Chapter Read this chapter for: • 1756-CN2, 1756-CN2R modules • 1756-CNB, 1756-CNBR modules • 1769-L32C, 1769-L35CR controllers • 1784-PCIC, 1784-PCICS, • 1784-PKTCS cards 1788-CNx cards Set Up the Hardware This chapter describes how a controller uses a ControlNet communication module to communicate with PanelView and RSView software products over a ControlNet network.
7-2 Communicate with PanelView and RSView Products The Logix5000 controller in the local chassis can be any of the following, with their ControlNet communication modules: • 1756 ControlLogix controller with a 1756-CN2 or 1756-CN2R communication module in the chassis • 1756 ControlLogix controller with a 1756-CNB or 1756-CNBR communication module in the chassis • 1769-L32C or 1769-L35CR CompactLogix controller • 1789 SoftLogix controller with a 1784-PCIC, 1784-PCICS or 1784-PKTCS communication card • 1794
Communicate with PanelView and RSView Products 7-3 We recommend the following when you use PanelView terminals with Logix5000 controllers over ControlNet: • PanelView Standard terminals – A maximum of 4 PanelView Standard terminals can request data from a Logix5000 controller.
7-4 Communicate with PanelView and RSView Products 3. Select the local ControlNet communication module type from the Select Module Type pop-up. The example below uses a 1788-CNC card. A. Select the local ControlNet communication module. B. Click OK. The table ControlNet communication Modules Available Locally lists the ControlNet communication modules available locally (in the local chassis, computer or controller) with each Logix5000 controller. Table 7.
Communicate with PanelView and RSView Products 7-5 5. Add a PanelView terminal to the project. A. Right-click on the local communication module. B. Select New Module. 6. Select the PanelView terminal for your project. A. Select the PanelView terminal. B. Click OK.
7-6 Communicate with PanelView and RSView Products 7. Configure the terminal. Organize Controller Data for a PanelView Terminal Organize data for a PanelView or PanelView Plus terminal based on how the data is used. For Data That Is Do This Time-critical (scheduled data) PanelView terminals only Use the I/O tags of the terminal. The terminal supports a maximum of 32 input tags and 32 output tags.
Communicate with PanelView and RSView Products 7-7 To access the scheduled I/O tags of the PanelView terminal, use the following address format: If The Terminal Then Use This Address writes the data name_of_terminal:I.Data[x].y reads the data name_of_terminal:O.Data[x].y where: Determine Connections to RSView Applications This Address Variable Is name_of_terminal name of the instance in the I/O configuration of the controller x element of the input (I) or output (O) structure.
7-8 Communicate with PanelView and RSView Products Notes: Publication CNET-UM001C-EN-P - November 2005
Chapter 8 Troubleshoot Your ControlNet Communication Modules Use This Chapter 1 This chapter provides descriptions for status indicators used on the ControlNet communication modules and adapters and how to use those indicators to troubleshoot your application.
8-2 Troubleshoot Your ControlNet Communication Modules 1756-CN2 and 1756-CN2R ControlNet Communication Modules This figure shows the status indicators used on the 1756-CN2 and 1756-CN2R modules. Figure 8.
Troubleshoot Your ControlNet Communication Modules If the OK Indicator Is With This Module Status Display It Means Red Msg scrolls(1) Module’s network address is set to 00, an invalid ControlNet address. See footnote at end of table. 8-3 Take This Action 1. Optional – Turn chassis power supply off. 2. Remove the module from the chassis. 3. Set the network address switches to a unique address (01 to 99) 4. Install the module in the chassis. 5. If off, turn chassis power supply on.
8-4 Troubleshoot Your ControlNet Communication Modules If the OK Indicator Is Flashing Green (1) With This Module Status Display It Means Take This Action SW ERR Node address switch changed after power-up. None required, but we recommend that you either return switches to their original settings or replace the module, since this could indicate a latent hardware problem. OK Normal operation. No connections to or through the module. No action required CNFG ERR ControlNet configuration error.
Troubleshoot Your ControlNet Communication Modules 8-5 This table describes the 1756-CN2 and 1756-CN2R network channel status indicators. Table 8.2 1756-CN2 and 1756-CN2R Network Channel Status Indicators If Both Channel Status Indicators Are It Means Take This Action Off No power Apply power. Steady red Faulted module 1. Cycle power to the module. 2. If fault persists, contact your Rockwell Automation representative or distributor.
8-6 Troubleshoot Your ControlNet Communication Modules 1756-CNB and 1756-CNBR ControlNet Communication Modules This figure shows the status indicators used on the 1756-CNB and 1756-CNBR modules. Figure 8.
Troubleshoot Your ControlNet Communication Modules If The OK Indicator Is With This Module Status Display It Means Steady red Msg scrolls(1) Module’s network address is set to 00, an invalid ControlNet address, or 99, an invalid ControlNet address if you are using redundant control. See footnote at end of table. 8-7 Take This Action 1. Optional – Turn chassis power supply off. 2. Remove the module from the chassis. 3.
8-8 Troubleshoot Your ControlNet Communication Modules If The OK Indicator Is With This Module Status Display It Means Take This Action Flashing red BOOT Module has invalid firmware. Update module firmware with ControlFlash Update Utility. ROM Flash update is in progress. None required. SNGL KPR! Module detected that it has been connected to a Cnet 1.0 or 1.25 (single-keeper) network. Update the firmware of module at node address 01 and reschedule the network.
Troubleshoot Your ControlNet Communication Modules 8-9 If The OK Indicator Is With This Module Status Display It Means Take This Action Steady green or off SO_1 Old primary switchover phase 1 in progress. SO_2 Old primary switchover phase 2 in progress. SO_3 Old primary switchover phase 3 in progress. SN_1 New primary switchover phase 1 in progress. If the display shows any message for more than three seconds, then the CNB module failed during transition from one redundancy phase to another.
8-10 Troubleshoot Your ControlNet Communication Modules This table describes the 1756-CNB and 1756-CNBR network channel status indicators. Table 8.4 .1756-CNB and 1756-CNBR Network Channel Status Indicators If Both Channel Status Indicators Are It Means Take This Action Off No power Apply power. Steady red Faulted module 1. Cycle power to the module. 2. If fault persists, contact your Rockwell Automation representative or distributor.
Troubleshoot Your ControlNet Communication Modules 1769-L32C and 1769-L35CR CompactLogix Controllers 8-11 This figure shows the status indicators used on the 1769-L32C and 1769-L35CR CompactLogix controller. Figure 8.
8-12 Troubleshoot Your ControlNet Communication Modules Interpret Status Indicators Use the following status indicators to determine how your CompactLogix 1769-L32C or 1769-L35CR controller is operating on the ControlNet network: • Module Status • Network Channel Status These status indicators provide information about the controller and the network when the controller is connected to ControlNet via the BNC connectors. describes the possible conditions for module and network status indicators.
Troubleshoot Your ControlNet Communication Modules 8-13 Module Status (MS) indicator This table describes the 1769-L32C and 1769-l35CR CompactLogix controller module status indicators. Table 8.5 1769-L32C and 1769-L35CR CompactLogix Controller Module Status Indicators If The Module Status (MS) Indicator Is It Means Take This Action Off The controller has no power. Apply power. The controller is faulted. Make sure that the controller is properly installed.
8-14 Troubleshoot Your ControlNet Communication Modules Network Channel Status Indicators Channel B is only labelled on the 1769-L35CR controller. The 1769-L32C controller only has channel A but uses the second indicator in some LED patterns as described in (Table 10)Need CR. This table describes the 1769-L32C and 1769-l35CR CompactLogix network channel status indicators. Table 8.
Troubleshoot Your ControlNet Communication Modules 1784-PCIC, 1784-PCICS and 1784-PKTCS ControlNet PCI Cards 8-15 This figure shows the status indicators used on the 1784-PCIC, 1784-PCICS and 1784-PKTCS cards. Figure 8.4 1784-PCIC, 1784-PCICS and 1784-PKTCS Channel Status indicators Network Channel Status Indicators 43609 The status indicators on the card give you information about the card and the ControlNet network when you are connected via the BNC connectors.
8-16 Troubleshoot Your ControlNet Communication Modules Table 8.7 1784-PCIC, 1784-PCICS and 1784-PKTCS Network Channel Status Indicators If Both Channel Status It Means Indicators Are Off No power 1784-PCIC(S) driver not started Steady red Alternating red/green Alternating red/off Apply power. 1. Start RSLinx software. 2. Verify that the appropriate driver has been configured properly in RSLinx software. 1784-PKTCS driver is not installed or the card is Install the driver and/or configure the card.
Troubleshoot Your ControlNet Communication Modules 8-17 This figure shows the status indicators used on the 1788-CNC and 1788-CNCR cards. 1788-CNC, 1788-CNCR, 1788-CNF and 1788-CNFR ControlNet Daughtercards Figure 8.
8-18 Troubleshoot Your ControlNet Communication Modules Module and I/O Status Indicator Interpretation Status indicators provide information about the card and the network when you are connected via the BNC connectors. • Steady - indicator is on continuously in the defined state. • Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators when viewed together); the two indicators are always in opposite states, out of phase.
Troubleshoot Your ControlNet Communication Modules 8-19 This table describes the 1788-CNC, 1788-CNCR and 1788-CNF module and I/O status indicators. Table 8.8 1788-CNC, 1788-CNCR and 1788-CNF Module and I/O Status Indicators If The Module Status (MS) Indicator Is It Means Take This Action Off No power Apply power. Host is faulted Make sure that the daughtercard is firmly seated in the slot. Host is holding daughtercard in reset 1. Cycle power. 2.
8-20 Troubleshoot Your ControlNet Communication Modules Network Channel Status Indicator Interpretation IMPORTANT When you connect the module to a ControlNet network using only the NAP, the LEDs are meaningless. • Steady - indicator is on continuously in the defined state. • Alternating - the two indicators alternate between the two defined states at the same time (applies to both indicators viewed together). The two indicators are always in opposite states, out of phase.
Troubleshoot Your ControlNet Communication Modules 1794-ACN15 and 1794-ACNR15 ControlNet FLEX I/O Adapters 8-21 This figure shows the status indicators used on the 1794-ACN15 and 1794-ACNR15 modules. Figure 8.6 1794-ACN15 and 1794-ACNR15 Status Indicators 43610 Network Channel Status Indicators Module Status Indicators This graphic shows a 1794-ACNR15.
8-22 Troubleshoot Your ControlNet Communication Modules If Either Channel Status Indicators Are It Means Take This Action Off No power Apply power. Steady red Faulted module 1. Cycle power. 2. If the fault persists, contact your Rockwell Automation representative or distributor. Alternating red/green The module is performing a self-test None Alternating red/off Incorrect node configuration Check the module’s network address and other ControlNet configuration parameters.
Troubleshoot Your ControlNet Communication Modules 1797-ACNR15 ControlNet FLEX Ex Redundant Media I/O Adapter 8-23 This figure shows the status indicators used on the 1797-ACNR module. Figure 8.7 1797-ACNR15 Status Indicators Network Channel Status Power Module Status 41412 The modules use the following 2 status indicators: • Comm - Communication status indicator for each channel • Status - Module status indicator This table describes the 1797-ACNR15 communication status indicators. Table 8.
8-24 Troubleshoot Your ControlNet Communication Modules If Either Channel Status Indicators Are It Means Take This Action Off No power Apply power. Steady red Faulted module 1. Cycle power. 2. If the fault persists, contact your Rockwell Automation representative or distributor. Alternating red/green The module is performing a self-test None Alternating red/off Incorrect node configuration Check the module’s network address and other ControlNet configuration parameters.
Appendix A Connection Use Over ControlNet Use This Appendix Read this chapter for: • 1756-CN2, 1756-CN2R modules • 1756-CNB, 1756-CNBR modules • 1769-L32C, 1769-L35CR controllers • 1784-PCC, 1784-PCIC, 1784-PCICS, ControlNet communication modules use connections to manage communication. A connection is a point-to-point communication mechanism that transfers data between a transmitter and a receiver.
A-2 Connection Use Over ControlNet The Logix5000 controller supports 250 connections. But the limit of connections ultimately resides in the communication module you use for the connection. If a message path routes through a communication module or card, the connection related to the message also counts towards the connection limit of the communication module or card. Connected Messaging Limits Table A.
Connection Use Over ControlNet Product Connected Messaging Limits 1788-CNx Each module supports 32 connections, of which 22 connections can be scheduled connections.
A-4 Connection Use Over ControlNet Notes: Publication CNET-UM001C-EN-P - November 2005
Appendix B ControlNet Overview This chapter defines some basic ControlNet concepts and how the ControlNet network is used for control. Understand the ControlNet Network ControlNet is a real-time control network that provides high-speed transport of both time-critical I/O and interlocking data and messaging data, including upload/download of programming and configuration data on a single physical media link.
B-2 ControlNet Overview Exchange Information on ControlNet ControlNet communication modules use a message-based protocol that implements a relative path to send a message from the producing module in a system to the consuming modules. This protocol also allows you to communicate between devices on ControlNet and DeviceNet or EtherNet/IP without writing additional application code.
ControlNet Overview B-3 A ControlNet link’s most important function is to transport time-critical control information, such as I/O data and control interlocking. Other information (non-time-critical messages such as program uploads and downloads) is also transported but does not interfere with time-critical messages because of ControlNet’s transmission of scheduled and unscheduled data. On a ControlNet link, information is transferred between nodes by establishing connections.
B-4 ControlNet Overview Network Update Time (NUT) The network update time (NUT) is the smallest repetitive time interval in which data can be sent on the ControlNet network. It represents the fastest possible update rate for scheduled data transfers on that network. For example, a network that runs with a 5ms NUT cannot send scheduled data at a rate faster than 5ms. It can, however, send data at a slower rate. The minimum NUT you can specify is 2ms. The NUT is divided into three parts: Table B.
ControlNet Overview B-5 how often to produce the data for that module. For example, if you specify an RPI of 50ms, every 50ms the I/O module sends its data to the controller and/or the controller sends its data to the I/O module. Set the RPI only as fast as needed by the application. The RPI also determines the number of packets per second that the module will handle on a connection. Each module has a limit of how many packets it can handle per second.
B-6 ControlNet Overview Table B.2 NUT Example Data Rates With this NUT And this multiple 5ms The Module Can Send Data at this Rate 1 5ms 2 10ms 4 20ms 8 40ms 16 80ms 32 160ms 64 320ms 128 640ms In our example, if you specify an RPI of 25ms, then the network produces an API of 20ms, which is the next fastest rate at which the module can send data. The module places the data on the network at every fourth network update interval to produce the 20ms API.
ControlNet Overview B-7 Control of Scheduled I/O Scheduled connections allow you to send and to receive data repeatedly at a predetermined rate. You can use the 1756-CNB or the 1756-CN2 module to control scheduled I/O when you use it in conjunction with a ControlLogix controller.
B-8 ControlNet Overview Understand the Network Keeper Every ControlNet network requires at least one module that stores programmed parameters for the network and configures the network with those parameters at start-up. This module is called a “keeper” because it keeps the network configuration. RSNetWorx for ControlNet software configures the keeper. To avoid a single point of failure, ControlNet supports multiple redundant keepers.
ControlNet Overview B-9 To see a list of valid keeper devices on your network, do the following steps: 1. Go online in RSNetWorx for ControlNet software. 2. Access the Keeper Status for the network. A. Click Network. B. Click Keeper Status. The Keeper Status screen appears with a list of all nodes on the network and indications of whether the nodes are: • Keeper Capable Nodes • Active Keeper • Valid Keepers The screen below shows an example of the Keeper Status screen.
B-10 ControlNet Overview Default Parameters When a ControlNet network is powered-up for the first time, it comes up with a default set of ControlNet parameters capable of sending only unscheduled data. The default set of network parameters in all ControlNet devices, is: • Network Update Time (NUT) = 100ms • Scheduled Maximum Node Address (SMAX) = 0 The SMAX is the highest network address of a node that can use the scheduled service.
ControlNet Overview ControlNet Capacity and Topology B-11 When planning a ControlNet network, you should consider the following: • • • • topology number of nodes distances connections Topology ControlNet supports a variety of topologies, including trunkline/dropline, star, tree, and ring redundancy. In its simplest form, ControlNet is a trunkline, to which you connect nodes with a tap and a 1-meter dropline, as shown in the figure Example ControlNet System Trunkline/Dropline Topology.
B-12 ControlNet Overview Figure B.2 Example ControlNet System Trunkline/Dropline Topology Tap with Dropline Trunkline Node Node Node Node 43620 Figure B.
ControlNet Overview B-13 Figure B.
B-14 ControlNet Overview Number of Nodes Each ControlNet network supports up to 99 nodes. Logix5000 controllers support multiple ControlNet networks, giving you the flexibility to add more nodes to your ControlNet network, or to boost performance. Distances In a ControlNet network, the maximum distance depends on the number of nodes on a segment; a segment is a section of trunk between 2 terminators. Use repeaters to add more segments or gain more distance.
Appendix C Determine Your ControlNet Media Requirements Use This Appendix Use this appendix to determine your network media requirements.
C-2 Determine Your ControlNet Media Requirements Design a ControlNet Media System The design of a ControlNet media system is a process of measurement and judgement. The objective is to select the ControlNet media that will serve as the foundation for the network operations.
Determine Your ControlNet Media Requirements C-3 ControlNet Media Components ControlNet network media components provide flexibility when designing a communication network for a particular application. A ControlNet network consists of a combination of the media components listed in the following table. Table C.1 ControlNet Media Components Component Definition Trunk cable A bus or central part of a network media system that serves as a communication channel between any two points on a network.
C-4 Determine Your ControlNet Media Requirements Determine How Many Taps You Need The number of taps you need depends on the number of devices you want to connect to the network. You need a tap for each node and fiber hub on a segment. If you plan to add nodes at a later date, you should consider ordering and installing the cable and connectors for these additional nodes when you install the initial network. This will minimize disruption to the network during operation.
Determine Your ControlNet Media Requirements C-5 These tap kits are available: Figure C.2 Available Tap Kits Straight T-taps Straight Y-tap Right-angle T-tap Right-angle Y-tap 41330 1786-TCT2BD1 Connect Programming Devices 1786-TPS 1797-TPS 1786-TPYS 1797-TPYS 1786-TPR 1797-TPR 1786-TPYR 1797-TPYR Programming devices in non-hazardous areas may be connected to the ControlNet cable system through a 1784-PCIC, 1784-PCICS or 1784-PCC communication card.
C-6 Determine Your ControlNet Media Requirements Determine What Type of Cable You Need There are several types of RG-6 quad shield cable that may be appropriate for your installation, depending on the environmental factors associated with your application and installation site. IMPORTANT You should install all wiring for your ControlNet cable system in accordance with the regulations contained in the National Electric Code (or applicable country codes), state codes, and applicable municipal codes.
Determine Your ControlNet Media Requirements Determine Trunk Cable Section Lengths C-7 A segment is comprised of several sections of trunk cable separated by taps between 75Ω terminators. The total cable length of a segment is equal to the sum of all of the trunk-cable sections. Figure C.
C-8 Determine Your ControlNet Media Requirements The total allowable length of a segment containing standard RG-6 quad shield cable depends upon the number of taps in your segment. There is no minimum trunk-cable section length requirement. The maximum allowable total length of a segment is 1,000 m (3280 ft) with two taps connected. Each additional tap decreases the maximum length of the segment by 16.3 m (53 ft).
Determine Your ControlNet Media Requirements C-9 The amount of high-flex RG-6 cable you can use in a system is less than the amount of standard RG-6 cable due to higher attenuation, so you should keep high-flex cable use to a minimum. Use BNC bullet connectors to isolate areas that require high-flex RG-6 cable from areas that require standard RG-6 cable; this allows the high-flex RG-6 section to be replaced before flexture life is exceeded.
C-10 Determine Your ControlNet Media Requirements You can install repeaters on a segment to increase the total trunk-cable length or number of taps. This creates another segment. You need to install repeaters if your system requires more than 48 taps per segment, or a longer trunk cable than the specifications allow.
Determine Your ControlNet Media Requirements Determine How Many Trunk Terminators You Need C-11 You must use 75Ω trunk terminators (cat. nos. 1786-XT and 1797-XT) to terminate each segment for the ControlNet cable system. You need two XT terminators per segment because you need one for each end of the segment.
C-12 Determine Your ControlNet Media Requirements Install Repeaters In Series When you install repeaters in series, you can install a maximum of 20 repeaters (or 21 segments) to form a link. In the link below: • there are 3 repeaters in series (A, B and C) • segments 1 and 4 each have 2 taps and each = 1000 m (3280 ft) maximum length • segments 2 and 3 each have 3 taps and each = 983.7 m (3226.6 ft) maximum length Figure C.
Determine Your ControlNet Media Requirements C-13 Install Repeaters In Parallel When you install repeaters in parallel, you can install a maximum of 48 repeaters (the maximum number of taps per 250 m segment) to form a link. shows an example of repeaters used in parallel. Figure C.6 Repeater A Repeater B Repeater C Segment 1 Repeater D Segment 2 Segment 3 42307 Device 1 Device 2 Device 3 Repeaters A and B are in parallel off of segment 1.
C-14 Determine Your ControlNet Media Requirements Install Repeaters In A Combination Of Series And Parallel You can install repeaters in a combination of series and parallel connections following the guidelines listed for each to form a link. For mixed topologies (series and parallel) the maximum number of repeaters in series between any two nodes is twenty. Figure C.
Determine Your ControlNet Media Requirements Determine What Type of Connectors You Need C-15 Depending on the type of connection you need to make, you can select from multiple Rockwell Automation ControlNet connectors.
C-16 Determine Your ControlNet Media Requirements ATTENTION IMPORTANT Do not let any metallic surfaces on the BNC connectors, plugs, or optional accessories touch grounded metallic surfaces. This contact could cause noise on the network. All exposed metal must be covered with either intrinsically safe blue sheaths or another form of sufficient insulation.
Determine Your ControlNet Media Requirements C-17 You can run a second trunk cable between your ControlNet nodes for redundant media. With redundant media, nodes send signals on two separate segments. The receiving node compares the quality of the two signals and accepts the better signal to permit use of the best signal. This also provides a backup cable should one cable fail.
C-18 Determine Your ControlNet Media Requirements Observe these guidelines when planning a redundant media system in a hazardous area. • Route the two trunk cables (trunk cable A and trunk cable B) differently to reduce the chance of both cables being damaged at the same time. • Each node on a redundant-cable link must support redundant coax connections and be connected to both trunk cables at all times.
Determine Your ControlNet Media Requirements C-19 Figure C.9 Segment 1 Trunk Cable A = Terminators Terminators Trunk Cable B = Repeater B Node Node Repeater A Node Node Trunk Cable B = Trunk Cable A = Terminators Terminators Segment 2 43630 To use redundant media, all nodes must support redundant media. IMPORTANT Make sure you do not mix A and B cable connections in a redundant operations.
C-20 Determine Your ControlNet Media Requirements Application Considerations The guidelines in this section coincide with the guidelines for “the installation of electrical equipment to minimize electrical noise inputs to controllers from external sources” in IEEE standard 518-1982. When planning your cable system there are certain installation considerations depending on your application. There are three categories of conductors: Table C.
Determine Your ControlNet Media Requirements C-21 General Wiring Guidelines Follow these guidelines with regard to noise coupling. Intrinsic safety requirements should prevent most or all of these situations from occurring. They are provided as a general reference for wiring. • If it must cross power feed lines, it should do so at right angles. • Route at least 1.5 m (5 ft) from high-voltage enclosures, or sources of rf/microwave radiation.
C-22 Determine Your ControlNet Media Requirements Wire Inside Enclosures Cable sections that run inside protective equipment enclosures are relatively short. As with wiring external to enclosures, you should maintain maximum separation between your ControlNet cable and Category-1 conductors. When you are running cable inside an enclosure, route conductors external to all raceways in the same enclosure, or in a raceway separate from Category-1 conductors. Table C.
Determine Your ControlNet Media Requirements Order Components C-23 Now that you are ready to begin ordering components, use these guidelines to help you select components. General Planning The ControlNet cable system is isolated from earth and must be protected from inadvertent ground connections.
C-24 Determine Your ControlNet Media Requirements Notes: Publication CNET-UM001C-EN-P - November 2005
Appendix D Control 1771 I/O Over ControlNet Use This Appendix Use this appendix to monitor and control I/O devices that are wired to 1771 I/O modules when a: • 1756-CN2(R) or the 1756-CNB(R) module connects the local chassis to a ControlNet network. • 1771-ACN(R)15 adapter connects the 1771 I/O modules to the same ControlNet network.
D-2 Control 1771 I/O Over ControlNet Add the Local 1756-CN2(R) or 1756-CNB(R) Module For more information on how to do this, see the section Add Local and Remote ControlNet Modules in the chapter Control I/O. Add the 1771-ACN(R)15 Module To transfer discrete data between remote 1771 I/O and the ControlLogix controller in the local chassis (via the 1756-CN2(R), 1756-CNB(R) module), you need to add a remote 1771-ACN(R)15 ControlNet adapter to the I/O configuration. 1. Add the 1771-ACN(R)15 module. A.
Control 1771 I/O Over ControlNet D-3 2. Configure the 1771-ACN(R)15 module. E. Select the module’s node number on ControlNet. A. Name the module. B. Select a Comm Format. For more information on choosing a Comm Format, see section Communication Format. F. Select the Input Size. G. Select the Output Size. C. Select the module’s Revision level. H. Click Next. D. Select an Electronic Keying level. For more information on choosing a keying level, see table Electronic Keying Options. I. Set the RPI rate.
D-4 Control 1771 I/O Over ControlNet Read or Write Data To or From a Block Transfer Module Via a Message Instruction Use this procedure to transfer data to or from a module that requires block transfers. Use an INT buffer in the message and move the data into or out of the buffer as needed because DINTs can increase the program scan. Read Data From a Block Transfer Module 1.
Control 1771 I/O Over ControlNet D-5 Configure the Message 1. In the MSG instruction, click ... . 2. Configure the message as shown below. A. Select a Block Transfer Read message type. B. Select the number of elements to read. In this case, the number of elements is the number of INTs to read. C. Select the tag to hold the data that is read. D. Use the Browse button to select a path for the message.
D-6 Control 1771 I/O Over ControlNet Write Configuration or Output Data To a Block Transfer Module 1. To read data from a block transfer module, enter the following rung of ladder logic: The MSG instruction sends the data in int_buffer_write to the module. This table describes the tags used in this message Table D.
Control 1771 I/O Over ControlNet D-7 Configure the Message 1. In the MSG instruction, click ... . 2. Configure the message as shown below. A. Select a Block Transfer Write message type. B. Select the tag where the data is written from; the tag should be INT. C. Select the number of elements to write. D. Use the Browse button to select a path for the message. To use this method, you must make sure the remote 1771 adapter was added to your project’s I/O configuration. E. Select ControlNet. F.
D-8 Control 1771 I/O Over ControlNet Address I/O To monitor or control discrete 1771 I/O devices, assign the tag name of the device to an instruction in your logic: • For step-by-step instructions on how to enter logic and tag names, refer to the Logix5000 Controllers Common Procedures, publication 1756-PM001. • All the data for I/O modules is at the controller scope. As you assign addresses, click Controller Scoped Tags to see the I/O tags.
Control 1771 I/O Over ControlNet EXAMPLE D-9 Address a digital device that is wired to a 1771 I/O module − I/O Configuration (Controller I/O tree) − [5] 1756-CNB(R)/D Local_CNB (local CNB in slot 5) − 4 1771-ACN Remote_1771 (Remote_1771_adapter is the name assigned to the adapter) Input Device Group 2 Bit 0 Adapter Module for Node Number 4 Remote_1771:I.Data[2].
D-10 Control 1771 I/O Over ControlNet Notes: Publication CNET-UM001C-EN-P - November 2005
Index Numerics 1734-ACNR module additional documentation Preface-3 overview 1-7 1756-CN2, 1756-CN2R modules additional documentation Preface-3 overview 1-3 troubleshooting 8-2–8-5 1756-CNB, 1756-CNBR modules additional documentation Preface-3 overview 1-4 troubleshooting 8-6–8-10 1769-L32C, 1769-L35CR controllers additional documentation Preface-3 overview 1-4 troubleshooting 8-11–8-14 1784-PCC card additional documentation Preface-3 overview 1-5 1784-PCIC, 1784-PCICS, 1784-PKTCS cards additional documentat
2 Index as they affect network update time 5-6 bandwidth limitations 5-6 determining connections 5-3 for non-Logix5000 controllers 5-12 organizing tag data 5-5 controlling I/O over ControlNet 4-1– 4-19, B-7 accessing distributed I/O data 4-13– 4-16 adding distributed I/O to an RSLogix 5000 project 4-11–4-13 controlling 1771 I/O D-1–D-9 requested packet interval 4-2 validating connections 4-17–4-19 ControlNet overview B-1–B-14 D data types in produced or consumed tags 5-5 direct connections 4-5–4-6 di
Index unscheduled portion B-4 O overview 1734-ACNR module 1-7 1756-CN2, 1756-CN2R modules 1-3 1756-CNB, 1756-CNBR modules 1-4 1769-L32C, 1769-L35CR controllers 1-4 1784-PCC card 1-5 1784-PCIC, 1784-PCICS, 1784-PKTCS cards 1-5 1788-CNC, 1788-CNCR, 1788-CNF, 1788-CNFR cards 1-6 1794-ACN15, 1794-ACNR15 modules 1-6 1797-ACNR15 module 1-7 of ControlNet communication modules 1-1–1-12 of the RSLogix 5000 configuration process 3-2 ownership in a Logix5000 system 4-8– 4-9 listen-only connection 4-8–4-9 owner
4 Index 1756-CN2, 1756-CN2R modules 8-2– 8-5 1756-CNB, 1756-CNBR modules 8-6– 8-10 1769-L32C, 1769-L35CR controllers 8-11–8-14 Publication CNET-UM001C-EN-P - November 2005 1784-PCIC, 1784-PCICS, 1784-PKTCS cards 8-15–8-16 1788-CN(x) cards 8-17–8-20 1794-ACN15, 1794-ACNR15 modules 8-21–8-22 1797-ACNR15 module 8-23–8-24
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 ControlNet Modules in Logix5000 Control Systems Cat. No. Multiple ControlNet catalog numbers Pub. No. CNET-UM001C-EN-P Pub. Date November 2005 Part No. 957988-68 Please complete the sections below.
PLEASE FASTEN HERE (DO NOT STAPLE) PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO.
ControlLogix, RSLogix 5000, RSView, RSNetWorx, RSNetWorx for ControlNet, and RSLinx software are trademarks of Rockwell Automation, Inc. ControlNet is a trademark of ControlNet International, Ltd. Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Automation Support Rockwell Automation provides technical information on the web to assist you in using its products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
ControlNet Modules in Logix5000 Control Systems User Manual
