Page 2
Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication.
Page 3
EN 61131-2 Programmable Controllers, Part 2 - Equipment Requirements and Tests. For specific information required by EN 61131-2, see the appropriate sections in this publication, as well as the Allen-Bradley publication Industrial Automation Wiring and Grounding Guidelines For Noise Immunity, publication 1770-4.1.
Where to Find More Information Rockwell Automation Support Who Should Use This Manual Use this manual if you are knowledgeable about ControlLogix products, but need information about integrating them into a ControlNet network. You should: be familiar with Microsoft® Windows® NT and with terms that describe what you should be doing when working in Windows NT, e.g., double...
The example applications are intended to provide you with enough information to get your own network up and running. We recommend that you set up and run the example applications and use them as a guide for setting up your own system. About the Example The example applications presented in this manual are as follows: Applications...
Common Techniques Used The following conventions are used throughout this manual: in This Manual Numbered lists provide sequential steps. Bulleted lists provide information, not procedural steps. Text in bold font indicates words or phrases you should type, programming windows, and menu selections. Pictures of keys and/or screens and windows represent the actual keys you press or the screens and windows you use (see the following figure).
For information about See this publication Publication number network cabling and wiring ControlNet Cable Planning and Installation Guide 1786-6.2.1 the ControlLogix ControlNet Interface Module ControlLogix ControlNet Bridge Installation Instructions 1756-5.71 the ControlLogix Chassis ControlLogix Chassis Installation instructions 1756-5.2 ControlLogix power supplies ControlLogix Power Supplies Installation Instructions 1756-5.1...
Page 10
Publication Problem Report (at the back of this manual). If you have any suggestions about how we can make this manual more useful to you, please contact us at the following address: Rockwell Automation, Allen-Bradley Company, Inc. Control and Information Group Technical Communication...
Page 11
Configuring the 1784-KTCX15 Card....2-3 Installing the ControlLogix Modules ..... . 2-5 Connecting the ControlNet Network .
Page 12
Chapter 4 (continued) Configure the Consumer Logix5550 Controller ....4-6 Add the Producer to the I/O Configuration of the Consumer . 4-6 Create the Consumer Tags ......4-12 Download to the Consumer.
Page 13
Chapter 8 (continued) Survey the Network for Connected Devices ... . . 8-5 Configure the PLC-5C Processor ..... . 8-6 Configure the Consumer Logix5550 Controller.
Page 14
What This Appendix Contains ......A-1 How the ControlLogix System Uses Connections ... . A-1 Connections Determining Connections for I/O Modules .
Rack Optimized and Direct Connections Default Parameters 1-10 Module Versions The ControlLogix ControlNet interface module is available in redundant (1756-CNBR) and non-redundant (1756-CNB) configurations. Either version may be used in the example applications, but for simplicity, we refer to both as the 1756-CNB module.
ControlNet Communication Basics Module Features The 1756-CNB module performs two primary tasks: 1. control of I/O data in conjunction with a Logix5550 controller (scheduled data) 2. support of messaging data for configuration and programming information (unscheduled data) The 1756-CNB module has these primary features: support for a maximum of 64 bidirectional connections with other ControlNet devices support of up to 20 buffers for unconnected messages...
To properly route the messages that it receives, the 1756-CNB must be supplied with the correct path information.To route an unscheduled message through the ControlLogix backplane, a path segment of “1 ss” is first required, where ss is the slot number of the module the message is being sent to.
3-5 for an example. Understanding the In traditional I/O systems, controllers poll input modules to obtain their input status. Digital input modules in the ControlLogix system are not Producer/Consumer Model polled by a controller. Instead, the modules produce (“multicast”) their data either upon a change of state or periodically.
For the PLC-5C send and receive scheduled messages are configured using the Map Editing Tool in RSNetWorx for ControlNet. For ControlLogix controllers, a consumed tag in the consumer must be specified exactly the same as a produced tag in the producer. In the following example, consumer_2 does not have the correct tags.
ControlNet Network When you place the module in the I/O configuration list of a Logix5550 controller and attach a second ControlLogix chassis to the same ControlNet network, you can perform remote control operations on the I/O in the second chassis.
ControlNet Communication Basics Understanding the Network Every ControlNet network requires at least one module that is able to store programmed parameters for the network and configure the network with Keeper those parameters upon start-up. This module is called a “keeper” since it keeps the network configuration.
ControlNet Communication Basics Actual Packet Interval (API) The API is the actual update rate for a particular piece of data on the network. ControlNet will set this rate equal to or faster than the RPI, based upon the binary multiple of the NUT which is the next fastest rate at which a module can send data.
Page 23
ControlNet Communication Basics Assume you have set up a system that contains 10 discrete I/O modules in a remote ControlNet chassis. If you used direct connections to transfer data to each of the these I/O modules, you would need 11 connections to transfer all of the data (one connection to the communication module and 1 connection to each of the ten I/O modules).
With this default ControlNet network, you can communicate between the various devices on the network by using such packages as RSNetWorx for ControlNet, RSLogix5000, and the ControlLogix Gateway Tool (1756-GTWY). If used in this default state, optimum performance may not be achieved.
Chapter Installing the ControlNet Network What this Chapter Contains This chapter describes how to install the ControlLogix and PLC-5C modules and connect them to the ControlNet network. For information about See page Installing the 1784-KTCX15 Communication Interface Card Installing the ControlLogix Modules...
Installing the ControlNet Network Installing the 1784-KTCX15 Perform the following steps to install the 1784-KTCX15 card in your personal computer. Communication Interface Card 1. Set the card’s base memory address location on switches S1 and S2. For detailed information on installing the 1784-KTCX15, refer to the ControlNet Communication Interface...
2. Select Configure Drivers from the Communications menu. The following window will appear: 3. Select the Allen-Bradley 1784-KT/KTC(X) device from the pull-down list and click on Add/New. 4. When prompted for a name for the new driver, select the default name assigned by the system, i.e., AB_KTC-1.
Page 28
Installing the ControlNet Network The Configure Device window will appear: 5. Enter the following configuration: Station Name ABKTC Net. Address Interrupt None I/O Base Mem. Address This is an unscheduled device. For maximum efficiency, set its address higher than the highest scheduled address on your network.
Installing the ControlNet Network Installing the ControlLogix Important: These instructions assume that you have installed your ControlLogix chassis and power supplies. If you have not Modules installed these components, install them now in accordance with the following instructions: ControlLogix Chassis Installation Instructions, publication number 1756-5.2...
Page 30
Installing the ControlNet Network 2. Install the1756-CNB modules, Logix5550 controllers, and ControlLogix I/O modules by placing them in the formed tracks on the top and bottom of the selected slots and sliding them into the chassis. Press firmly and evenly to seat a module in the backplane connector.
Installing the ControlNet Network Important: You can install or remove a module while chassis power is applied. ATTENTION: When you insert or remove a module while backplane power is on, an electrical arc may occur. An electrical arc can cause personal injury or property damage by: sending an erroneous signal to your system’s field devices causing unintended machine motion or loss...
Page 32
Installing the ControlNet Network 2. Connect the tap’s straight or right angle connector to the module’s BNC connector. If your node supports Connect the tap’s connector non-redundant media to the channel A connectors (1756-CNB, -CNBR) (channel B is not used) redundant media (1756-CNBR) from trunkline A to channel A from trunkline B to channel B...
2-10 Installing the ControlNet Network The following figure shows an example of a completed ControlNet network used for the examples in chapters 5 and 6 of this manual. PLC-5C 1771 I/O ControlLogix Chassis Chassis 1756-CNB Logix5550 ControlNet Trunk Cable Controller...
Chapter Logix5550 to Logix5550 Controller: Unscheduled Messaging This example application sends an unscheduled message from one About the Example Application Logix5550 controller to another Logix5550 controller. Both controllers are on the same ControlNet but in different chassis. In both chassis the controller is in slot 0 and the 1756-CNB module is in slot 1.
Logix5550 to Logix5550 Controller: Unscheduled Messaging Verify that the Logix5550 controllers and the 1756-CNB modules are in slots 0 and 1 in each ControlLogix chassis, as shown. Verify that the node addresses for the 1756-CNB modules are 1 and 6 as shown.
Logix5550 to Logix5550 Controller: Unscheduled Messaging Create the Controller Tags for the Write Message Program 1. Double-click on the Controller Tags folder in the project window. The Controller Tags window will appear. 2. Select the Edit Tags tab and create the following tags: Tag Name Alias For Base Tag...
Logix5550 to Logix5550 Controller: Unscheduled Messaging Create the Write Message Ladder Program 1. Double-click on Main Routine under the Main Program folder, and create the following ladder program: 2. Click on the button in the MSG instruction. The Message Configuration window will appear. 3.
Page 39
Logix5550 controller: 1, 1, 2, 6, 1, 0. For the path in this example: “1” indicates a connection to the backplane of the left ControlLogix chassis. “1” indicates a connection to the CNB module in slot 1. “2” indicates a connection to port 2 of the CNB module (get on the ControlNet wire).
Logix5550 to Logix5550 Controller: Unscheduled Messaging Download and Run the Program 1. Click on the Communications menu and select Who Active. 2. The Who Active window will appear (Your window may look different depending upon the drivers and other devices you have installed). 3.
Logix5550 to Logix5550 Controller: Unscheduled Messaging The New Controller window will appear. 3. Enter an appropriate Name for the Controller, e.g., “L1_from_L1”. 4. Select the correct Chassis Type and Slot Number of the Logix5550 controller, and the folder where you want to save the file (Create In). Then click on OK.
Page 42
Logix5550 to Logix5550 Controller: Unscheduled Messaging The Controller Tags window will appear. 2. Select the Edit Tags tab and create the following tags: Tag Name Type Style destination_data_buffer DINT Decimal 1756-6.5.3 - December 1999...
Logix5550 to Logix5550 Controller: Unscheduled Messaging Download the Test Program You do not need any ladder logic in the Test program. The program can consist of a single “End” rung. 1. Click on the Communications menu and select Who Active. 2.
3-10 Logix5550 to Logix5550 Controller: Unscheduled Messaging Test the Communications 1. Double-click on the Controller Tags folder in the Controller view window and select the Monitor Tags tab. You should see this value changing. 2. Examine the destination_data_buffer field. You should see the value changing to keep up with the accumulated value of the timer in the controller in the left chassis.
Chapter Logix5550 to Logix5550 Controller: Scheduled Communication About the Example Application This example application sends data from one Logix5550 controller (the producer) to another Logix5550 controller (the consumer). Both controllers are on the same ControlNet but in different chassis. In both chassis the controller is in slot 0 and the 1756-CNB module is in slot 1.
Logix5550 to Logix5550 Controller: Scheduled Communication Verify that the Logix5550 controllers and the 1756-CNB modules are in slots 0 and 1 in each ControlLogix chassis, as shown. Verify that the node addresses for the 1756-CNB modules are 1 and 6 as shown.
Logix5550 to Logix5550 Controller: Scheduled Communication Create the Producer Tags See Appendix B for additional information on producer tags. 1. Double-click on the Controller Tags folder in the project window. The Controller Tags window will appear. 2. Select the Edit Tags tab and create the following tags: Type Style produced_data...
Page 48
Logix5550 to Logix5550 Controller: Scheduled Communication 3. Produce the tag that is being sent. Either: Check the “P” box in the tag database: Check the “P” box in the tag database to make this a produced tag. -OR- Right-click on the tag select Edit Tag Properties. The Tag Properties window will appear: Make sure this box is checked.
Logix5550 to Logix5550 Controller: Scheduled Communication Create the Producer Ladder Program 1. Double-click on Main Routine under the Main Program folder, and create the following ladder program: Download to the Producer 1. Click on the Communications menu and select Who Active. 2.
Logix5550 to Logix5550 Controller: Scheduled Communication 5. Put the controller in Run mode. 6. Minimize RSLogix5000. Configure the Consumer In order to test the application you have to create a consumer controller, add the producer controller to the I/O configuration of the consumer controller, Logix5550 Controller and create a consumed tag to receive the data.
Page 51
Logix5550 to Logix5550 Controller: Scheduled Communication Add the Local CNB Module to the I/O Configuration 1. Select the I/O Configuration folder in the project window and click the right mouse button The following pop-up menu will appear. 2. Select New Module. The Select Module Type window will appear.
Page 52
Logix5550 to Logix5550 Controller: Scheduled Communication The Module Properties window will appear. 4. Enter the following parameters: Name Local_CNB Slot Electronic Keying Compatible Module 5. Click on Finish to accept the configuration. 1756-6.5.3 - December 1999...
Page 53
Logix5550 to Logix5550 Controller: Scheduled Communication Add the Remote CNB Module to the I/O Configuration Next, you must add the remote 1756-CNB as a “child” of the local 1756-CNB. 1. In the Project window, right click on the local 1756-CNB and select New Module.
Page 54
4-10 Logix5550 to Logix5550 Controller: Scheduled Communication The Module Properties window will appear. 3. Enter the following parameters: Name Remote_CNB Node Chassis Size (Enter your chassis size) Slot Comm Format None Electronic Keying Compatible Module 4. Click on Finish to accept the configuration. The remote 1756-CNB module should appear indented under the local 1756-CNB in the I/O Configuration folder.
Page 55
Logix5550 to Logix5550 Controller: Scheduled Communication 4-11 Add the Remote Controller to the I/O Configuration You must now add the remote Controller to the I/O Configuration List under the remote 1756-CNB module. 1. Right click on the remote 1756-CBN or -CNBR under the I/O Configuration folder and select New Module.
4-12 Logix5550 to Logix5550 Controller: Scheduled Communication 3. Enter the following parameters: Name Producer Slot 4. Click on the Finish button to accept the configuration. The I/O Configuration tree should look similar to the one shown below. See Appendix B for additional Create the Consumer Tags information on consumer tags.
Page 57
Logix5550 to Logix5550 Controller: Scheduled Communication 4-13 The Controller Tags window will appear. 2. Select the Edit Tags tab and create the following tag: Tag Name Type Style consumed_data DINT Decimal 3. Right-click on the new tag. The following pop-up menu will appear: 4.
Page 58
4-14 Logix5550 to Logix5550 Controller: Scheduled Communication The New Tag window will appear. 5. Enter the following parameters: Name consumed_data Tag Type Consumed Controller Producer Remote Tag produced_data Data Type DINT Style Decimal These parameters must match those in the producer. Remember that the RPI cannot be faster than the NUT.
Logix5550 to Logix5550 Controller: Scheduled Communication 4-15 Download to the Consumer You do not need any ladder logic in the Consumer program. The program can consist of a single “End” rung. 1. Click on the Communications menu and select Who Active. The Who Active window will appear (Your window may look different depending upon the drivers and other devices you have installed).
4-16 Logix5550 to Logix5550 Controller: Scheduled Communication Schedule the Network Using Before scheduled communication can take place, you must run RSNetWorx for ControlNet to schedule the network. Running RSNetWorx transfers RSNetWorx for ControlNet configuration data to networked modules and establishes a Network Update Time (NUT) for ControlNet that is compliant with the desired communication options specified for each module.
Logix5550 to Logix5550 Controller: Scheduled Communication 4-17 4. Select the AB_KTC-1, ControlNet driver and click on OK. The software will browse the network. When it is finished, your network window should appear similar to that shown below: 5. Verify that the devices shown and the network node addresses displayed are correct.
Page 62
4-18 Logix5550 to Logix5550 Controller: Scheduled Communication 2. Make sure that these parameters to are set to the following values: In this field Select Network_Update_Time (ms) 5 ms Max Scheduled Address Max Unscheduled Address Remember that the requested packet interval (RPI) for any of the devices on the network cannot be faster than the NUT.
Page 63
Logix5550 to Logix5550 Controller: Scheduled Communication 4-19 The following pop-up window will appear: 6. Select “Optimize and re-write schedule for all connections” and click on The Save As window will appear 7. Enter an appropriate name for the network (e.g., “Sched_L1_to_L1”) and click on Save.
4-20 Logix5550 to Logix5550 Controller: Scheduled Communication Test the Communications 1. Restore the session of RSLogix5000 for the Consumer controller. 2. Double-click on the Controller Tags folder in the Controller view window and select the Monitor Tags tab. You should see this value changing. 3.
This example application sends an unscheduled message from a Logix5550 processor to a PLC-5C processor. The Logix5550 processor is in slot 0 of the ControlLogix chassis and the1756-CNB module (configured as node 1) is in slot 1. The PLC-5C is configured as ControlNet node 11. A Counter that increments continuously provides the test data for the message.
Logix5550 Controller to PLC-5C: Unscheduled Messaging Verify that the KTCX15 driver card is configured as described on page 2-3. Verify that all wiring and cabling is properly connected. Create the Example Application Perform the following steps to create the example application: 1.
Logix5550 Controller to PLC-5C: Unscheduled Messaging Create the Controller Tags for the Write Message Program You must create a source tag for the message under the controller scope and assign it the same data type as the destination element (e.g., INT). 1.
Logix5550 Controller to PLC-5C: Unscheduled Messaging 3. Select the Monitor Tags tab. 4. Enter a 1 in the PLUS_ONE field. Create the Write Message Ladder Program 1. Double-click on Main Routine under the Main Program folder, and enter the following ladder program: 2.
Page 69
PLC-5C on ControlNet. For the path in this example: “1” indicates a connection to the backplane of the ControlLogix chassis. “1” indicates a connection to the CNB module in slot 1. “2” indicates a connection to port 2 of the CNB module (get on the ControlNet wire).
Logix5550 Controller to PLC-5C: Unscheduled Messaging If the Cache Connections option is selected, the controller keeps the connection open after it completes the data transfer. The next data transfer uses the open connection and avoids the delay required to open the connection.
Logix5550 Controller to PLC-5C: Unscheduled Messaging Test the Example Application Perform the following steps to test the example application: 1. Start the RSLogix5 software. 2. From the Comms menu in RSLogix5, select System Comms. The System Options window will appear with the System Communications tab open.
Page 72
Logix5550 Controller to PLC-5C: Unscheduled Messaging 4. Select the AB_KTC-1, ControlNet driver and double-click on the PLC-5 processor at node 11 (1785-L40C15 in the above example). 5. When the System Communications tab reappears, click on the Online button. If no program is loaded in the PLC-5C processor, a pop-up window will appear with the message “You cannot go Online to DEFAULT program.”...
This example application sends scheduled data from a Logix5550 controller (producer) to a PLC-5C processor (consumer). The Logix5550 controller is in slot 0 of the ControlLogix chassis and the 1756-CNB module (configured as node 1) is in slot 1. The PLC-5C is configured as node 11. A Timer provides the data for the message.
Logix5550 Controller to PLC-5C: Scheduled Communications Verify that the Logix5550 controller and the 1756-CNB module are in slots 0 and 1 as shown. Verify that the node address for the 1756-CNB module is 1 and the node address for the PLC-5C processor is 11 as shown. Verify that the KTCX15 driver card is configured as described on page 2-3.
Logix5550 Controller to PLC-5C: Scheduled Communications Create the Producer Tags See Appendix B for additional information on producer tags. Controller tags are created using the project window on the left side of the screen. 1. Double-click on Controller Tags under the Controller folder. The Controller Tags window will appear.
Page 76
Logix5550 Controller to PLC-5C: Scheduled Communications 3. Produce the tag that is being sent. Either: Check the “P” box in the tag database to make this a produced tag. Check the “P” box in the tag database: -OR- Right-click on the tag and select Edit Tag Properties. The Tag Properties window will appear: Make sure this box is checked.
Logix5550 Controller to PLC-5C: Scheduled Communications For two-way communication you can also configure a consumed tag for this controller. See chapter 8 for details. See Appendix B and the Logix5550 Controller User Manual, publication 1756-6.5.12, for more information on creating produced and consumed tags.
Logix5550 Controller to PLC-5C: Scheduled Communications Download and Run the Program 1. Click on the Communications menu and select Who Active. 2. The Who Active window will appear (Your window may look different depending upon the drivers and other devices you have installed). 3.
Logix5550 Controller to PLC-5C: Scheduled Communications Schedule the Network Using Before communication can take place, you must run RSNetWorx for ControlNet to configure the PLC-5C processor as the consumer and RSNetWorx for ControlNet schedule the network. Running RSNetWorx transfers configuration data to networked modules and establishes a Network Update Time (NUT) for ControlNet that is compliant with the desired communication options specified for each module.
Page 80
Logix5550 Controller to PLC-5C: Scheduled Communications The Browse for Network window will appear with a list of available drivers. (Your list may appear different from that shown below, but you should have the AB_KTC-1 driver configured as described in chapter 2.) 4.
Logix5550 Controller to PLC-5C: Scheduled Communications 6. Enter an appropriate name for the network (e.g., “Sched_Logix5550_to_PLC5”) and click on Save. Your ControlNet network should appear similar to that shown below: 7. Verify that the devices shown and the network node addresses displayed are correct.
6-10 Logix5550 Controller to PLC-5C: Scheduled Communications 2. Make sure that these parameters to are set to the following values: In this field Select Network_Update_Time (ms) 5 ms Max Scheduled Address Max Unscheduled Address Remember that the requested packet interval (RPI) for any of the devices on the network cannot be faster than the NUT.
Logix5550 Controller to PLC-5C: Scheduled Communications 6-11 RSNetWorx for ControlNet will survey the network for connected devices. When it is finished, the network window should appear similar to that shown below. Configure the PLC-5C to Receive Scheduled Messages 1. Right-click on the PLC5 icon in the RSNetWorx window. The following pop-up window will appear: 2.
Page 84
6-12 Logix5550 Controller to PLC-5C: Scheduled Communications The PLC-5C ControlNet Configuration window will open. Right-click on the 1756L1 3. Right-click on the 1756L1 processor. 4. Select “Insert Receive Scheduled Message.” 1756-6.5.3 - December 1999...
Logix5550 Controller to PLC-5C: Scheduled Communications 6-13 The Receive Scheduled Message configuration window will appear: 5. Enter the following parameters and click on OK. In this field Enter Node Number Slot Number produced_data Requested Packet Interval (use default) Message Size 2 (for DINT) This is the name of the tag created in RSLogix 5000.
6-14 Logix5550 Controller to PLC-5C: Scheduled Communications The following pop-up window will appear: 8. Select “Optimize and re-write schedule for all connections” and click on OK. 9. Close the PLC-5 ControlNet Configuration window and Minimize the RSNetWorx for ControlNet software. Test the Communications You now have the ControlNet network commissioned.
Page 87
Logix5550 Controller to PLC-5C: Scheduled Communications 6-15 The RSWho window will appear (Your window may appear different, depending on the drivers and devices installed on your system). 4. Double-click on the PLC-5C processor at node 11 (1785-L40C15 in this example). 5.
Page 88
6-16 Logix5550 Controller to PLC-5C: Scheduled Communications You you will receive the following warning: This warning is telling you that you need to tell RSLogix5 which RSNetWorx for ControlNet project file is associated with this PLC-5 so that the two packages can exchange information about the I/O. You will take care of this shortly.
Page 89
Logix5550 Controller to PLC-5C: Scheduled Communications 6-17 10.Double-click on Controller Properties in the Project tree. The Controller Properties window will appear: 11.Verify/Enter the following parameters: In this field Enter Processor Name CONSUMER PLC ControlNet Node 12.Click on the Browse button and Open the RSNetWorx for ControlNet project file created previously (e.g., “Sched_Logix5550_toPLC5.xc”).
Page 90
6-18 Logix5550 Controller to PLC-5C: Scheduled Communications To verify that the message is being received by the PLC-5C processor, you must examine the input file configured in RSNetWorx for ControlNet (i.e., N9). Examine this file. 14.Double-click on file N9 in the Data Files folder. You should see the value in N9:0 continuously changing to reflect the data from the Logix5550 controller.
This example application sends an unscheduled message from a PLC-5C to a Logix5550 controller. The PLC-5C is at ControlNet node 11. The Logix5550 controller is in slot 0 of the ControlLogix chassis and the1756-CNB module (configured as ControlNet node 1) is in slot 1. The PLC-5C’s seconds timer (S:23) provides the test data for the message.
PLC-5C to Logix5550 Controller: Unscheduled Messaging Verify that the node address for the 1756-CNB module is 1 and the node address for the PLC-5C is 11 as shown. Verify that the KTCX15 driver card is configured as described on page 2-3. Verify that all wiring and cabling is properly connected.
PLC-5C to Logix5550 Controller: Unscheduled Messaging Create the PLC-5C Program 1. Enter the following ladder program: 2. Double-click on Setup Screen in the MSG instruction. The following window will appear. 3. Under the General tab in the message Setup Screen, enter the following configuration: In this field Select...
Page 94
To Address Type To Address This PLC5 1756-CNB Node (dec) ControlLogix Backplane 1756 Backplane Slot (dec) 6. From the Edit menu, select Verify Project. 7. Select the Save As option from the File menu. 8. Enter an appropriate file name (e.g., “PLC5_to_LOGIX5550”) and click on Save.
PLC-5C to Logix5550 Controller: Unscheduled Messaging Download the PLC-5C Program 1. From the Comms menu, select System Communications. The System Options window will appear with the System Communications tab open. 2. Select AB_KTC-1 as the Driver and click on Who Active. The RSWho window will appear (Your window may appear different, depending on the drivers and devices installed on your system).
Page 96
PLC-5C to Logix5550 Controller: Unscheduled Messaging 4. When the System Communications tab reappears, click on the Download button. You will see a window similar to that below. 5. Click on Yes to download the program. It is not necessary to keep the existing Online ControlNet configuration.
PLC-5C to Logix5550 Controller: Unscheduled Messaging Test the Example Application In order to test the application you have to go online with the Logix5550 controller and create a tag for the buffer to receive the message. Perform the following steps: 1.
PLC-5C to Logix5550 Controller: Unscheduled Messaging Create the Controller Tags for the Logix5550 Controller 1. Double-click on the Controller Tags folder in the project window. The Controller Tags window will appear. 2. Select the Edit Tags tab and create the following tag: Tag Name Type Style...
Page 99
PLC-5C to Logix5550 Controller: Unscheduled Messaging 3. From the Logic menu, select Map PLC/SLC Messages. 4. Select the File Number used in the PLC-5C Typed Write message setup (i.e., number 7). 5. Select the Logix5550 Tag Name created previously (PLC5_Data). 6.
7-10 PLC-5C to Logix5550 Controller: Unscheduled Messaging Download the Logix5550 Program You do not need any ladder logic in the Logix5550 program. The program can consist of a single “End” rung. 1. Click on the Communications menu and select Who Active. 2.
PLC-5C to Logix5550 Controller: Unscheduled Messaging 7-11 Verify the Message 1. Double-click on the Controller Tags folder in the project window and select the Monitor Tags tab. You should see this value changing. 2. Examine the PLC5_Data field. You should see that it is incrementing once a second to reflect the seconds timer in the PLC-5C processor sending the message.
Page 102
7-12 PLC-5C to Logix5550 Controller: Unscheduled Messaging 1756-6.5.3 - December 1999...
Logix5550 controller (consumer). The PLC-5C is ControlNet node 11; the 1756-CNB module is node 1. The Logix5550 controller is in slot 0 of the ControlLogix chassis and the 1756-CNB is in slot 1. The PLC-5C’s seconds timer (S:23) provides the data for the message.
PLC-5C to Logix5550 Controller: Scheduled Communications Verify that the Logix5550 controller and the 1756-CNB module are in slots 0 and 1 as shown. Verify that the node address for the 1756-CNB module is 1 and the node address for the PLC-5C processor is 11 as shown. Verify that the KTCX15 driver card is configured as described on page 2-3.
Page 105
PLC-5C to Logix5550 Controller: Scheduled Communications The Browse for Network window will appear with a list of available drivers. (Your list may appear different from that shown below, but you should have the AB_KTC-1 driver configured as described in chapter 2.). 4.
PLC-5C to Logix5550 Controller: Scheduled Communications RSNetWorx for ControlNet will browse the network for the attached devices. When it is done browsing, your ControlNet network should appear similar to that shown below: 7. Verify that the devices shown and their network node addresses are correct.
PLC-5C to Logix5550 Controller: Scheduled Communications 2. Make sure that these parameters to are set to the following values: In this field Select Network_Update_Time (ms) 5 ms Max Scheduled Address Max Unscheduled Address Remember that the requested packet interval (RPI) for any of the devices on the network cannot be faster than the NUT.
PLC-5C to Logix5550 Controller: Scheduled Communications When RSNetWorx for ControlNet is finished surveying, the network window should appear similar to that shown below. Configure the PLC-5C Processor 1. Right-click on the PLC-5C icon in the RSNetWorx window. The following pop-up window will appear: 2.
Page 109
PLC-5C to Logix5550 Controller: Scheduled Communications The PLC-5C ControlNet Configuration window will open. 3. Make sure that the Edits Enabled box is checked and right-click on the PLC-5 processor. The following pop-up window will appear: 4. Select “Insert Send Scheduled Message.” The Send Scheduled Message window will appear: 1756-6.5.3 - December 1999...
Page 110
PLC-5C to Logix5550 Controller: Scheduled Communications 5. Accept and record the default Message Number. You will enter this as the “Remote Instance Number” in the Logix5550 controller configuration. 6. Set the Message Size to 2. 7. Click on OK. A new configuration line in blue text will appear: This new configuration line will appear.
PLC-5C to Logix5550 Controller: Scheduled Communications Configure the Consumer In order to test the application you must configure the Logix 5550 controller as a consumer, add the producer to the I/O configuration of the consumer, Logix5550 Controller and create a consumed tag to receive the data. Perform the following steps to create the consumer: 1.
8-10 PLC-5C to Logix5550 Controller: Scheduled Communications Add the Producer to the I/O Configuration I/O configuration is done using the project window on the left side of the screen. 1. Right-click on the I/O Configuration folder in the project window and select New Module from the pop-up window that appears.
Page 113
PLC-5C to Logix5550 Controller: Scheduled Communications 8-11 The Module Properties window will appear. 3. Enter the following parameters: Name Local_CNB Slot Electronic Keying Compatible Module 4. Click on Finish to accept the configuration of the 1756-CNB module. The Local_CNB module will appear indented under the I/O Configuration folder.
Page 114
8-12 PLC-5C to Logix5550 Controller: Scheduled Communications The Select Module Type window will appear. 6. Select the 1785-PLC5C module and click on OK. The Module Properties window will appear: 7. Enter the following parameters: Name Producer Node 8. Click on the Finish button to accept the configuration. 1756-6.5.3 - December 1999...
PLC-5C to Logix5550 Controller: Scheduled Communications 8-13 The Producer PLC5C will now appear indented under the local 1756-CNB in the I/O Configuration folder. See Appendix B for additional Create the Consumer Tags information on consumer tags. The consumer tags are created using the project window on the left side of the screen.
Page 116
8-14 PLC-5C to Logix5550 Controller: Scheduled Communications The Data Type configuration window will appear: 2. Enter the following Data Type parameters: Name Consumed_data Members Name Data Type Style Consumed_1 DINT Decimal PLC5_data INT[2] Decimal See Appendix B and the Logix5550 Controller User Manual, publication 1756-6.5.12, for more information on creating consumed tags.
Page 117
PLC-5C to Logix5550 Controller: Scheduled Communications 8-15 You must now configure the consumed tags under the controller scope. 4. Double-click on Controller Tags in the project folder. The Controller Tags window will appear. 5. Select the Edit Tags tab and create the following tag: Tag Name Type PLC5_data...
Page 118
8-16 PLC-5C to Logix5550 Controller: Scheduled Communications The following pop-up window will appear. 7. Select Edit Tag Properties. The New Tag configuration window will appear: 8. Enter the following parameters: Name PLC5_data Tag Type Consumed Controller PRODUCER Remote Instance Data Type Consumed_data The Remote Instance must match the Message Number assigned by RSNetWorx for ControlNet.
PLC-5C to Logix5550 Controller: Scheduled Communications 8-17 9. Click on OK to save the tag configuration. 10.Save the RSLogix5000 program. For two-way communication you can also configure a produced tag for the Logix5550 controller at this time. See chapter 6 for details. Download the Logix5550 Program You do not need any ladder logic in the Consumer program.
8-18 PLC-5C to Logix5550 Controller: Scheduled Communications Create the Producer Perform the following steps to create the PLC-5C producer application: Application 1. Start the RSLogix5 software. 2. From the File menu, select New. The Select Processor Type window will appear. 3.
PLC-5C to Logix5550 Controller: Scheduled Communications 8-19 Create the PLC-5C Program 1. Enter the following ladder program: N10 is the Output File configured in RSNetWorX for ControlNet. The data will be sent to an integer array of size 2 (PLC5_data) in the Logix5550 processor.
Page 122
8-20 PLC-5C to Logix5550 Controller: Scheduled Communications The RSWho window will appear (Your window may appear different, depending on the drivers and devices installed on your system.). 3. Double-click on the PLC-5/40C processor at node 11. 4. When the System Communications tab reappears, click on the Download button.
Page 123
PLC-5C to Logix5550 Controller: Scheduled Communications 8-21 You should see the Data Output File (i.e., N10) you configured with RSNetWorx for ControlNet in the following prompt: 7. Click on Yes to continue the download using these ControlNet files. 8. When prompted, save the program. 9.
8-22 PLC-5C to Logix5550 Controller: Scheduled Communications Schedule the Network Whenever you change the network configuration you must run RSNetWorx for ControlNet to reschedule the network. 1. Restore RSNetWorx for ControlNet and click on the Enable Edits box. 2. From the Selection menu, select Survey Network. 3.
PLC-5C to Logix5550 Controller: Scheduled Communications 8-23 Verify the Message 1. Restore RSLogix5550. 2. Double-click on the Controller Tags folder in the Project window and select the Monitor Tags tab. You should see these values changing with an offset of 5. 3.
Page 126
8-24 PLC-5C to Logix5550 Controller: Scheduled Communications 1756-6.5.3 - December 1999...
In this example you establish communications between two PLC-5C processors on different ControlNet networks. Two 1756-CNB modules in the same ControlLogix chassis are used to bridge the networks. The 1756-CNB modules are in slots 1 and 3 and are configured as nodes 1 and 6, respectively.
PLC-5C to PLC-5C Unscheduled Messaging Over Two ControlNet Networks Verify that the 1784-KTCX15 driver card is configured as described on page 2-3. Verify that all wiring and cabling is properly connected. Create the Example Application Perform the following steps to create the example application: 1.
PLC-5C to PLC-5C Unscheduled Messaging Over Two ControlNet Networks Create the Ladder Program 1. Enter the following ladder program: 2. Double-click on Setup Screen in the MSG instruction. The following window will appear. This message writes the value of the seconds clock (S:23) in the PLC-5/40C on ControlNet network #1 into data file N7:0 of the PLC-5/40C processor on...
Page 130
From Device From Port To Address Type To Address This PLC5 1756-CNB Node (dec) ControlLogix Backplane 1756 Backplane Slot (dec) 1756-CNB ControlNet Node (dec) 6. From the Edit menu, select Verify Project. 7. Save the file. 1756-6.5.3 - December 1999...
PLC-5C to PLC-5C Unscheduled Messaging Over Two ControlNet Networks Download the Program 1. From the Comms menu, select System Communications. The System Options window will appear with the System Communications tab open. 2. Select AB_KTC-1 as the Driver and click on Who Active. The RSWho window will appear (Your window may appear different depending upon the drivers and other devices you have installed).
PLC-5C to PLC-5C Unscheduled Messaging Over Two ControlNet Networks You will see a window similar to the following one. 5. Click on Yes to download the program. It is not necessary to keep the existing Online ControlNet configuration. 6. Go Online and put the processor in Run mode. 7.
Page 133
PLC-5C to PLC-5C Unscheduled Messaging Over Two ControlNet Networks 3. Click on Who Active. The RSWho window will appear. (Your window may look different depending upon the drivers and other devices you have installed). 4. Drill down the tree through the ControlNet driver to the PLC-5/40C processor at ControlNet node 16 (1785-L40C15 in this example).
Page 134
PLC-5C to PLC-5C Unscheduled Messaging Over Two ControlNet Networks 7. Double-click on N7 in the data file list. You should see the following screen: Verify that this value is being updated. When you see N7:0 being updated at one second intervals the message is being sent successfully from the PLC-5C processor on ControlNet network #1, node 11, to the PLC-5C processor on ControlNet network #2, node 16.
The basic procedure given in this example can also be used to configure and schedule FLEX I/O on a ControlNet network. The local ControlLogix chassis contains the Logix5550 controller in slot 0 and the “parent” 1756-CNB module (configured as node 1) in slot 1. The remote chassis contains a “child”...
10-2 Controlling I/O Over a ControlNet Network Set Up the Example Application Change your system configuration to that shown below: Slot 0 1 Slot 1 2 3 Local Data Remote Chassis Chassis 1756-OB16I 1756-CNB Logix5550 1756-CNB Digital Output Controller (Node 1) (Node 6) ControlNet Network 1756-IB16...
Controlling I/O Over a ControlNet Network 10-3 3. Enter an appropriate name for the Controller, e.g., “I/O Controller.” 4. Select the correct Chassis Type, Slot Number of the Logix5550 controller, and folder where you want to save the file (Create In). Click on OK.
10-4 Controlling I/O Over a ControlNet Network The Select Module Type window will appear. 3. Select the 1756-CNB/B or 1756-CNBR/B module and click on OK. The Module Properties window will appear. 4. Enter the following parameters: Name Local_CNB Slot Electronic Keying Compatible Module 5.
Page 139
Controlling I/O Over a ControlNet Network 10-5 In a FLEX I/O system, you would add a FLEX ControlNet adaptor instead of the remote CNB module. 1. In the Project window, right click on the local 1756-CNB under the I/O Configuration folder and select New Module from the pop-up window. The Select Module Type window will appear.
Page 140
10-6 Controlling I/O Over a ControlNet Network The Module Properties window will appear. 3. Enter the following parameters: Name Remote_CNB Node Chassis Size (Enter your chassis size) Slot Comm Format Rack Optimization Electronic Keying Compatible Module 4. Click on Next. The following page will appear: 5.
I/O modules for your system. This example application uses the I/O module default configurations. For information on altering the default configurations see the ControlLogix Digital I/O Module User Manual, publication 1756-6.5.8. Add the Remote Digital Input Module 1.
Page 142
Electronic Keying Compatible Module If you want to alter the default parameters, click on Next. Refer to the ControlLogix Digital I/O User Manual, publication 1756-6.5.8, for details. 4. Click on the Finish button to accept the configuration. 1756-6.5.3 - December 1999...
Page 143
Controlling I/O Over a ControlNet Network 10-9 The digital input module will appear indented under the remote 1756-CNB module. Add the Remote Digital Output Module 5. Right click on the remote 1756-CNB module and again select New Module. The Select Module Type window will appear. 6.
Page 144
Compatible Module If you want to alter the default parameters, click on Next. Refer to the ControlLogix Digital I/O User Manual, publication 1756-6.5.8, for details. 8. Click on the Finish button to accept the configuration. The I/O Configuration in the Project window should look similar to the one shown below.
Controlling I/O Over a ControlNet Network 10-11 Edit the Controller Tags 1. Double-click on the Controller Tags folder in the project window. Note that the system has created the tags for the remote 1756-CNB module and for the remote digital I/O modules. User creates this tag.
10-12 Controlling I/O Over a ControlNet Network Create the Ladder Logic Program 1. Double-click on Main Routine under the Main Program folder, and enter the following program: 2. Save the program, using an appropriate name (e.g. “Remote_IO”). Download the Program 1.
Controlling I/O Over a ControlNet Network 10-13 3. Drill down the tree through the ControlNet driver and the 1756-CNB module at node 1 to the controller in slot 0. 4. Highlight the controller and click on the Download button to download the program to the Logix5550 controller in the local chassis.
Page 148
10-14 Controlling I/O Over a ControlNet Network The Browse for Network window will appear with a list of available drivers. (Your list may appear different from that shown below, but you should have the AB_KTC-1 driver configured as described in chapter 2.).
Controlling I/O Over a ControlNet Network 10-15 RSNetWorx will browse the network for the attached devices. When it is done browsing, your network window should appear similar to that shown below: 7. Verify that the devices and their network node addresses displayed are correct.
10-16 Controlling I/O Over a ControlNet Network 2. Make sure that these parameters to are set to the following values: In this field Select Network_Update_Time (ms) 5 ms Max Scheduled Address Max Unscheduled Address Remember that the requested packet interval (RPI) for any of the devices on the network cannot be faster than the NUT.
Controlling I/O Over a ControlNet Network 10-17 When RSNetWorx for ControlNet is finished surveying, the network window should appear similar to that shown below. Schedule the Network and Save the Configuration 1. From the Network menu, select Save. The following pop-up window will appear: 2.
LEDs on the 1756-OB16I output module turn off. Refer to the ControlLogix Digital I/O Modules User Manual, publication 1756-6.5.8, for assistance in wiring and debugging the I/O modules. This completes the scheduled I/O example.
Chapter Adding an I/O Chassis to an Existing ControlNet Network About the Example Application Each 1756-CNB interface module can support up to 64 bidirectional connections. This example application expands the ControlNet network from the previous chapter by adding another remote I/O chassis. The new remote chassis contains another “child”...
11-2 Adding an I/O Chassis to an Existing ControlNet Network Set Up the Example Application Change the system configuration of the previous chapter to that shown below by adding the second remote chassis with a 1756-CNB module and a 1756-OF6VI analog output module: Slot 0 1 Slot 1 2 3...
Adding an I/O Chassis to an Existing ControlNet Network 11-3 Add the Second Remote 1756-CNB Module to the I/O Configuration 1. Right click on the local 1756-CNB under the I/O Configuration folder and select New Module from the pop-up window. The Select Module Type window will appear.
Page 156
11-4 Adding an I/O Chassis to an Existing ControlNet Network The Module Properties window will appear. 3. Enter the following parameters: Name Remote_CNB_2 Node Chassis Size (Enter your chassis size) Slot Comm Format None Electronic Keying Compatible Module 4. Click on the Next button. The following page will appear. 5.
I/O module for your system. For additional information on configuring an analog I/O module see the ControlLogix Analog I/O Module User Manual, publication 1756-6.5.9. 1. Right click on the Remote_CNB_2 module under the I/O Configuration folder and select New Module from the pop-up window.
Page 158
You will now configure the channel settings of the I/O module. When you do this a series of pages will appear in the Module Properties window. For a detailed explanation of the following pages, see the ControlLogix Analog I/O User Manual, publication 1756-6.5.9.
Page 159
Adding an I/O Chassis to an Existing ControlNet Network 11-7 4. Click on the Next button. The following page will appear: 5. Make sure the Requested Packet Interval (RPI) is set to 5ms or greater. Important: The RPI cannot be set to a rate faster than the network update time (NUT).
Page 160
11-8 Adding an I/O Chassis to an Existing ControlNet Network The choices available on the Channel Configuration pages will vary according to the module being configured. The page below appears for the 1756-OF6VI module. 8. Click on Channel 0 and enter the following Scaling parameters: High Signal High Engineering 10.0 V...
Adding an I/O Chassis to an Existing ControlNet Network 11-9 11.Click on Finish to accept the configuration. The I/O Configuration tree should now look similar to the one shown below. Edit the Controller Tags 1. Double-click on the Controller Tags folder in the project window. 2.
11-10 Adding an I/O Chassis to an Existing ControlNet Network 3. Select the Edit Tags tab at the bottom of the Controller Tags window. 4. Create the following tag: Tag Name Type Analog_Output Timer Modify the Ladder Program 1. Double-click on Main Routine under the Main Program folder, and add rungs 3 and 4 to the ladder program: 2.
Adding an I/O Chassis to an Existing ControlNet Network 11-11 3. Drill down the tree through the ControlNet driver and the 1756-CNB module at node 1 to the controller in slot 0. 4. Highlight the controller and click on the Download button. 5.
Page 164
11-12 Adding an I/O Chassis to an Existing ControlNet Network The Browse for Network window will appear with a list of available drivers. (Your list may appear different from that shown below, but you should have the AB_KTC-1 driver configured as described in chapter 2.).
Adding an I/O Chassis to an Existing ControlNet Network 11-13 RSNetWorx for ControlNet will browse the network for the attached devices. When it is done browsing, your ControlNet network should appear similar to that shown below: 7. Verify that the devices shown and their network node addresses are correct.
11-14 Adding an I/O Chassis to an Existing ControlNet Network 2. Make sure that these parameters to are set to the following values: In this field Select Network_Update_Time (ms) 5 ms Max Scheduled Address Max Unscheduled Address Remember that the requested packet interval (RPI) for any of the devices on the network cannot be faster than the NUT.
Adding an I/O Chassis to an Existing ControlNet Network 11-15 When RSNetWorx for ControlNet is finished surveying, the network window should appear similar to that shown below. Schedule the Network and Save the Configuration 1. From the File menu, select Save. The following pop-up window will appear: 2.
4. Verify that the digital I/O modules in the other remote chassis are still working. See page 10-18. Refer to the ControlLogix Analog I/O Modules User Manual, publication 1756-6.5.9, and the ControlLogix Digital I/O Modules User Manual, publication 1756-6.5.8, for assistance in wiring and debugging the I/O modules, if needed.
Adding an I/O Chassis to an Existing ControlNet Network 11-17 Adding 1756-CNB Modules to The ControlNet network in the example application can support a maximum of 64 remote bidirectional connections. To expand the network you can add Expand the Network additional 1756-CNB interface modules to the local chassis and connect them to remote 1756-CNB modules on the same or another ControlNet network.
Page 170
11-18 Adding an I/O Chassis to an Existing ControlNet Network The RSLogix5000 I/O configuration for the expanded network is shown in the following figure. To add remote I/O modules to the configuration, add them to the remote 1756-CNB modules as you did in the example application.
Chapter Troubleshooting The 1756-CNB and 1756-CNBR modules are provided with the LED diagnostic indicators shown below. The diagnostics provided by these indicators is described in the following sections. 1756-CNB 1756-CNBR module status display and module status display and network network addressdescribed on page 14 address module status indicator...
Page 172
The module has detected that Change this node’s address to a it is unable to be the keeper value of 2 or greater. Contact for this network due to a Allen-Bradley for a compatible firmware incompatibility. firmware update. BPIC There is a hardware fault Replace the module.
Troubleshooting 12-3 Display Cause Action Green or BPRX Too many CRC errors being Cycle power on the module or send Flashing generated by the multicast a reset to the module. If condition Green backplane receiver, so the persists, replace the module. backplane multicast receivers (This error is caused by a module have been shut off.
Page 174
12-4 Troubleshooting Cause Action Alternating red/off Incorrect node configuration Check network address and other ControlNet configuration parameters. Channel disabled Program network for redundant media, if required. Steady green Normal operation None. Flashing green/off Temporary errors None; unit will self-correct. Node is not configured to go Make sure the Keeper node is on line present and working...
You indirectly determine the number of connections that the Logix5550 controller requires by configuring the controller to communicate with other devices in the system. Each module in the ControlLogix system supports a limited number of active connections. Take these connection limits into account when designing your system.
Interface module 1756-ENET ControlLogix Ethernet Bridge 64 TCP/IP connections 48 ControlLogix connections maximum per 1 TCP/IP connection 128 ControlLogix connections maximum per module The Ethernet module also supports 128 in and 128 out unscheduled ControlLogix connections. Unscheduled connections within a TCP/IP connection do not count toward the total of 48 possible ControlLogix connections.
Allocating Communication Connections If the module configuration is appropriate for the I/O module found in the slot, a connection is made and operation begins. If the module configuration is not appropriate, the connection is rejected. You can view the fault message on the Connection tab of the module’s properties.
Page 178
Allocating Communication Connections In this example, the owner controller communicates with all the digital I/O in the remote chassis but uses only one connection. The data from all three modules is sent together simultaneously at a rate specified by the 1756-CNB connection.
Allocating Communication Connections To configure an I/O module for a rack optimized connection, you select the Rack Optimization communication format. Most discrete I/O modules support a rack optimized connection. If this option does not appear when you are selecting communication format for an I/O module, the module does not support the rack optimized connection.
Allocating Communication Connections The local controller in this example uses these bidirectional connections: Connection Type Module Quantity Connections Total per Module Connections Logix5550 controller to local I/O module Logix5550 controller to remote analog I/O module Logix5550 controller to remote 1756-CNB module total Determining Connections for The Logix5550 controller supports the ability to produce (broadcast) and...
Allocating Communication Connections Optimizing produced tags Each produced tag requires connections that can be used for other controller operations. To minimize the of produced tags, and the number of required connections, consider grouping data into an array or a user-defined structure and producing only that array or structure, as long as the array or structure is not larger than 500 bytes.
Allocating Communication Connections Determining Connections Some types of messages use a connection to send or receive data. Some also give you the option of either leaving the connection open (cache) or closing for Messaging the connection when the message is done transmitting. The following table shows which messages use a connection and whether or not you can cache the connection: Using this...
Allocating Communication Connections Determining Total The Logix5550 controller supports 250 connections. Use the following table to tally connection requirements for a Logix5550 controller. Connection Requirements Connection Type Module Connections Total Quantity per Module Connections local I/O module remote I/O module (direct connection only) 1756-MO2AE servo module local 1756-CNB module remote 1756-CNB module through local...
Page 184
A-10 Allocating Communication Connections 1756-6.5.3 - December 1999...
Appendix Creating Produced and Consumed Tags What This Appendix Contains This appendix explains produced and consumed tags and describes how to create them. For information about See page Produced Tags Producing a tag from a Logix5550 Controller to a ControlNet PLC-5 Processor Consumed Tags Consuming a tag from a ControlNet PLC-5 Processor to a Logix5550 Controller...
Page 186
Creating Produced and Consumed Tags To specify a produced tag. In this field Enter or select Name Type a name for the tag. Description Type a description for the tag (optional). Tag Type Select one of these: Base for a normal tag Alias for a tag that references another tag or part of another tag Consumed...
Creating Produced and Consumed Tags Consumed Tags A consumed tag represents data that is produced (broadcast) by one controller and received and stored by the consuming controller. 1. In the Tag Editor, select the tag. 2. Click the right mouse button and select Tag Properties To specify a consumed tag: In this field...
Page 188
Creating Produced and Consumed Tags A produced or consumed tag cannot be larger than 500 bytes. The tag must also fit within the bandwidth of the network. See the Logix5550 Controllers User Manual, publication 1756-6.5.12 for more information. You can only create a consumed tag when programming offline. To consume data from a remote controller, use RSNetWorx for ControlNet software to schedule the connection over the ControlNet network.
Creating Produced and Consumed Tags Producing a tag from a To produce a tag that a ControlNet PLC-5 processor can consume, follow the steps below. Refer to chapter 6 for an example. Logix5550 Controller to a ControlNet PLC-5 Processor 1. Open the RSLogix5000 project. 2.
Page 190
Creating Produced and Consumed Tags 1756-6.5.3 - December 1999...
Appendix Electronic Keying ATTENTION: Be extremely cautious when you disable electronic keying. If used incorrectly, this option can lead to personal injury or death, property damage, or economic loss. Specifying Electronic Keying You specify electronic keying to ensure that a module being inserted or configured is of the proper type and firmware revision.
Page 192
Electronic Keying 1756-6.5.3 - December 1999...
“1” indicates a connection to the CNB module at ControlNet node 1. “1” indicates a connection to the backplane of the ControlLogix chassis. “0” indicates a connection to the module at slot 0 (the Logix5550 controller). Change the first “1” to “6” to download via the CNB module at node6.
Page 194
Setting Paths for Downloads in RSLogix5000, Version 2.10 2. Select the Communications tab and enter the following configuration to download through the 1756-CNB module at node 1: In this field Select Driver AB_KTC-1 Path 2, 1, 1, 0 This is the default name for the KTCx driver configured in chapter 2 using RSLinx.
Page 195
1756-CNB modules to for messaging A-8 expand the network 11-17 for produced and consumed tags A-6 11-18 create the example application 11-2 how ControlLogix uses connections 11-11 download the program 11-10 rack optimized A-3 11-11 consumed tags 1-4 edit the controller tags 11-9...
Page 196
Logix5550 to Logix5550 scheduled mapping PLC-5C file to Logix5550 tag communications 4-1 4-20 create consumer tags 4-12 4-13 messaging create producer tags 4-3 connections A-8 create the producer application 4-2 MultiHop 7-3 create the producer program 4-5 download to the consumer 4-15 paths for downloads D-2 download to the producer 4-5 PLC-5 processor installation 2-9...
Page 197
set up the example application 9-1 add remote I/O modules to test the example application 9-6 configuration 10-7 10-11 control of 1-6 produced tags 1-4 create the example application 10-1 creating B-1 10-13 optimizing A-7 create the ladder program 10-12 producer/consumer model 1-4 download the program 10-12 10-13...
Page 199
What is unclear? Sequence What is not in the right Other Comments Use back for more Your Name Location/Phone Return to: Marketing Communications, Allen-Bradley., 1 Allen-Bradley Drive, Mayfield Hts., OH 44124-6118Phone:(440) 646-3176 FAX:(440) 646-4320 Publication 1756-6.5.3- December 1999 PN 955127-21...
Page 200
PLEASE FASTEN HERE (DO NOT Other PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY FIRST-CLASS MAIL PERMIT NO. 18235 POSTAGE WILL BE PAID BY THE 1 ALLEN-BRADLEY DR MAYFIELD HEIGHTS OH 44124-9705...
Need help?
Do you have a question about the ControlLogix and is the answer not in the manual?
Questions and answers