Page 1 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...
Page 2: Important User Information
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
Page 3: Introduction
Summary of Changes This release of this document contains updated information. Changes are Introduction designated by change bars in margin, as shown to the right. The table below lists the new information included in this release of the New and Revised ControlNet Modules in Logix5000 Control Systems user manual.
Page 4 Summary of Changes Notes: Publication CNET-UM001C-EN-P - November 2005...
Page 5: Purpose Of This Manual
Preface This manual describes how you can use ControlNet with your Logix5000 Purpose of This Manual controller. With this manual, you can learn how to communicate between your controller and various devices on the ControlNet network. You should use this manual if you program applications that use ControlNet Who Should Use with one of the following Logix5000 controllers: This Manual...
Page 6: Information This Manuals Contains
Preface This table describes the information available in this manual. Information This Manuals Contains Section Title Chapter 1 About the Logix5000 ControlNet Communication Modules Chapter 2 Connect a Computer to the ControlNet Network Chapter 3 Configure a ControlNet Module Chapter 4 Control I/O Chapter 5 Produce and Consume Tags (Interlock Controllers)
Page 7: Related Documentation
Installation Guide AC Drives, DC Safety Guidelines - Application and Installation SGI-1.1 Drives To view or download these publications, go to: http://www.rockwellautomation.com/literature To obtain a hard copy, contact your Rockwell Automation distributor or sales representative. Publication CNET-UM001C-EN-P - November 2005...
Page 8 Preface Notes: Publication CNET-UM001C-EN-P - November 2005...
Page 9: Table Of Contents
Table of Contents Important User Information ....... . 1-2 Introduction ......Summary of Changes-1 Summary of Changes New and Revised Information .
Page 10 Table of Contents Schedule the Network Offline ......3-13 Schedule the Network Online ......3-19 Reschedule a ControlNet Network That Has Previously Been Scheduled .
Page 11 Table of Contents 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 .
Page 12 Table of Contents 1794-ACN15 and 1794-ACNR15 ControlNet FLEX I/O Adapters ..........8-21 1797-ACNR15 ControlNet FLEX Ex Redundant Media I/O Adapter .
Page 13 Index Rockwell Automation Support ......Backcover Installation Assistance ......Backcover...
Page 14 Table of Contents Publication CNET-UM001C-EN-P - November 2005...
Page 15: Use This Chapter
Chapter About the Logix5000 ControlNet Communication Modules This chapter introduces the Logix5000 ControlNet communication modules Use This Chapter and describes how you can use these modules in a control system: For This Information See Page Choose a ControlNet Communication Module 1756-CN2, 1756-CN2R Overview 1756-CNB, 1756-CNBR Overview 1769-L32C, 1769-L35CR Overview...
Page 16 About the Logix5000 ControlNet Communication Modules This table describes the ControlNet communication modules’ functionality. Table 1.1 The Functions of the ControlNet Communication Module ControlNet Module Functions as an Functions as a Functions as an Messaging I/O Bridge I/O Adapter Bridge 1756-CN2, 1756-CN2R 1756-CNB, 1756-CNBR 1769-L32C, 1769-L35CR...
Page 17: 1756-Cn2, 1756-Cn2R Overview
About the Logix5000 ControlNet Communication Modules ControlLogix ControlNet communication modules bridge ControlNet links to 1756-CN2, 1756-CN2R route messages to devices on other networks. The modules also monitor and Overview control I/O modules located remotely from the ControlLogix controller. The 1756-CN2 and 1756-CN2R modules are supported in the following software: •...
Page 18: 1756-Cnb, 1756-Cnbr Overview
About the Logix5000 ControlNet Communication Modules ControlLogix ControlNet communication modules bridge ControlNet links to 1756-CNB, 1756-CNBR route messages to devices on other networks. The modules also monitor and Overview control I/O modules located remotely from the ControlLogix controller. This module provides: •...
Page 19: 1784-Pcc Overview
About the Logix5000 ControlNet Communication Modules The 1784-PCC communication interface cards are personal computer memory 1784-PCC Overview card international association (PCMCIA) interface cards that enable laptop computers to communicate directly with other ControlNet products. These cards support: • messaging data for configuration and programming information, operator interfaces, upload/download.
Page 20: 1788-Cnc, 1788-Cncr, 1788-Cnf, 1788-Cnfr Overview
About the Logix5000 ControlNet Communication Modules The ControlNet communication card links the FlexLogix controller and 1788-CNC, 1788-CNCR, PowerFlex 700S with DriveLogix controller to other devices on a ControlNet 1788-CNF, 1788-CNFR network. The ControlNet communication card also provides access for the Overview FlexLogix controller to monitor and control I/O modules located remotely from the controller on the ControlNet network.
Page 21: 1797-Acnr15 Overview
About the Logix5000 ControlNet Communication Modules The 1797-ACNR15 modules operate as adapters for FLEX Ex I/O modules 1797-ACNR15 Overview on a ControlNet network in an intrinsically safe environment. This module supports: • control of I/O within its chassis–you can connect up to 8 FLEX Ex I/O modules to one 1797-ACNR15 module.
Page 22: Use The Controlnet Communication Modules In A Control System
About the Logix5000 ControlNet Communication Modules This figure shows how the different ControlNet modules can fit into a control Use the ControlNet system. Communication Modules in a Control System Figure 1.1 ControlNet Modules and the Control System Relationship PC Running SoftLogix5800 Distributed I/O Controller with...
Page 23: Bridge Across Networks
About the Logix5000 ControlNet Communication Modules Some ControlNet modules support the ability to bridge or route Bridge Across Networks 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.
Page 24 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.2 Configure a Drive on a DeviceNet Network PanelView Station Workstation ControlNet Network Bridge...
Page 25 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. The CompactLogix and FlexLogix controllers’ IMPORTANT performance degrades significantly if you use the controller as a bridge.
Page 26 1-12 About the Logix5000 ControlNet Communication Modules This table lists the possible bridges between communication networks. Table 1.3 Bridges Between Communication Networks To Bridge To This You Can Use the Following From This Network: In a CompactLogix System In a ControlLogix Chassis In a FlexLogix Controller Network •...
Page 27: Use This Chapter
Chapter Connect a Computer to the ControlNet Network This chapter describes how to configure a personal computer to operate on a Use This Chapter ControlNet network. Read this For This Information See Page chapter for: • Connect a Computer to Any Network 1784-PCC, 1784-PCIC, 1784-PCICS, 1784-PKTCS cards Configure the ControlNet Communication Driver in the RSLinx Software...
Page 28: Connect A Computer To Any Network
Connect a Computer to the ControlNet Network To access a network, either: Connect a Computer to Any • connect directly to the network or Network • connect to a different network and browse (bridge) to the desired network. This requires no additional programming. To use RSNetWorx software to configure and schedule a IMPORTANT ControlNet network, either:...
Page 29: Configure The Controlnet Communication Driver In The Rslinx
Connect a Computer to the ControlNet Network To configure the ControlNet communication driver for the personal computer Configure the ControlNet (programming workstation): Communication Driver in the RSLinx Software Do not use these steps to configure a ControlNet IMPORTANT communication driver for any application that uses a SoftLogix5800 controller.
Page 30 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.
Page 31: Connect A Softlogix Controller To Controlnet
Connect a Computer to the ControlNet Network The SoftLogix5800 controller is a soft control solution that runs in a Connect a SoftLogix Microsoft Windows NT, Windows 2000, or Windows XP environment. When Controller to ControlNet 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.
Page 32 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).
Page 33: Use This Chapter
Chapter Configure a ControlNet Module This chapter describes how to configure a ControlNet communication module Use This Chapter to operate on a ControlNet network. For This Information See Page Read this Set Up Your Computer to Connect to ControlNet chapter for: •...
Page 34: Set Up Your Computer To Connect To Controlnet
Configure a ControlNet Module You connect your personal computer to the ControlNet network via an Set Up Your Computer to RSLinx ControlNet software communication driver. You use the ControlNet Connect to ControlNet communication driver to: • upload and download controller projects using RSLogix 5000 software. •...
Page 35: Add A Local Controlnet Module
Configure a ControlNet Module 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. When you create a new RSLogix 5000 project with the IMPORTANT CompactLogix 1769-L32C or 1769-L35CR controller, the...
Page 36 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.1 ControlNet Communication Modules Available Locally If You Are Using This Logix5000 You Can Use This ControlNet Controller Communication Module Locally CompactLogix...
Page 37 Configure a ControlNet Module F. Inhibit the module, if necessary. Initially, do you want Then the module to communicate with the controller? Leave the box unchecked Check the When you test this portion of the system, F. Click Finish. clear the check box. G.
Page 38 Configure a ControlNet Module This table describes the keying options available in RSLogix 5000 software. Table 3.2 Electronic Keying Options Keying Option Definition Exact Match When a controller establishes a connection with the ControlNet module, the following parameters must match or the inserted module will reject the connection: •...
Page 39: Add A Remote Controlnet Module
Configure a ControlNet Module 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.
Page 40 Configure a ControlNet Module 3. Configure the remote ControlNet communication module. The example below shows configuration for a 1756-CNB IMPORTANT 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.
Page 41 Configure a ControlNet Module 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.
Page 42: Download The Project To The Logix5000 Controller
3-10 Configure a ControlNet Module Download the Project to the Logix5000 Controller Before you your RSLogix5000 project configuration to IMPORTANT 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.
Page 43 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...
Page 44: Use Rsnetworx For Controlnet Software
3-12 Configure a ControlNet Module You must use RSNetWorx for ControlNet software to schedule the network Use RSNetWorx for before the configured I/O devices in your application will become active. You ControlNet Software must also reschedule the network if a change is made to an existing network that was already scheduled.
Page 45: Schedule The Network Offline
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. •...
Page 46 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.
Page 47 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.
Page 48 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. Publication CNET-UM001C-EN-P - November 2005...
Page 49 Configure a ControlNet Module 3-17 Table 3.4 Network Parameters for Scheduling the Network Offline Parameter Description Network The smallest user-configurable repetitive time cycle in milliseconds at Update which data can be sent on ControlNet. Time (ms) Max. This is the node with the highest network address that can use scheduled Scheduled time on a ControlNet link.
Page 50 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.
Page 51: Schedule The Network Online
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.
Page 52 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.
Page 53 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. Publication CNET-UM001C-EN-P - November 2005...
Page 54 3-22 Configure a ControlNet Module Table 3.5 Network Parameters for Scheduling the Network Online Parameter Description Network Update The smallest user-configurable repetitive time cycle in Time (ms) milliseconds at which data can be sent on ControlNet. Max. Scheduled This is the node with the highest network address that can use Address scheduled time on a ControlNet link.
Page 55: Reschedule A Controlnet Network That Has Previously
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.
Page 56 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.
Page 57: Use This Chapter
Chapter Control I/O This chapter describes how a controller controls distributed I/O over Use This Chapter ControlNet. The controller requires a communication module to connect to the network. Distributed I/O modules require an adapter to connect to the Read this network.
Page 58: Set Up The Hardware
Control I/O In this example, the Logix5000 controller uses a ControlNet communication Set Up the Hardware 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.
Page 59: Select A Communication Format
Control I/O When you configure a remote ControlNet communication module or an I/O Select a module, you select a communication format. The communication format you Communication Format choose determines the data structure for the tags that are associated with the module.
Page 60 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.2 Communication Format for Module Types If You Have This Type And Want Select a Communication Format That Specifies of I/O Module digital module a rack optimized connection...
Page 61: Direct Or Rack Optimized Connection
Control I/O 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.
Page 62 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 I/O I/O I/O I/O ControlNet Adapter with ControlNet Adapter with ControlNet Adapter with Digital I/O Modules...
Page 63 Control I/O 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. Controller with ControlNet Communication Module ControlNet Network I/O I/O I/O I/O...
Page 64: Ownership
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.
Page 65 Control I/O Choose the Type of Ownership for a Module Table 4.5 Choose the Type of Module Ownership If The Module Is An And Another Controller And You Want To Then Use This Type of Connection Input Module Does not own the module Owner, such as: not listen-only Owns the module Maintain communication with the...
Page 66: Add Local And Remote Controlnet Modules
4-10 Control I/O Before you can connect to and control distributed I/O, you must add local and Add Local and Remote remote ControlNet communication modules. The type of distributed I/O ControlNet Modules determines your choice of a remote ControlNet adapter. For more information, see the table Choose the Appropriate Remote Adapter.
Page 67: Add Distributed I/O
Control I/O 4-11 To communicate with the I/O modules in your system, you add bridge, Add Distributed I/O 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).
Page 68 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.
Page 69: Access Distributed I/O
Control I/O 4-13 Table 4.8 Distributed I/O Formats If You Select This Format For The Select This Format For The Distributed Remote Adapter 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 Access Distributed I/O the specific features of the I/O module.
Page 70 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.
Page 71 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.
Page 72 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:I “FLEX_adapter” 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 “Input_module” in slot 0 FLEX_adapter:0:C.DelayTime_0 rack optimized connection FLEX_adapter:0:I Example 3...
Page 73: Validate Connections
Control I/O 4-17 Verify that the controller can communicate with the devices that you have just Validate Connections 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.
Page 74 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.
Page 75 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.
Page 76 4-20 Control I/O Notes: Publication CNET-UM001C-EN-P - November 2005...
Page 77: Use This Chapter
Chapter Produce and Consume Tags (Interlock Controllers) This chapter describes how to interlock (produce and consume tags) Use This Chapter controllers via a ControlNet network. Read this For This Information See Page chapter for: • Terminology 1756-CN2, 1756-CN2R modules • 1756-CNB, 1756-CNBR modules Set Up the Hardware •...
Page 78: Set Up The Hardware
Produce and Consume Tags (Interlock Controllers) In this example, the controller in the first chassis produces a tag that is Set Up the Hardware consumed by the controller in the second chassis. Data Chassis #1 Chassis #2 Logix5000 Controller Logix5000 Controller with ControlNet with ControlNet Communication Module...
Page 79: Determine Connections For Produced And Consumed Tags
Produce and Consume Tags (Interlock Controllers) • the communication driver (such as., AB-PCICS-1) is configured for the programming workstation. 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.
Page 80 Produce and Consume Tags (Interlock Controllers) This table describes each produced or consumed tag and the number of connections used. Table 5.1 Produced and Consumed Tags and number of Connections This Controller Has This Many A Produced Tag Uses This A Consumed Tag Uses This Connections Available Many Connections...
Page 81: Organize Tags For Produced Or Consumed Data
Produce and Consume Tags (Interlock Controllers) This table describes the guideline to follow as you organize your tags for Organize Tags for Produced produced or consumed data (shared data). or Consumed Data Table 5.2 Guidelines for Produced or Consumed Data Tags Guideline Details Create the tags at the controller...
Page 82: Adjust For Bandwidth Limitations
Produce and Consume Tags (Interlock Controllers) Guideline Details Combine data that goes to the If you are producing several tags for the same controller: same controller. • Group the data into one or more user-defined data types. (This uses less connections than producing each tag separately.) •...
Page 83: Produce A Tag
Produce and Consume Tags (Interlock Controllers) A Logix5000 controller can only produce controller-scoped user-created tags Produce a Tag 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.
Page 84 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]...
Page 85: Consume A Tag
Produce and Consume Tags (Interlock Controllers) Logix5000 controllers can only consume controller-scoped user-created tags Consume a Tag 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: You can only create consumed tags when your RSLogix IMPORTANT...
Page 86 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.
Page 87 Produce and Consume Tags (Interlock Controllers) 5-11 7. Use RSNetWorx for ControlNet software to schedule the network. Your Logix5000 controller can consume a tag that was IMPORTANT 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.
Page 88: Additional Steps For A Plc-5C Or Controlnet Scanner Card
5-12 Produce and Consume Tags (Interlock Controllers) Some devices connect to the ControlNet network via a ControlNet scanner Additional Steps for a and can use produced and consumed tags to share scheduled data with PLC-5C or ControlNet Logix5000 controllers. For example, you can connect a real-time control Scanner Card application, such as a Visual Basic application, to ControlNet through a 1784-PKTCS scanner card to exchange data with Logix5000 controllers.
Page 89: Use Rsnetworx To Produce A Tag From A Controlnet Scanner
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.
Page 90 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.
Page 91: Use Rsnetworx To Consume A Tag By A Controlnet Scanner
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.
Page 92 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.
Page 93: Reconstruct Values With Plc-5C Controller
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.
Page 94 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 Re-construct a floating point value. This example takes two consumed integers that were originally EXAMPLE a produced REAL, reverses the order of the integers and assembles them into a floating point value equal to the original REAL.
Page 95: Use This Chapter
Chapter Peer-to-Peer Messaging This chapter describes how to use MSG instructions to send data to and Use This Chapter receive data from other modules on a ControlNet network. Read this For This Information See Page chapter for: • Set Up the Hardware 1756-CN2, 1756-CN2R modules •...
Page 96: Set Up The Hardware
Peer-to-Peer Messaging In this example, the controller in the local chassis sends a message (using a Set Up the Hardware MSG instruction) to another module (which can be a controller) on the ControlNet network. Data Remote Chassis Local Chassis Logix5000 Controller ControlNet Programming Terminal...
Page 97 Peer-to-Peer Messaging 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 The 1769-L32C and 1769-L35CR controllers can produce IMPORTANT and consume tags over ControlNet to other Logix5000 controllers.
Page 98: Guidelines For Msg Instructions
Peer-to-Peer Messaging This table describes guidelines to use when working with message instructions. Guidelines for MSG Instructions Table 6.1 Guidelines for MSG Instructions Guideline Details 1. For each MSG instruction, create a Each MSG instruction requires its own control tag. This tag contains control elements control tag.
Page 99: Determine Connections For Messages
Peer-to-Peer Messaging Messages transfer data to other modules, such as other controllers, I/O Determine Connections for modules or operator interfaces. Each message uses one connection, regardless Messages 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.
Page 100: Enter Message Logic
Peer-to-Peer Messaging To send or receive data from a ControlNet module via a message, you must Enter Message Logic 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.
Page 101: Enter A Message
Peer-to-Peer Messaging Enter a Message Use relay ladder logic to enter a MSG instruction. Click to configure the MSG instruction. Enter a MSG instruction EXAMPLE 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.
Page 102: Message Type To Configure A Msg To Logix5000 Controller
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...
Page 103: Message Type To Configure A Msg To An Slc 500 Processor
Peer-to-Peer Messaging 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...
Page 104: Message Type To Configure A Msg To A Plc-5 Processor
6-10 Peer-to-Peer Messaging Message Type to Configure a MSG to a PLC-5 Processor Table 6.7 Message Type to Configure a MSG to a PLC-5 Processor If The Data Is And You Want To For This Item Type or Select integer (s) read (receive) data Message Type PLC5 Typed Read...
Page 105 Peer-to-Peer Messaging 6-11 Communication path from a Logix5000 controller to a PLC5 controller EXAMPLE over a ControlNet network ControlNet Network Node Address = 7 Node Address = 1 Message PLC5-C Path = 1, 1, 2, 1 Where Indicates connection to the backplane in local chassis slot number of 1756-CN2 module in local chassis connection to port 2 of the 1756-CN2 module (get on ControlNet) node address of remote PLC5...
Page 106: Communicate With Plc-5 Or Slc 500 Processors
6-12 Peer-to-Peer Messaging If the message is to a PLC-5 or SLC 500 processor and it reads or writes Communicate with PLC-5 or integers (not REALs), use a buffer of INTs in the message. SLC 500 Processors • Logix5000 controllers execute more efficiently and use less memory when working with 32-bit integers (DINTs).
Page 107 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.
Page 108: Map Tags
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.
Page 109 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.
Page 110: Stagger The Messages
6-16 Peer-to-Peer Messaging As you add messages to your project, you may have to coordinate the Stagger the Messages 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). Rule 2 Enable no more than 10 of the following types of messages at one time: •...
Page 111: Route A Controlnet Message
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: This section uses RSLogix 5 software, revision 3.x or IMPORTANT greater and PLC-5C Series C/Revision M, Series D/Revision C, Series E/Revision B, Series F/Revision A or greater 1.
Page 112 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.
Page 113: Communicate With Panelview And Rsview Products
Chapter Communicate with PanelView and RSView Products This chapter describes how a controller uses a ControlNet communication Use This Chapter module to communicate with PanelView and RSView software products over a ControlNet network. Read this chapter for: For This Information See Page •...
Page 114: Determine Connections To Panelview Terminals
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 •...
Page 115: Add A Panelview Terminal
Communicate with PanelView and RSView Products 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. • PanelView Plus terminals –...
Page 116 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.
Page 117 Communicate with PanelView and RSView Products 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. Publication CNET-UM001C-EN-P - November 2005...
Page 118: Organize Controller Data For A Panelview Terminal
Communicate with PanelView and RSView Products 7. Configure the terminal. Organize data for a PanelView or PanelView Plus terminal based on how the Organize Controller Data data is used. for a PanelView Terminal For Data That Is Do This Time-critical Use the I/O tags of the terminal.
Page 119: Determine Connections To Rsview Applications
Communicate with PanelView and RSView Products 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: This Address Variable name_of_terminal name of the instance in the I/O configuration of the controller element of the input (I) or output (O) structure.
Page 120 Communicate with PanelView and RSView Products Notes: Publication CNET-UM001C-EN-P - November 2005...
Page 121: Troubleshoot Your Controlnet Communication Modules
Chapter Troubleshoot Your ControlNet Communication Modules This chapter provides descriptions for status indicators used on the Use This Chapter ControlNet communication modules and adapters and how to use those indicators to troubleshoot your application. For This Information See Page 1756-CN2 and 1756-CN2R ControlNet Communication Modules 1756-CNB and 1756-CNBR ControlNet Communication Modules 1769-L32C and 1769-L35CR CompactLogix Controllers 8-11...
Page 122: 1756-Cn2 And 1756-Cn2R Controlnet Communication Modules
Troubleshoot Your ControlNet Communication Modules This figure shows the status indicators used on the 1756-CN2 and 1756-CN2R 1756-CN2 and 1756-CN2R modules. ControlNet Communication Modules Figure 8.1 1756-CN2 and 1756-CN2R Status Indicators 1756-CN2 1756-CN2R Module Status Display Module Status Indicator Network Channel Status Indicators Channel A BNC Connector Channel B BNC Connector...
Page 123 Troubleshoot Your ControlNet Communication Modules If the OK With This It Means Take This Action Indicator Is Module Status Display Module’s network address is set to 00, an 1. Optional – Turn chassis power supply Msg scrolls invalid ControlNet address. See footnote at end off.
Page 124: Network Channel Status Indicator Interpretation
Troubleshoot Your ControlNet Communication Modules If the OK With This It Means Take This Action Indicator Is Module Status Display 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.
Page 125 Take This Action Status Indicators Are 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. Alternating red/green Self-test None Alternating red/off Incorrect node configuration Check network address and other ControlNet configuration parameters.
Page 126: 1756-Cnb And 1756-Cnbr Controlnet Communication
Troubleshoot Your ControlNet Communication Modules This figure shows the status indicators used on the 1756-CNB and 1756-CNB and 1756-CNBR 1756-CNBR modules. ControlNet Communication Modules Figure 8.2 1756-CNB and 1756-CNBR Status indicators 1756-CNB 1756-CNBR Module Status Display Module Status Indicator Network Channel Status Indicators Channel A BNC Connector Channel B BNC Connector...
Page 127 Troubleshoot Your ControlNet Communication Modules If The OK With This It Means Take This Action Indicator Is Module Status Display Steady red Module’s network address is set to 00, an 1. Optional – Turn chassis power supply Msg scrolls invalid ControlNet address, or 99, an invalid off.
Page 128 Troubleshoot Your ControlNet Communication Modules If The OK With This It Means Take This Action Indicator Is Module Status Display Flashing red BOOT Module has invalid firmware. Update module firmware with ControlFlash Update Utility. Flash update is in progress. None required. UPDT SNGL KPR! Module detected that it has been connected to...
Page 129: Network Channel Status Indicator Interpretation
Troubleshoot Your ControlNet Communication Modules If The OK With This It Means Take This Action Indicator Is Module Status Display Steady green or SO_1 Old primary switchover phase 1 in progress. If the display shows any message for more than three seconds, then the CNB module failed SO_2 Old primary switchover phase 2 in progress.
Page 130 Take This Action Status Indicators Are 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. Alternating red/green Self-test None Alternating red/off One of the following: Check the node address and other ControlNet configuration parameters.
Page 131: 1769-L32C And 1769-L35Cr Compactlogix Controllers
Troubleshoot Your ControlNet Communication Modules 8-11 This figure shows the status indicators used on the 1769-L32C and 1769-L32C and 1769-L35CR 1769-L35CR CompactLogix controller. CompactLogix Controllers Figure 8.3 1769-L32C and 1769-L35CR CompactLogix Controller Status Indicators Network Channel A Status Indicator Network Channel B Status Indicator Module Status Indicator...
Page 132: Interpret Status Indicators
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.
Page 133: Module Status (Ms) Indicator
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 It Means Take This Action (MS) Indicator Is The controller has no power.
Page 134: Network Channel Status Indicators
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.
Page 135 Troubleshoot Your ControlNet Communication Modules 8-15 This figure shows the status indicators used on the 1784-PCIC, 1784-PCICS 1784-PCIC, 1784-PCICS and and 1784-PKTCS cards. 1784-PKTCS ControlNet PCI 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.
Page 136 3. Verify that you have firmly inserted the card into a PCI local bus expansion slot and that the expansion slot screw is tightened. 4. If fault persists, contact your Rockwell Automation representative or distributor. Channel disabled Program network for redundant media, if required...
Page 137 Troubleshoot Your ControlNet Communication Modules 8-17 This figure shows the status indicators used on the 1788-CNC and 1788-CNC, 1788-CNCR, 1788-CNCR cards. 1788-CNF and 1788-CNFR ControlNet Daughtercards Figure 8.5 1788-CNC, 1788-CNCR Status indicators I/O Status Indicator Module Status Indicator Node Address Switches 1788-CNC Network Channel Status Indicators (A and B)
Page 138: Module And I/O Status Indicator Interpretation
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. •...
Page 139 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 It Means Take This Action Status (MS) Indicator Is No power Apply power.
Page 140: Network Channel Status Indicator Interpretation
8-20 Troubleshoot Your ControlNet Communication Modules Network Channel Status Indicator Interpretation When you connect the module to a ControlNet network IMPORTANT using only the NAP, the LEDs are meaningless. • Steady - indicator is on continuously in the defined state. •...
Page 141 Troubleshoot Your ControlNet Communication Modules 8-21 This figure shows the status indicators used on the 1794-ACN15 and 1794-ACN15 and 1794-ACNR15 modules. 1794-ACNR15 ControlNet FLEX I/O Adapters Figure 8.6 1794-ACN15 and 1794-ACNR15 Status Indicators 43610 Network Channel Status Indicators Module Status Indicators This graphic shows a 1794-ACNR15.
Page 142 8-22 Troubleshoot Your ControlNet Communication Modules If Either Channel It Means Take This Action Status Indicators Are 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...
Page 143 Troubleshoot Your ControlNet Communication Modules 8-23 This figure shows the status indicators used on the 1797-ACNR module. 1797-ACNR15 ControlNet FLEX Ex Redundant Media Figure 8.7 1797-ACNR15 Status Indicators I/O Adapter Network Channel Status Power Module Status 41412 The modules use the following 2 status indicators: •...
Page 144 8-24 Troubleshoot Your ControlNet Communication Modules If Either Channel It Means Take This Action Status Indicators Are 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...
Page 145: Use This Appendix
Appendix Connection Use Over ControlNet ControlNet communication modules use connections to manage Use This Appendix communication. A connection is a point-to-point communication mechanism that transfers data between a transmitter and a receiver. Read this chapter for: ControlNet communication modules use connections that transfer data from a •...
Page 146: Connected Messaging Limits
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.
Page 147: Unconnected Messaging Limits
Connection Use Over ControlNet Product Connected Messaging Limits 1788-CNx Each module supports 32 connections, of which 22 connections can be scheduled connections. With these controllers, the number of end-node connections they effectively support is dependent on the application’s NUT and RPI: If the NUT and The controllers support a maximum of this the RPI are each...
Page 148 Connection Use Over ControlNet Notes: Publication CNET-UM001C-EN-P - November 2005...
Page 149: Understand The Controlnet Network
Appendix ControlNet Overview This chapter defines some basic ControlNet concepts and how the ControlNet network is used for control. ControlNet is a real-time control network that provides high-speed transport Understand the ControlNet of both time-critical I/O and interlocking data and messaging data, including Network upload/download of programming and configuration data on a single physical media link.
Page 150: Exchange Information On Controlnet
ControlNet Overview ControlNet communication modules use a message-based protocol that Exchange Information implements a relative path to send a message from the producing module in a on ControlNet 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.
Page 151 ControlNet Overview 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.
Page 152: Network Update Time (Nut
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.
Page 153: Actual Packet Interval (Api
ControlNet Overview 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.
Page 154: Schedule The Network
ControlNet Overview Table B.2 NUT Example Data Rates With this NUT And this multiple The Module Can Send Data at this Rate 10ms 20ms 40ms 80ms 160ms 320ms 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.
Page 155 ControlNet Overview 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.
Page 156: Understand The Network Keeper
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.
Page 157 ControlNet Overview 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: •...
Page 158: Default Parameters
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: •...
Page 159: Controlnet Capacity And Topology
ControlNet Overview B-11 When planning a ControlNet network, you should consider the following: ControlNet Capacity and Topology • 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.
Page 160 B-12 ControlNet Overview Figure B.2 Example ControlNet System Trunkline/Dropline Topology Tap with Dropline Trunkline Node Node Node Node 43620 Figure B.3 Example ControlNet System Star Topology Tap with 1-meter Coax Dropline Repeater Node Node Node Node Node Node 43621 Publication CNET-UM001C-EN-P - November 2005...
Page 161 ControlNet Overview B-13 Figure B.4 Example ControlNet System Ring Topology Node Node ControlNet Repeater Adapter and Fiber Ring Module Fiber Cables tap with 1-meter Coaxial Cable Dropline Node Node Node Node Node Node 43622 Publication CNET-UM001C-EN-P - November 2005...
Page 162: Number Of Nodes
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;...
Page 163: Use This Appendix
Appendix Determine Your ControlNet Media Requirements Use this appendix to determine your network media requirements. Use This Appendix For More Information See Page Determine How Many Taps You Need Connect Programming Devices Determine What Type of Cable You Need Determine Trunk Cable Section Lengths Determine if You Need Repeaters C-10 Determine How Many Trunk Terminators You Need...
Page 164: Design A Controlnet Media System
Determine Your ControlNet Media Requirements The design of a ControlNet media system is a process of measurement and Design a ControlNet Media judgement. The objective is to select the ControlNet media that will serve as System the foundation for the network operations. When designing a network for an application, you must address the following deciding factors to assure a steady control foundation: •...
Page 165: Controlnet Media Components
Determine Your ControlNet Media Requirements 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...
Page 166: Determine How Many Taps You Need
Determine Your ControlNet Media Requirements The number of taps you need depends on the number of devices you want to Determine How Many Taps connect to the network. You need a tap for each node and fiber hub on a You Need segment.
Page 167: Connect Programming Devices
Determine Your ControlNet Media Requirements 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 1786-TPS 1786-TPR 1786-TPYR 1786-TPYS 1797-TPS 1797-TPR 1797-TPYR 1797-TPYS Programming devices in non-hazardous areas may be connected to the Connect Programming ControlNet cable system through a 1784-PCIC, 1784-PCICS or 1784-PCC Devices...
Page 168: Determine What Type Of Cable You Need
Determine Your ControlNet Media Requirements There are several types of RG-6 quad shield cable that may be appropriate for Determine What Type of your installation, depending on the environmental factors associated with your Cable You Need application and installation site. You should install all wiring for your ControlNet cable IMPORTANT system in accordance with the regulations contained in the...
Page 169: Determine Trunk Cable Section Lengths
Determine Your ControlNet Media Requirements A segment is comprised of several sections of trunk cable separated by taps Determine Trunk between 75Ω terminators. The total cable length of a segment is equal to the Cable Section sum of all of the trunk-cable sections. Lengths Figure C.4 Taps and Trunk Cable Sections Trunk Cable Section...
Page 170 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).
Page 171 Determine Your ControlNet Media Requirements 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;...
Page 172: Determine If You Need Repeaters
C-10 Determine Your ControlNet Media Requirements You can install repeaters on a segment to increase the total trunk-cable length Determine if You or number of taps. This creates another segment. You need to install repeaters Need Repeaters if your system requires more than 48 taps per segment, or a longer trunk cable than the specifications allow.
Page 173: Determine How Many Trunk Terminators You Need
Determine Your ControlNet Media Requirements C-11 You must use 75Ω trunk terminators (cat. nos. 1786-XT and 1797-XT) to Determine How terminate each segment for the ControlNet cable system. You need two XT Many Trunk Terminators terminators per segment because you need one for each end of the segment. You Need 1786-XT Intrinsically Safe Sheath...
Page 174: Install Repeaters In Series
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) •...
Page 175: Install Repeaters In Parallel
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...
Page 176: Install Repeaters In A Combination Of Series And Parallel
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.
Page 177: Determine What Type Of Connectors You Need
C-15 Depending on the type of connection you need to make, you can select from Determine What Type multiple Rockwell Automation ControlNet connectors. The following are of Connectors You examples of connections you may need to make in your ControlNet...
Page 178 C-16 Determine Your ControlNet Media Requirements Do not let any metallic surfaces on the BNC connectors, ATTENTION 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.
Page 179: Use Redundant Media
Determine Your ControlNet Media Requirements C-17 You can run a second trunk cable between your ControlNet nodes for Use Redundant Media 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.
Page 180 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. •...
Page 181 Determine Your ControlNet Media Requirements C-19 Figure C.9 Trunk Cable A = Segment 1 Terminators Terminators Trunk Cable B = Repeater B Node Node Repeater A Node Node Trunk Cable B = Trunk Cable A = Terminators Terminators 43630 Segment 2 To use redundant media, all nodes must support redundant media.
Page 182: Application Considerations
C-20 Determine Your ControlNet Media Requirements The guidelines in this section coincide with the guidelines for “the installation Application Considerations 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.
Page 183: General Wiring Guidelines
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. •...
Page 184 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.
Page 185: Order Components
Determine Your ControlNet Media Requirements C-23 Now that you are ready to begin ordering components, use these guidelines to Order Components help you select components. General Planning The ControlNet cable system is isolated from earth and must be protected from inadvertent ground connections. Segment Planning •...
Page 186 C-24 Determine Your ControlNet Media Requirements Notes: Publication CNET-UM001C-EN-P - November 2005...
Page 187: Control 1771 I/O Over Controlnet
Appendix Control 1771 I/O Over ControlNet Use this appendix to monitor and control I/O devices that are wired to 1771 Use This Appendix I/O modules when a: • 1756-CN2(R) or the 1756-CNB(R) module connects the local chassis to a ControlNet network. •...
Page 188: Add The Local 1756-Cn2(R) Or 1756-Cnb(R) Module
Control 1771 I/O Over ControlNet For more information on how to do this, see the section Add Local and Add the Local 1756-CN2(R) Remote ControlNet Modules in the chapter Control I/O. or 1756-CNB(R) Module To transfer discrete data between remote 1771 I/O and the ControlLogix Add the 1771-ACN(R)15 controller in the local chassis (via the 1756-CN2(R), 1756-CNB(R) module), Module...
Page 189 Control 1771 I/O Over ControlNet 2. Configure the 1771-ACN(R)15 module. A. Name the module. E. Select the module’s node number on ControlNet. B. Select a Comm Format. For more information on choosing a Comm Format, F. Select the Input Size. see section Communication Format.
Page 190: Read Or Write Data To Or From A Block Transfer Module Via A Message Instruction
Control 1771 I/O Over ControlNet Use this procedure to transfer data to or from a module that requires block Read or Write Data To or transfers. Use an INT buffer in the message and move the data into or out of From a Block Transfer the buffer as needed because DINTs can increase the program scan.
Page 191: Configure The Message
Control 1771 I/O Over ControlNet 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.
Page 192: Module
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.2 Tag Descriptions Tag Name...
Page 193: Configure The Message
Control 1771 I/O Over ControlNet 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.
Page 194: Address I/O
Control 1771 I/O Over ControlNet To monitor or control discrete 1771 I/O devices, assign the tag name of the Address I/O 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.
Page 195 Control 1771 I/O Over ControlNet Address a digital device that is wired to a 1771 I/O module EXAMPLE − 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...
Page 196 D-10 Control 1771 I/O Over ControlNet Notes: Publication CNET-UM001C-EN-P - November 2005...
Page 197: Index
Index Numerics determining how many taps your network C-4–C-5 needs 1734-ACNR module determining how many trunk terminators Preface-3 additional documentation C-11– your network needs overview C-14 1756-CN2, 1756-CN2R modules determining if your network needs Preface-3 additional documentation C-10 repeaters overview determining what type of cable your 8-2–8-5 troubleshooting...
Page 198 Index 4-3– as they affect network update time selecting a communication format bandwidth limitations 4-17–4-19 determining connections validating connections 5-12 for non-Logix5000 controllers inhibiting the connection to a ControlNet organizing tag data module 4-1– controlling I/O over ControlNet interlocking controllers 4-19, B-7 See produced tags or consumed tags 4-13–...
Page 199 Index unscheduled portion when organizing produced and consumed tag data routing PLC-5 messages between 6-16–6-18 ControlNet networks overview RSLinx 1734-ACNR module configuring ControlNet communications 1756-CN2, 1756-CN2R modules 2-3–2-4 driver 1756-CNB, 1756-CNBR modules RSLogix 5000 1769-L32C, 1769-L35CR controllers 4-13– accessing distributed I/O data 1784-PCC card 4-16 1784-PCIC, 1784-PCICS, 1784-PKTCS...
Page 200 Index 8-2– 1756-CN2, 1756-CN2R modules 1784-PCIC, 1784-PCICS, 1784-PKTCS 8-15–8-16 cards 8-6– 8-17–8-20 1756-CNB, 1756-CNBR modules 1788-CN(x) cards 8-10 1794-ACN15, 1794-ACNR15 modules 8-21–8-22 1769-L32C, 1769-L35CR controllers 8-11–8-14 8-23–8-24 1797-ACNR15 module Publication CNET-UM001C-EN-P - November 2005...
Page 201 ___No, there is no need to contact me ___Yes, please call me ___Yes, please email me at _______________________ ___Yes, please contact me via _____________________ Return this form to: Rockwell Automation Technical Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705 Fax: 440-646-3525 Email: RADocumentComments@ra.rockwell.com Publication CIG-CO521C-EN-P- May 2003...
Page 202 PLEASE FASTEN HERE (DO NOT STAPLE) Other Comments PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE 1 ALLEN-BRADLEY DR MAYFIELD HEIGHTS OH 44124-9705...
Page 203 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.
Page 204: Rockwell Automation Support
Rockwell Automation provides technical information on the web to assist you in using Rockwell Automation its products. At http://support.rockwellautomation.com, you can find technical Support 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.

This manual is also suitable for:

Allen-bradley controlnet 1756-cn2 Allen-bradley controlnet 1756-cn2r Allen-bradley controlnet 1756-cnb Allen-bradley controlnet 1756-cnbr Allen-bradley controlnet 1769-l32c Allen-bradley controlnet 1769-l35cr ... Show all

Rockwell Automation Allen-Bradley ControlNet 1734-ACNR User Manual

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

Chapter 6

Communicate with Panelview and Rsview Products

Chapter 7

Chapter 8

Troubleshoot Your Controlnet Communication Modules

Appendix A Controlnet Connections

Appendix B

Appendix C Design a Controlnet Media System

Appendix D

Control 1771 I/O over Controlnet

Index

Quick Links

Related Manuals for Rockwell Automation Allen-Bradley ControlNet 1734-ACNR

Summary of Contents for Rockwell Automation Allen-Bradley ControlNet 1734-ACNR

This manual is also suitable for:

Table of Contents