Home

ControlNet Network Configuration User Manual, CNET-UM001D-EN-P

1. Item Description 1 Node 2 Tap with 1 m 3 28 ft dropline 3 Coaxial repeater 22 Rockwell Automation Publication CNET UM001D EN P June 2011 TIP ControlNet Overview Chapter 1 Coax repeaters are typically used in trunkline and star topologies See the ControlNet Coax Media Planning and Installation Guide publication CNET INOO2 for more specific information on coax topologies you can create With fiber media you can configure your network in trunkline star and ring topologies Only the 1786 RPFRL and 1786 RPFRXL repeaters support a ring topology For more information consult the ControlNet Fiber Media Planning and Installation Guide publication CNET INO01 Figure 7 Example ControlNet Network Ring Topology fe amp fe a m 1 A Tae Item Description Node Fiber cables Coaxial cable Tap with 1 m 3 28 ft dropline on A j N ControlNet Repeater Adapter and Fiber Ring Module Rockwell Automation Publication CNET UM001D EN P June 2011 23 Chapter 1 24 ControlNet Overview Number of Nodes Each ControlNet network supports up to 99 nodes Logix5000 controllers support multiple ControlNet networks providing the flexibility to add nodes to a ControlNet network or boost perform
2. Exact Match Exact Match keying requires all keying attributes that is Vendor Product Type Product Code catalog number Major Revision and Minor Revision of the physical module and the module created in the software to match precisely in order to establish communication If any attribute does not match precisely I O communication is not permitted with the module or with modules connected through it as in the case of a communication module 38 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 Use Exact Match keying when you need the system to verify that the module revisions in use are exactly as specified in the project such as for use in highly regulated industries Exact Match keying is also necessary to enable Automatic Firmware Update for the module via the Firmware Supervisor feature from a Logix5000 controller EXAMPLE In the following scenario Exact Match keying prevents 1 0 communication The module configuration is for a 1756 IB16D module with module revision 3 1 The physical module is a 1756 IB16D module with module revision 3 2 In this case communication is prevented because the Minor Revision of the module does not match precisely Module Configuration Vendor Allen Bradley fm SIE TF BCD Product Type Digital Input a a e Module Catalog Number 1756 IB16D a Wea Das a Major Revision 3 Minor Revision 1 I7 Open Module Prope
3. Find Add Favorite By Category By Vendor Favorites OK Cancel Help IMPORTANT This procedure shows the New Module dialog box for a 1756 CN2R B However various dialogs appear during configuration depending on the ControlNet module you select For help configuring a module refer to the online help in RSLogix 5000 software Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 This table lists the ControlNet communication modules available locally in the local chassis computer or controller with each Logix5000 controller Table 6 ControlNet Communication Modules Available Locally Logix5000 Controller Local ControlNet Communication Module 1768 CompactLogix 1768 CNB 1768 CNBR ControlLogix 1756 CN2 1756 CN2R 1756 CNB 1756 CNBR SoftLogix 1784 PCIC 1784 PCICS 3 Complete the fields on the New Module dialog box and then click OK Field Action Name Type a name for the local ControlNet module Node Enter the module s node number on the network Description Type a description of the local ControlNet module Slot Enter the module s slot number in the chassis Revision Choose a major and minor revision of RSLogix 5000 software Electronic Keying Choose a keying option as described in Electronic Keying on page 37 Open Module Properties na the box checked to configure connection properties in the next step New Module
4. Keeper signatures are used to identify the network configuration and ensure that all keeper capable devices are synchronized on the network This dialog provides insights into the keeper mismatch messages that appear in the Messages view Keeper Capable Node Valid Keeper Keeper Signatu Offline File Ox6a50693a 01 Ox6a50693a 03 NO Ox6a50693a D4 NO Ox6a50693a 05 NO Ox6a50693a 06 NO Ox6a50693a OF NO Ox6a50693a 10 NO Ox6a50693a 11 NO 0x6a50693a Node 16 is not 16 NO NO Ox86c69e96 lt a Refresh Update Keeper Help a valid keeper 20 Rockwell Automation Publication CNET UM001D EN P June 2011 ControlNet Network Capacity and Topology ControlNet Overview Chapter 1 Default Parameters When a ControlNet network is first established it relies on a default set of parameters capable of sending only unscheduled data Default parameters in all ControlNet devices include the following e Network Update Time NUT 100 ms e Scheduled Maximum Node Address SMAX 1 The SMAX is the highest network address of a node that can use the scheduled service e Unscheduled Maximum Node Address UMAX 99 The UMAX is the highest network address of a node that can communicate on a ControlNet network The UMAX must be set equal to or higher than the SMAX e Assumed maximum cable lengths and maximum number of repeaters With this default ControlNet network you can have unscheduled communication between the various de
5. Offline fl F RUN No Forces b r No Edits Ar Pa Tasks 3 Motion Groups Trends G Data Types amp 140 Configuration D H 3 g 1 1756 CNB7D Local_comm_module 4 i 1 0 1756 CNB D Remote_comm_module 5 p 8 1 1756 L63 Remote_Controller Item Description Local controller and communication module 2 Remote controller and communication modules 3 Local communication module for the local controller 4 Remote communication module for the remote controller 5 Remote controller For more information on how to add ControlNet modules and remote devices to the local controller s I O configuration see Chapter 4 Rockwell Automation Publication CNET UM001D EN P June 2011 87 Chapter6 Messaging Enter a Message Use relay ladder logic to enter a MSG instruction Click Jj to configure the MSG instruction as shown in the example below EXAMPLE Enter a MSG instruction as shown below ATTENTION 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 user_bit count_messages EN MSG J fa Type CIP Generic END Message Control count_messages E lt DND ER gt TIP We recommend an XIO of the MSG control block tag en such as the count_messages EN portion of this rung as an in series precondition for all message instructions Do not manipulate the contro
6. 1756 EN2T 7756 cnaA Ey ki 1756 CN2 Item Description 1 Local controller in any of these combinations e 1756 ControlLogix controller with a 1756 CN2 or 1756 CN2R communication module in the chassis e 1756 ControlLogix controller with a 1756 CNB or 1756 CNBR communication module in the chassis e 1768 L43 CompactLogix controller with a 1768 CNB or 1768 CNBR communication module in the chassis e 1769 L32C or 1769 L35CR CompactLogix controller e 1789 SoftLogix controller with a 1784 PCICS communication card e PowerFlex 700S with DriveLogix controller and a 1788 CNx ControlNet communication card 2 HMI terminal Make sure of the following The ControlNet communication modules are connected to a scheduled ControlNet network e All wiring and cabling are properly connected 92 Rockwell Automation Publication CNET UM001D EN P June 2011 Communicate with PanelView Terminals Chapter 7 Determine Connections to How A ia S a a between a ia eral or ea PanelView Terminals terminal and a Logix5000 controller over a ControlNet network depends on how you want to use controller connections Communication Type PanelView Standard PanelView Plus Scheduled always connected Supported Supported in revision 3 2 and later Unscheduled connected No
7. June 2011 Use RSLogix 5000 Software Chapter 3 Configure a ControlNet Module This chapter explains how to configure a ControlNet communication module to operate on a ControlNet network Topic Page Use RSLogix 5000 Software 29 Use RSNetWorx for ControlNet Software 44 IMPORTANT The example configuration process shown in this chapter uses a 1756 CN2R B ControlLogix ControlNet bridge module in a ControlLogix controller project However the overall configuration process described in Configure the 1 0 Configuration Tree in Your Project generally applies to any of the ControlNet communication modules covered in this manual Use RSLogix 5000 software to configure the I O tree in your project Configure the 1 0 Configuration Tree in Your Project When you use RSLogix 5000 software to configure a ControlNet communication module you must perform these tasks 1 Add and Configure a Local ControlNet Module 2 Add and Configure a Remote ControlNet Module IMPORTANT There are some differences between configuring a local ControlNet communication module and configuring a remote ControlNet communication module Those differences are covered later in this chapter 3 Download the Project to the Logix5000 Controller Rockwell Automation Publication CNET UM001D EN P June 2011 29 Chapter 3 Configure a ControlNet Module 30 Add and Configure a Local ControlNet Module After you have started RSLogix 5000
8. Type 1756 CN2R 6 1756 ControlNet Bridge Vendor Allen Bradley Name f Description Revision 20 v 1 E Electronic Keying Compatible Keying Open Module Properties Cancel Help Rockwell Automation Publication CNET UM001D EN P June 2011 31 Chapter 3 32 Configure a ControlNet Module 4 On the Module Properties dialog box configure the connection properties and then click Apply Connection Property Inhibit Module Action If the module does not need to communicate with the controller check the checkbox or lf the module needs to communicate with the controller leave the checkbox cleared IMPORTANT When you test this portion of the system leave the checkbox cleared Major Fault On Controller If Connection Fails While In Run Mode If you want the controller to produce a major fault if the connection to the local communication module fails in Run mode check the checkbox or If you want the controller to continue operating if the connection to the local communication module fails in Run mode leave the checkbox cleared Use ladder logic to monitor the connection E Module Properties Local 2 1756 CN2R B 20 1 General Connection RSNetWork Module Info Backplane Requested Packet Interval RPI ms C Inhibit Module C Major Fault On Controller If Connection Fails While in Run Mode Module Fault Status Offline Rockwell Automation P
9. Configure a ControlNet Module 54 6 From the Save Configuration dialog box click Optimize and rewrite the schedule for all connections Save Configuration mS Either of the following choices will save the updated schedule x to the file and to the online network if you are online o Save Type Cancel Optimize and re write schedule for all connections c Help 7 Click OK IMPORTANT Itis better to optimize connections However in some cases involving multiple controllers the Merge changes option is available This option lets controllers whose connections have not changed to continue uninterrupted operation When you merge changes into the existing schedule those controllers whose connections have not changed remain in Run mode rather than changing to Program mode 8 In RSLogix 5000 software save the online project Rockwell Automation Publication CNET UM001D EN P June 2011 Chapter 4 Control 1 0 This chapter explains how a controller controls distributed I O over a ControlNet network Topic Page Set Up the Hardware 56 Requested Packet Interval RPI 56 Communication Format 57 Add a Remote Adapter 63 Add Distributed 1 0 63 Access Distributed 1 0 65 Validate Connections 68 To control distributed I O over a ControlNet network you must do the following e Add local and remote ControlNet communication modules to your RSLogix 5000 project When you create a new R
10. on page 53 for more information To schedule a network online follow this procedure in RSNetWorx for ControlNet software 1 From the File menu choose New ControlNet RSNetWorx for ControlNet Ete Edit view Network Device Diagnostics T amp Open Ctrl 0 2 From the New File dialog box select a ControlNet configuration for the new file and click OK New File Single Pas ontinuous Browse Rockwell Automation Publication CNET UM001D EN P June 2011 49 Chapter 3 50 Configure a ControlNet Module 4 From the Browse for Network dialog box expand the tree to find and select a communication path to the ControlNet network and click OK Browse for Network Select a communications path to the desired network I Autobrowse Workstation USMAYCCIANCI m as Linx Gateways Ethernet a AB_ETHIP 1 Ethernet 4g AB_ETHIP 2 Ethernet E AB_VBP 1 1789 417 A Virtual Chassis USB 16 1784 U2CN USB Interface 1784 U2CN wee This example uses a previously configured communication path to the controller Here the computer is connected to the ControlNet network via a 1784 PCIC card The driver was previously configured via RSLinx software as described in Connect a Computer to the ControlNet Network on page 25 5 From the Network menu choose Single Pass Browse ControlNet RSNetWorx for ControlNet File Edit View Network Device Diagnostics Tools Help Continuous
11. s I O Configuration 04 87 Enter a Message ssies Ba de Viet taana riage EE EA REA Aa 88 Configure a Message nsttuctionin 05 56 ivecc akeisheas verter 88 Stagger the Messapes rererere s aia tun ien ea 90 Chapter 7 Set Up th Hardware jai iu dia Gee ian ee eae lee Sts ae 92 Determine Connections to PanelView Terminals 5 93 Add a PanelView Dermitial ocdsisek oe oi eu Ave odin e bees aes 94 Organize Controller Data for a PanelView Terminal 96 6 Rockwell Automation Publication CNET UM001D EN P June 2011 Preface This manual describes how you can use ControlNet communication modules with your Logix5000 controller Use this manual if you program applications that use a ControlNet network with one of these Logix5000 controllers e CompactLogix controller e ControlLogix controller e PowerFlex 700S with DriveLogix controller e SoftLogix5800 controller Also be familiar with the following e Networking concepts e RSLogix 5000 software e RSLinx Classic software e RSNetWorx for ControlNet software iti These documents contain additional information concerning related products tional nesources 8 P from Rockwell Automation Resource Description ControlNet Modules Installation Instructions Describes how to install 1756 CN2 1756 CN2R publication CNET IN005 1756 CN2RXT 1756 CNB 1756 CNBR 1768 CNB and 1768 CNBR ControlNet modules Industrial Automation Wiring and Gro
12. see the Logix5000 Controllers General Instructions Reference Manual publication 1756 RM003 The individual system user manuals for Logix5000 controllers also provide MSG examples unique to specific controller platforms Rockwell Automation Publication CNET UM001D EN P June 2011 85 Chapter6 Messaging Determine Connections for Messages Enter Message Logic Messages transfer data to other modules such as other controllers I O modules or operator interfaces Each message uses one connection regardless of how many modules are in the message path To conserve connections you can configure one message to read from or write to multiple modules Also you can configure multiple messages for the same path and use only one connection if only one message is active at a time however this requires that you write your ladder logic correctly to make sure that only one message is active at any time These connected messages can leave the connection open cache or close the connection when the message has finished transmitting Table 22 Message Connections and Communication Methods Message Type Communication Method Connection Required CIP data table read or write CIP Yes CIP generic CIP Optional Block transfer read or write Not applicable Yes 1 You can connect CIP generic messages but for most applications we recommend you leave CIP generic messages unconnected Guidelines for Caching Message Connections Follo
13. 74 127 Connections Used by a Produced Tag Number of consumers 1 Connections Used by a Produced Tag Number of consumers Rockwell Automation Publication CNET UM001D EN P June 2011 Connections Used by a Consumed Tag Connections Used by a Consumed Tag Produce and Consume Tags interlock controllers Chapter 5 Org anize Tags for Produced Follow these guidelines as you organize your tags for produced or consumed data or Consumed Data shared data Table 19 Guidelines for Produced or Consumed Data Tags Function Create the tags at the controller scope Guidelines You can produce and consume only controller scoped tags Produce and consume specific tags You cannot produce or consume these types Alias Axis type BOOL Consumed 0 INT e Message Use one of these data types e DINT REAL Array of DINTs or REALs User defined To share other data types create a user defined data type that contains the required data Use the same data type for the produced tag and corresponding consumed tag or tags Limit the size of the tag to 480 bytes If you must transfer more than 480 bytes create logic to transfer the data in smaller packets or create multiple produce consume tags To share tags with a PLC 5C controller use a user defined data type To This Then Produce Integers BOOLs or Create a user defined data type that contains an array
14. Autobrowse EJ workstation USMAYCCIANCI ge Linx Gateways Ethernet gs AB_ETHIP 1 Ethernet Upload S f 10 88 92 10 1756 EN2T A 1756 EN2T A S 6 Backplane 1756 A10 A Download f 00 1756 CN2R 1756 CN2R B 01 1756 CNBR D 1751 Update Firmware e f A 573 Close 04 1756 EN2T A 1756 EN2T A as AB_ETHIP 2 Ethernet Help ge AB_ETHIP 3 Ethernet E E AB_VBP 1 1789 A17 4 Virtual Chassis Path AB_ETHIP 1410 88 92 10 Backplane 3 Set Project Path Path in Project lt none gt 4 When the Download dialog box appears click Download Electronic Keying The electronic keying feature automatically compares the expected module as shown in the RSLogix 5000 I O Configuration tree to the physical module before I O communication begins You can use electronic keying to help prevent communication to a module that does not match the type and revision expected For each module in the I O Configuration tree the user selected keying option determines if and how an electronic keying check is performed Typically three keying option are available e Exact Match e Compatible Keying e Disable Keying You must carefully consider the benefits and implications of each keying option when selecting between them For some specific module types fewer options are available Rockwell Automation Publication CNET UM001D EN P June 2011 37 Chapter3 Configure a ControlNet Module Electronic keying is based on a set
15. Browse 3 I Edits Eng as Online 6 Check Edits Enabled When you enable edits RSNetWorx for ControlNet software reads data in the ControlNet modules and builds a schedule for the network Network schedule xc RSNetWorx for ControlNet File Edit Yiew Network Device Diagnostics Tools Help I Edits Enabled Network Update Time ms 5 00 Unscheduled Bytes Per Sec 544057 Current Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 7 To change the network properties from default settings to those that best fit your network from the Network menu choose Properties Network schedule xc RSNetWorx for ControlNet File Edit Yiew Network Device Diagnostics Tools Help a x Network Usage J Edits Eng wa Online Network Up Enable Edits Unschedule Upload from Network Download to Network Download Minimum to Network Hardware Keeper Status Scanner Signature Status E Controle O Ac Drive gt No Drive m 8 On the Network Parameters tab configure the network parameters as described in the table below Parameter Network Update Time Description The smallest user configurable repetitive time cycle in milliseconds at which data can be sent on a ControlNet link Max Scheduled Address The node with the highest network address that can use scheduled time on a ControlNet link 1 0 data is transferred d
16. Distance Fibe Glass Fiber Cable 9904 RPA Repeater Adapter 9904 APFS Short Distance Fiber b 9904 RPFM Medium Distance Fibe H A A 3904 Long Distence Fiber Module Default Media Configuration of 1000 m 1786 APT Coax Repeater Herne REE ND 3280 84 ft of RG6 Coaxial Cable 9904 RPTCoax Repeater 9904 RPTD Coax Repeater 24D RGS Coax Cable 1786 RPFRL Long Fiber Ring Rep 1786 RPFRXL Extra Long Fiber Ri lt gt Click OK On the Save Configuration dialog box click Optimize and rewrite the schedule for all connections Save Configuration ial EJ Either of the following choices will save the updated schedule to the file and to the online network if you are online Save Type Cancel Optimize and re write schedule for all connections ch i Help Click OK Return to your RSLogix 5000 software project a Save your project to update the network file in your RSLogix 5000 project b Download your project as described in Download the Project to the Logix5000 Controller on page 36 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 Schedule the Network Online Prior to scheduling a network online make sure 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 Reschedule a ControlNet Network that has Previously been Scheduled
17. been configured by RSNetWorx for ControlNet software and that configuration is the same as that of the first keeper that became active after the network was formed or reconfigured by RSNetWorx software Rockwell Automation Publication CNET UM001D EN P June 2011 19 Chapter 1 ControlNet Overview If the active keeper is taken off the network a valid back up keeper can take over for it and continue to act as keeper As long as at least one valid multi keeper device is present on the network new scheduled connections can be established To review the valid keeper devices on your network follow this procedure in RSNetWorx for ControlNet software 1 From the Network menu choose Keeper Status Network schedule xc RSNetWorx for ControlNet Bile Edit View Network Device Diagnostics Tools Help S snoer Edits Ene aa Online Network Up Enable Edits Unschedule Upload From Network Download to Network Download Minimum to Network Hardware E Scanner Signature Status 2 Review the keeper devices on the Keeper Status dialog box Network Usage On a typical network the following must be true e There must be only one active valid keeper e All other keepers must be valid If a keeper is not valid it cannot perform any scheduled communication However all unscheduled communication occurs as expected The keeper signature shown in hex must be the same for all nodes Keeper Status
18. code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect support programs For more information contact your local distributor or Rockwell Automation representative or visit http www rockwellautomation com support Installation Assistance If you experience a problem within the first 24 hours of installation review the information that is contained in this manual You can contact Customer Support for initial help in getting your product up and running United States or Canada 1 440 646 3434 Outside United States or Use the Worldwide Locator at http www rockwellautomation com support americas phone_en html or contact Canada your local Rockwell Automation representative New Product Satisfaction Return Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning and needs to be returned follow these procedures United States Contact your distributor You must provide a Customer Support case number call the phone number above to obtain one to your distributor to complete the return process Outside United States Please contact your local Rockwell Automation representative for the return procedure Document
19. configure and schedule a ControlNet network we recommend that you either connect to an EtherNet IP network and bridge to a ControlNet network or use a 1784 U2CN cable to connect directly to a ControlNet network 2 Typically this is a point to point connection between a Logix5000 controller and another device such as a PanelView Plus operator terminal In Figure 2 a workstation configures a drive on the DeviceNet network The workstation bridges from the ControlNet network to the DeviceNet network to reach the drive The bridge is a ControLogix chassis with ControlNet and DeviceNet modules Rockwell Automation Publication CNET UM001D EN P June 2011 11 Chapter 1 ControlNet Overview Figure 2 Drive Configuration on a DeviceNet Network 6 5 Item Description Item Description 1 Workstation 4 Drive 2 PanelView terminal 5 DeviceNet network 3 Bridge 6 ControlNet network IMPORTANT The performance of a CompactLogix controller on a ControlNet network degrades significantly if you use the controller as a bridge Target bridging over a CompactLogix controller on a ControlNet network toward applications that are not real time dependent such as RSLogix 5000 software program downloads In the example shown above you can transfer messages from the DeviceNet network through the Logix5000 controller to an RSView32 operator interface With a CompactLogix controller as a bridge you can map t
20. controller When you place the module in the I O configuration list of a ControlLogix controller and configure a second ControlLogix chassis with a remote 1756 CNB or 1756 CN2 module on the same ControlNet network you can perform remote control operations on the I O or to a second controller in the second chassis In this case the ControlLogix controller and the 1756 CN2 module in the local chassis together act as a scanner while the 1756 CN2 module in the remote chassis with the I O plays the role of an adapter Understand the Network Keeper Every ControlNet network requires at least one module to store programmed parameters for the network and configures the network with those parameters when the module is started This module is called a keeper because it keeps the network configuration RSNetWorx for ControlNet software configures the keeper To avoid a single point of failure a ControlNet network supports multiple redundant keepers These ControlNet communication modules are keeper capable devices e 1756 CN2 and 1756 CN2R modules e 1756 CNB and 1756 CNBR modules e 1768 CNB and 1768 CNBR modules e 1769 L32C and 1769 L35CR controllers e 1784 PCICS and 1784 PKTCS cards e 1788 CNx cards e PLC 5C module On a multi keeper network any keeper capable module can keep the network at any legal node address 01 99 The multi keeper capable node with the lowest node address becomes the active keeper provided it is valid It has
21. for DH DH 485 devices 1784 KT C x for ControlNet devices DF1 Polling Master Driver 1784 PCC for ControlNet devices 1784 PCIC S for ControlNet devices 1747 PIC 2 AIC Driver Ls 3 Click Add New The Add New RSLinx Driver dialog box appears The driver name defaults to AB_xxx gt Status Running Configure Running Startup Add New RSLinx Classic Driver Choose a name for the new driver 0K 15 characters maximum ox Cancel AB_PCIC A pe 4 Type the name of the new ControlNet driver 5 Click OK The Configure Device dialog box appears The appearance of this screen varies depending on the type of card used Configure 1784 PCIC Device Name AB_PCIC Serial Number hex 002b8e62 1784 PCIC 002b8e62 1784 PCICS PCICS Slot5 Network Address dec 1 Cancel Help 26 Rockwell Automation Publication CNET UM001D EN P June 2011 Connect a Computer to the ControlNet Network Chapter 2 6 If your computer contains multiple cards from the Serial Number hex field choose the correct card 7 In the Network Address dec box type the correct network address 8 Click OK The driver is now available and you can choose the ControlNet port from Who Active in RSLogix 5000 software Rockwell Automation Publication CNET UMO001D EN P June 2011 27 Chapter 2 Notes 28 Connect a Computer to the ControlNet Network Rockwell Automation Publication CNET UM001D EN P
22. in this example eS i A 1 1 1756 CNB D Local_CNB f 2 0 1756 CNB D Remote_CNB 1 1756 L63 Producing_controller Local ControlNet module in consuming controller s chassis Remote ControlNet module Producing controller 3 Make sure the communication format for the remote ControlNet module is None Rockwell Automation Publication CNET UM001D EN P June 2011 79 Chapter 5 Tag Name Field Produce and Consume Tags interlock controllers 4 Within the Controller Organizer of RSLogix 5000 software right click Controller Tags and choose Edit Tags ft RSLogix 5000 ControlNet 1769 L35CR 19 11 File Edit View Search Logic Communications Tools Windo ae a pe oco D E RUN Offline NoFaces EOK F BAT No Edits ar Wi Organizer Controller ControlNet New Tag Ctrl w lue 40 43 04 U0 Sj Tasks 5 8 Maintask Monitor Tags i Verify 433 5 From the Controller Tags dialog box type the name of the new tag in an available Tag Name field ft RSLogix 5000 ControlNet 1769 L35CR 19 11 Co File Edit View Search Logic Communications Tools Wind CORA amp it 2Bo D m RUN F oK BAT m 1 0 D Scope fa ControlNet v Show Al Tags Name zale Alias For Base Tag F Consumed tag Bo o n 6 Right click the new tag name and choose Edit Properties fe RSLogix 5000 ControlNet 1769 L3
23. local and remote ControlNet communication modules For more information refer to Add and Configure a Local ControlNet Module on page 30 and Add and Configure a Remote ControlNet Module on page 33 2 In RSLogix 5000 software right click your remote ControlNet communication module and choose New Module S 10 Configuration 5 1 21756 CNB B Local CNB 3 1794 ACNR15 C Remoje f 5 1756 0816 Local_output MAUMAU 5 6 1756 1B161 Local_input_mi Cut Ctra dule 3 From the Module Properties dialog box configure the distributed I O module IMPORTANT This procedure shows the Module Properties dialog box for a 1794 IB16XOB16P A digital combo module However various dialogs appear during configuration depending on the type of distributed 1 0 For help configuring a module refer to the online help in RSLogix 5000 software Module Properties Remote_FLEX_CNET_adapter 0 1794 IB16XOB16P A 1 1 Type 1794 1B16X0B16P 4 16 Input 16 Output 24 DC Sink Protected Source Vendor Allen Bradley Parent Remote_FLEX_CNET_adapter Name FLEX_combo_module Slot fi 3 Description B Comm Format Rack Optimization X Revision fl Electronic Keying Compatible Module Cancel lt Back l Next gt L Enis Help To Then Use the module s default configuration a Type the module name communication format and RPI b Click Finish Customize the configuration a Type the module nam
24. must use a rack optimized connection for the remote ControlNet communication module the owner controller still makes direct connections with the three I O modules configured as such Each remote ControlNet communication module is limited to five rack optimized connections Module Properties Remote_ENB 1756 IB16 2 1 Type 1756 1B16 16 Point 10 31 2 DC Input Vendor Allen Bradley Parent Remote_ENB Name Slot fi 4 Description fea Rack optimized Connection gp Comm Format Revision Rack Optimization B fi 4 Electronic Keying Compatible Modu Rockwell Automation Publication CNET UM001D EN P June 2011 Control O Chapter 4 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 ControlNet Adapter with ControlNet Adapter with ControlNet Adapter with Three Digital I O Modules Two Analog 1 0 Modules Two Digital 1 0 Modules The table below calculates the connections in this example Table 11 Connection Calculations System Connections Amount Controller to local ControlNet communication module 0 Controller to ControlNet adapter 0 Direct connection for digital 1 0 modules 5 digital Direct connection for analog I O modules 2 analog Total conn
25. of your project Scheduling off line can be used to predict performance and measure bandwidth TIP To learn more about using RSLogix 5000 and RSNetWorx software offline to predict performance refer to answer ID 54793 on the Rockwell Automation Knowledgebase at http www rockwellautomation com knowledgebase Before scheduling a network offline make sure of the following e Your RSLogix 5000 software project uses one controller and one network We recommend that you use only one 1756 CN2 1756 CNB or 1768 CNB module in the local chassis when scheduling the network offline e Your RSLogix 5000 software project is complete but has not been downloaded to the controller If your network has already been scheduled and you made a change to it you must reschedule it For more information refer to Reschedule a ControlNet Network that has Previously been Scheduled on page 53 To schedule a network offline perform this procedure 1 In your RSLogix 5000 software project right click your local ControlNet module and choose Properties amp J 1 0 Configuration amp 1756 Backplane 1756 47 fa 0 1756 L63 CNET_messaging EJ J 1 1756 CNB D LocalCNB 2 1756 CN2R B ControlNet_Modhles See ControlNet 8 New Module 1 1756 CN2R B ControlNe F S 21756 CN2R B Remote N gt amp 1756 Backplane 1756 Copy Ctrl C S 31756 CN2R B Remote_ aie 1756 Backplane 1756 T EH IE Cross Refere
26. software to schedule the network in order to activate the configured I O devices in your application You must also reschedule the network if a change is made to an already scheduled network Schedule a ControlNet Network for the First Time RSNetWorx for ControlNet software stores information in keeper devices These ControlNet communication modules are keeper cable devices e 1756 CN2 and 1756 CN2R modules e 1756 CNB and 1756 CNBR modules e 1768 CNB and 1768 CNBR module e 1769 L32C and 1769 L35CR controllers e 1784 PCICS and 1784 PKTCS cards If you configure a keeper on one network and then use it on another network the conflicting information can make it difficult to use RSNetWorx for ControlNet software to schedule the new network In extreme cases it may be difficult to go online e For more information on the network keeper see the section Understand the Network Keeper on page 19 e For more information on how to reset valid keepers to an unconfigured state to resolve mismatches refer to the RSNetWorx for ControlNet software online help e For more information on how to clear the memory or keeper information in a ControlNet communication module refer to the Knowledgebase at http www rockwellautomation com support 44 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 Schedule the Network Offline Scheduling a project offline is most useful in the design phase
27. tab Produced Tag Connection Connection Status Max Consumers v C Send Data State Change Event To Consumer s Rockwell Automation Publication CNET UM001D EN P June 2011 Produce and Consume Tags interlock controllers Chapter 5 8 In the Maximum Consumers field type a number of consumers Ifyou are unsure of the number of consumers use a number higher than the actual number of consumers Unused connections are deducted from the number of available controller connections 9 Click OK IMPORTANT When your Logix5000 controller produces a tag any device that interfaces with a ControlNet network can consume the tag However when a non Logix controller such as a personal computer using a 1784 PKTCS card consumes the tag produced by a Logix controller you must perform additional tasks in RSNetWorx for ControlNet software Consume a Tag Logix5000 controllers can consume only controller scoped user created tags from another controller s tag structure The Logix5000 controllers cannot consume I O tags or tags aliased to I O tags IMPORTANT You can create consumed tags only when your RSLogix 5000 project is offline To consume a tag perform this procedure 1 Open the RSLogix 5000 project that contains the controller that you want to consume the produced tag 2 Make sure the controller producing the tag to be consumed is in the consuming controller s I O configuration as shown
28. that can use unscheduled time on a ControlNet link Messaging data is transferred during unscheduled time Nodes set at addresses higher than the maximum unscheduled node do not communicate on the network For example they will not display in RSLinx software Media Redundancy Designates if the network uses media redundancy Network Name Network schedule User defined name of the network Network Parameters Media Configuration General Current Pending Network Update Time ms Bo 5o Max Scheduled Address a foo Max Unscheduled Address fos re Media Redundancy nl 4 Only x Network Name f _defaul Cancel Help Rockwell Automation Publication CNET UMO001D EN P June 2011 41 Chapter 3 48 Configure a ControlNet Module 11 12 13 14 15 16 Click the Media Configuration tab Generally you can use the default media configuration Adjust the configuration if your network is longer or uses repeaters If the media configuration does not accurately represent the maximum propagation delay between any two nodes your network may experience errors Network schedule Network Parameters Media Configuration General Available Media Media Configuration Description Quantity Description 1000 meters RG6 Coax Cable el TE 1786 Short Distance Fiber b 1786 RPFM Medium Distance Fibe 1786 Long Distance Fiber Module 1797 RPA Repeater Adapter IS ve 1797 APFM Medium
29. the possible bridges between communication networks Note that you can bridge from a ControlNet network to an Ethernet network and from an Ethernet network to a ControlNet via a SoftLogix virtual chassis However the products and methods you must use to do so are more detailed than can be effectively described in the following tables For more information on how to bridge from one network to another via a SoftLogix virtual chassis see the SoftLogix5800 System User Manual publication 1789 UM002 Table 2 Bridges from a ControlNet Network Destination Modules for a 1768 CompactLogix Modules for a 1769 CompactLogix Modules for a ControlLogix Network System System Chassis DeviceNet e 1768 L43 or 1768 L45 controller e 1769 L32C or 1769 L35CR controller e 1756 CN2 module e 1768 CNB R module e 1769 SDN scanner or 1788 CN2DN e 1756 CN2R module e 1769 SDN scanner module e 1756 CNB module e 1756 CNBR module e 1756 DNB module EtherNet IP e 1768 L43 or 1768 L45 controller Not applicable e 1756 CN2 module e 1768 CNB R module e 1756 CN2R module e 1768 ENBT module e 1756 CNB module e 1756 CNBR module e 1756 ENBT module e 1756 EN2T module e 1756 EN2TR module e 1756 EN3TR module 1 Can serve as a dedicated standalone bridge from a ControlNet network to a DeviceNet network Rockwell Automation Publication CNET UM001D EN P June 2011 13 Chapter 1 ControlNet Overview Table 3 Bridges from an EtherNet IP Network Destin
30. to Peer Messaging Example Data 3 Acr 1 Item Description 1 Remote chassis with any of these configurations e PLCs SLC or Logix5000 controllers on a ControlNet or other network e 0 modules such as ControlLogix analog module configuration data on a ControlNet or other network e 1771 block transfer modules 2 Programming terminal 3 Local chassis with any of these combinations module in the chass module in the chass module in the chass 1769 PowerFlex 700S wit communication card 1756 ControlLogix controlle is 1756 ControlLogix controlle S 1768 L43 CompactLogix con S L32C or 1769 L35CR C with a 1756 CN2 or 1756 CN2R communication with a 1756 CNB or 1756 CNBR communication troller with a 1768 CNB or 1768 CNBR communication ompactLogix controller 1789 SoftLogix controller w ith a 1784 PCICS communication card h DriveLogix controller and a 1788 CNx ControlNet Non Logix5000 controller or other device connected to ControlNet via a ControlNet scanner card IMPORTANT The 1769 L32C and 1769 L35CR controllers can produce and consume tags over a ControlNet network to other Logix5000 controllers Howe
31. 1 FLEX_adapter 1 C Config rack optimized connection FLEX_adapter 1 C DelayTime_0 FLEX_adapter 1 1 3 Example 3 Remote 1794 0B16D FLEX_adapter 2 C Output_module in slot 2 FLEX_adapter 2 C SSData rack optimized connection FLEX_adapter 2 0 FLEX_adapter 2 0 1 The tags listed are not a complete list of the tags created for each module type For a full list of the tags created for each module see the Tag Monitor tool in RSLogix 5000 software Rockwell Automation Publication CNET UM001D EN P June 2011 67 Chapter4 Control 1 0 Validate Connections You need to verify that the controller can communicate with the devices that you have just configured To validate connections perform this procedure 1 Determine if communication has been established with the devices If a warning symbol A Appears over the 1 0 Configuration folder The controller cannot communicate with the device Go to step 2 Does not appear over the 1 0 Configuration The controller can communicate with the device folder and connections are valid 2 Identify any faults in communication modules by working down through the I O configuration tree Si 1 0 Configuration 1 1 1756 CNB A Local _CNB S fh 4 0 1756 CNB 4 Remote_ControlNe fh 5 1756 0816 Remote_Output_r 6 1756 1B16 Remote_Input_mox In this example faults occurred at the remote 1756 CNB module and the I O modules added below it 3 Identify the fault co
32. 2CN USB to ControlNet cable You are not required to configure the driver in RSLinx Classic software IMPORTANT _ If you are running RSLinx Classic software version 2 51 2 52 or 2 53 you must manually install the USBCIP driver To obtain the driver installation package refer to answer ID 55431 on the Rockwell Automation Knowledgebase at http www rockwellautomation com knowledgebase If you are running RSLinx Classic software version 2 54 or later the USBCIP driver is already installed on the computer After preparing the driver for use connect the card or cable to the computer and then connect the computer to the network Rockwell Automation Publication CNET UM001D EN P June 2011 25 Chapter2 Connect a Computer to the ControlNet Network Co nfigure the ControlNet To configure a ControlNet communication driver perform this procedure in Communication Driver in RSLinx Classic software RSLinx Classic Software IMPORTANT _ f you are using a 1794 U2CN cable to connect to the network you are not required to configure the driver 1 From the Communications menu choose Configure Drivers Commu nications Station DDE OPC RSwWho Carl m Whewker ike 2 From the Available Driver Types pull down menu choose a driver for a ControlNet device Configure Drivers Available Driver Types cose Add New RS 232 DF1 devices Help Ethernet devices 0 Ethernet IP Driver 1784 KT KTX DJ PKTX D PCMK
33. 5CR 19 11 Controller Tags C File Edit View Search Logic Communications Tools Window Help acl 6 tee oo fl E RUN n Fok EJ M BAT Tio D All Tags fa ControlNet v 8 4 Alias For Base Tag aed meS Monitor Consumed_tag New Tag which aliases Consumed_tag Edit Consumed_tag Properties Alt Enter Edit Consumed_tag Description Ctrl D 80 Rockwell Automation Publication CNET UM001D EN P June 2011 Produce and Consume Tags interlock controllers Chapter 5 7 From the Tag Properties dialog box complete these fields From the Type pull down menu choose Consumed e Inthe Data Type field type a data type that the controller can produce A controller cannot produce a tag by using the MSG or INT data types i Tag Properties Consumed_tag General Name Consumed_tad i Description Type Consumed v Alias For Data Type DINT a Scope fa ControlNet_Controller External Read write Access Style Decimal 8 Click Connection 9 From the Consumed Tag Connection dialog box complete these fields From the Producer pull down menu choose Producing_controller This menu contains all possible paths to previously configured controllers in the I O tree In the Remote Data field type the name of the produced tag in the producing controller Int
34. CNB 1768 CNBR 1769 CompactLogix 1769 L32C 1769 L35CR built in ControlNet port ControlLogix 1756 CN2 1756 CN2R 1756 CNB 1756 CNBR SoftLogix 1784 PCIC unscheduled data only or 1784 PCICS unscheduled data only 94 Rockwell Automation Publication CNET UM001D EN P June 2011 PanelView Terminal Communicate with PanelView Terminals Chapter 7 4 From Module Properties dialog box configure the local ControlNet module For information on configuring local ControlNet communication modules refer to Configure a ControlNet Module on page 29 New Module Type 1756 CN2 B 1756 ControlNet Bridge Change Type Vendor Allen Bradley Name Node Description Slot Revision Electronic Keying Compatible Keying v ea ControlNe a Cut Ctrl x 6 From the Select Module Type dialog box select the PanelView terminal and click OK E Select Module E Communications E Controllers Drives erator Terminal Allen Bradley Other By Category ByVendor Favorites A Rockwell Automation Publication CNET UM001D EN P June 2011 95 Chapter 7 Communicate with PanelView Terminals 7 From the Module Properties dialog box configure the terminal For information on configuring local ControlNet communication modules refer to Configure a ControlNet Module on page 29 New Module Type PanelView 2711 P
35. Mode Module Fault Status Offline Download the Project to the Logix5000 Controller IMPORTANT Before you download your RSLogix 5000 project to your ControlNet modules consider whether you will schedule the ControlNet network offline or online e lf you are going to schedule the network offline complete the procedure in the section Schedule the Network Offline on page 45 e f you are going to schedule the network online complete the procedure in this section and then proceed to the section Schedule the Network Online on page 49 When you have added the local and remote ControlNet communication modules to your RSLogix 5000 project download the new configuration to your Logix5000 controller To download a project to a Logix5000 controller follow this procedure 1 Because you must schedule the ControlNet network before by using the new configuration switch your Logix5000 controller to Program mode using one of these methods e Turn the controller keyswitch to PROG e Turn the controller keyswitch to REM and use RSLogix 5000 software 2 In RSLogix 5000 software from the Communications menu choose Who Active eee Tools Winc Who dctive Seler tRerent Path 36 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 3 From the Who Active dialog box browse to and select the controller to which to download a project and click Download f Who Active
36. R module with a 1756 CN2R module Release notes for individual modules indicate the specific compatibility details When a module is created the module developers consider the module s development history to implement capabilities that emulate those of the previous module However the developers cannot know future developments Because of this when a system is configured we recommend that you configure your module by using the earliest that is lowest revision of the physical module that you believe will be used in the system By doing this you can avoid the case of a physical module rejecting the keying request because it is an earlier revision than the one configured in the software EXAMPLE In the following scenario Compatible Keying prevents 1 0 communication The module configuration is for a 1756 IB16D module with module revision 3 3 The physical module is a 1756 IB16D module with module revision 3 2 In this case communication is prevented because the minor revision of the module is lower than expected and may not be compatible with 3 3 Module Configuration Vendor Allen Bradley Te Me celta aa ae Product Type Digital Input CO ECON Module Catalog Number 1756 IB16D De Major Revision 3 Fe Minor Revision 3 FZ Open Modde Properties Caneel Hele Communication is prevented Physical Module Vendor Allen Bradley Product Type Digital Input Module Catalog Number 1756 IB16D Major R
37. SLogix 5000 project with the CompactLogix 1769 L32C or 1769 L35CR controller the Controller Organizer creates a ControlNet port in the local chassis In this case you do not need to add a separate local communication module e Add distributed I O to your RSLogix 5000 project e Schedule the ControlNet network via RSNetWorx for ControlNet software e Use the I O information in RSLogix 5000 software You can also validate connections to distributed I O when controlling it over a ControlNet network This task is particularly useful when one or more of the connections are not working but is not required especially when all connections appear to work normally Rockwell Automation Publication CNET UMO001D EN P June 2011 55 Chapter4 Control 1 0 Set Up the Hardware Local Chassis Logix5000 e jaje e le Controller with ControlNet j communication module Requested Packet Interval RPI In this example the Logix5000 controller uses a ControlNet communication module in the local chassis to connect to the ControlNet network The distributed remote I O has a ControlNet adapter to connect it to the ControlNet network Figure 10 Overview of ControlNet 1 0 Distribution Distributed 1 0 ControlNet adapter with 1 0 modules Programming Terminal Make sure of the following e All wiring and cabling are prop
38. User Manual Allen Bradley ControlNet Network Configuration na Al As j r am 3 yR j i ay Allen Bradley Rockwell Software Automation Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls publication SGI 1 1 available from your local Rockwell Automation sales office or online at http www rockwellautomation com literature describes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation Inc be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment The examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation Inc cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information circuits equipme
39. ag All ControlNet modules support at least 32 connections The number of available connections limits the number of tags that can be produced or consumed If the communication module uses all of its connections for I O and other communication modules no connections are left for produced and consumed tags Rockwell Automation Publication CNET UM001D EN P June 2011 73 Chapter 5 Produce and Consume Tags interlock controllers Table 18 Produced and Consumed Tags and Number of Connections Controller Available Connections CompactLogix PowerFlex 700S with DriveLogix 100 software ControlLogix 250 SoftLogix5800 Communication Card Available Connections ControlNet port on the 32 CompactLogix controller 1768 CNB and 1768 CNBR 48 CompactLogix ControlNet modules 1788 CNx card in PowerFlex 700S with DriveLogix controller 32 total ControlNet connections 22 of which can be scheduled and used for producing and consuming tags 1756 CN2 and 1756 CNZ2R series B ControlNet modules in the local chassis of a ControlLogix controller 131 Note that 3 of the 131 connections are always reserved for redundant control Therefore 128 connections are available for standard use 1756 CNB and 1756 CNBR ControlNet modules in the local chassis of a ControlLogix controller 64 We recommend that you do not use more than 40 48 scheduled connections 1784 PCICS card in a SoftLogix5800 controller
40. ai au hae io eee a eee te 56 Requested Packet Interval RPI witts sor sspan teeta ntetuaeseeeiearsuegs 56 Communication Format 0 cc cee cece eee e tenn e een ennees 57 Direct or Rack optimized Connections 0s seen eee 58 Owners hipaa eiiean a E a aor eactaee saya AEE 61 Adda Remote Adaptetscc pun ieraracueter tna r EY 63 Add Distributed T O s sraa a a E Ea a TAa 63 Distributed I O Communication Formats 000 cece 65 Access Distributed I O ovnicesavasaeua saan unite ehdn deadaanuasas 65 Validate Connections 4 6 Wiaieis 20 lt b 2bedon Geek lad Seeded ok 68 Chapter 5 Terminology cote J trinseraeateaty ie tents oe aa siaer EE e behean 71 Set Up the Hardware uve Medea EEA E tease oe eh ale 72 Determine Connections for Produced and Consumed Tags 73 Organize Tags for Produced or Consumed Data 0006 75 Adjust for Bandwidth Limitations 00 0c cee e eee eee 76 Produce as Tages petals Guba eects E AE E baeahiatuen porters 77 Cons me d Tap eo eon URNS egestas pom PUR ST Pee ASS 79 Chapter 6 Set Upthe Hardwares ani tae teme ene aE aces 84 Guidelines for MSG Instructions ccccccececeeeeceeesens 85 Determine Connections for Messages 000i icincvcoryevewsueenawees 86 Guidelines for Caching Message Connections 00 86 Enter Message Logic sers wsax ce duintad ty aa resape ntur Es iisa r prrs 86 Add the ControlNet Modules and Remote Devices to the Local Controller
41. ance Lengths In a ControlNet network the maximum length depends on the number of nodes on a segment a segment is a section of trunk between two terminators Use repeaters to add segments or increase length Figure 8 Maximum Length of a ControlNet Network Maximum Allowable Segment Length 1000 m 3280 ft 16 3 m 53 4 ft X Number of Taps 2 1000 3280 _ g Add a Repeater 750 2460 E 500 1640 No Repeater S 250 820 Required i m a 2 16 32 48 This graph assumes that a 1786 RG6 cable is being used Rockwell Automation Publication CNET UM001D EN P June 2011 Chapter 2 Connect a Computer to the ControlNet Network This chapter explains how to set up a computer to operate on a ControlNet network Topic Page Configure the ControlNet Communication Driver in RSLinx Classic Software 26 You need to load a ControlNet communication driver for a computer to communicate with other devices on a ControlNet network A computer uses this driver to do the following e Upload and download controller projects over ControlNet via RSLogix 5000 software e Schedule the ControlNet network via RSNetWorx for ControlNet software e Operate an HMI type application Depending on the connection device you can use one of these drivers e 1784 PCIC or 1784 PCICS card You must configure the driver in RSLinx Classic software as described on page 26 e USBCIP driver Use only with a 1784 U
42. anelView Operator Terminal Vendor Allen Bradley Parent LocalCNB Name HMI_Device Description Comm Format Data 32 INT v a Revision 1 Electronic Keying Compatible Keying Org anize Controller Data Organize data for a Panel View or PanelView Plus terminal based on how the data for a PanelView Terminal is used Data Type Required Actions Time critical scheduled data Use the 1 0 tags of the terminal The terminal supports a maximum PanelView terminals only of 32 input tags and 32 output tags The tags for this data were created when you added the PanelView terminal to the 1 0 configuration of the controller They are similar to the tags of 1 0 modules Not time critical PanelView Create arrays to store the data or PanelView Plus terminals 1 For each screen create a BOOL array with enough elements for the bit level objects on the screen For example the BOOL 32 array gives you 32 bits for push buttons and indicators 2 For each screen create a DINT array with enough elements for the word level objects on the screen For example the DINT 28 array gives you 28 values for numeric entry controls and numeric displays To access the scheduled I O tags of the PanelView terminal use these address formats Terminal Function Address Definition Writes the data name_of_terminal Data x y Reads the data name_of_terminal 0 Data x y Address Variable Definition name_of_ter
43. ata at a rate that is faster than the NUT When you run RSNetWorx for ControlNet software an Actual Packet Interval API is calculated The API is equal to or faster than the RPI Actual Packet Interval API The API is the actual update rate for a particular piece of data on the network A ControlNet network sets this rate equal to or faster than the RPI based on the binary multiple of the NUT which is the next fastest rate at which a module can send data If this cannot be done a ControlNet network provides reports that it cannot support the configuration Rockwell Automation Publication CNET UM001D EN P June 2011 17 Chapter 1 18 ControlNet Overview Understand the Effect of the NUT on the API This example illustrates how the NUT affects the API A module on the network can produce data only at binary multiples of the NUT to a maximum of the NUT multiplied by 128 These multiples are referred to as rates on a ControlNet network Therefore with a NUT of 5 ms the module can send data at these rates Table 5 NUT Example Data Rates NUT Multiple Rate at Which Module Can _ Send Data oms 1 5 ms 2 10 ms 4 20 ms 8 40 ms 16 80 ms 32 160 ms 64 320 ms 128 640 ms In this example if you specify an RPI of 25 ms then the network produces an API of 20 ms which is the next fastest rate at which the module can send data The module places the data on the network at every fourth network updat
44. ation Feedback Your comments will help us serve your documentation needs better If you have any suggestions on how to improve this document complete this form publication RA DU002 available at http www rockwellautomation com literature Rockwell Otomasyon Ticaret A S Kar Plaza Ig Merkezi E Blok Kat 6 34752 erenk y stanbul Tel 90 216 5698400 www rockwellautomation com Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation NV Pegasus Park De Kleetlaan 12a 1831 Diegem Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication CNET UMO001D EN P June 2011 Supersedes Publication CNET UM001C EN P November 2005 Copyright 2011 Rockwell Automation Inc All rights reserved Printed in the U S A
45. ation Modules for a 1768 Modules for a 1769 Modules for a Modules for a 1769 Network CompactLogix System CompactLogix System ControlLogix Chassis CompactLogix Packaged Controller System ControlNet e 1768 L43 or 1768 L45 Not applicable e 1756 CN2 module Not applicable controller e 1756 CN2R module e 1768 ENBT module e 1756 CNB module e 1768 CNB R module e 1756 CNBR module e 1756 ENBT module e 1756 EN2T module e 1756 EN2TR module e 1756 EN3TR module DeviceNet e 1768 L43 or 1768 L45 e 1769 L32E or 1769 L35E e 1756 DNB module e 1769 L23E 0B1B controller controller controller e 1756 ENBT module e 1769 L23E OBFC1B controller e 1768 ENBT module e 1769 SDN scanner or 1788 1756 EN2T module e 1769 L23 OBFC1B controller e 1769 SDN scanner EN2DN module e 1756 EN2TR module e 1769 SDN scanner e 1756 EN3TR module E 1 Can serve as a dedicated standalone bridge from an EtherNet IP network to a DeviceNet network Exchange Information on a ControlNet Network ControlNet communication modules use a message based protocol that implements a relative path to send a message from the producing module in a system to the consuming modules This protocol also lets you communicate between devices on a ControlNet DeviceNet or EtherNet IP network without writing additional application code With unscheduled data the device from which a message originates such as a Logix5000 controller contains the path information that makes sure the m
46. d DINTs throughout the project This increases the efficiency of your project because Logix5000 controllers execute more efficiently and use less memory when working with 32 bit integers DINTs If you want to enable more than 16 MSGs at one time use some type of management strategy If you enable more than 16 MSGs at one time some MSG instructions may experience delays in entering the queue To guarantee the execution of each message you can take these actions e Enable each message in sequence e Enable the messages in smaller groups e Program a message to communicate with multiple modules e Program logic to coordinate the execution of messages Cache connected MSGs that execute most frequently Cache the connection for those MSG instructions that execute most frequently up to the maximum number permissible for your controller revision This optimizes execution time because the controller does not have to open a connection each time the message executes Limit the number of unconnected and uncached MSGs to fewer than the number of unconnected buffers The controller can have 10 40 unconnected outgoing buffers e The default number is 10 e fall the unconnected buffers are in use when an instruction leaves the message queue the instruction errors and does not transfer the data e You can increase the number of unconnected buffers to a maximum of 40 For more information on programming MSG instructions
47. des specifically the fault at the module that is highest in the I O tree 4 Right click the module and choose Properties Gj 170 Configuration S 1 1 1756 CNB A Local CNB z Emi Gone Bite Ctrl C Cite Del Cross Reference Ctrl E 5 From the Module Properties dialog box click the Connection tab E Module Properties Local_CNB 0 1756 CNB A 1 1 General Connection RSNetWor Module Info Backplane Requested Packet Interval RPI 20 044 ms 2 0 750 0 ms T Inhibit Module I Major Fault On Controller If Connection Fails While in Run Mode Module Fault Code 16 0317 Connection Request Error Connection not scheduled Status Faulted Cancel Apply Help 6 Identify the fault in the Module Fault area 68 Rockwell Automation Publication CNET UM001D EN P June 2011 Control O Chapter 4 7 To interpret the fault codes return to RSLogix 5000 software and from the Help menu choose Contents File Edit View Search Logic Communications Tools Window alla 2 sole of eee Instruction Help i n e Mo ke BUN LA4 H H Release Notes No Forces b E OK T No Edits a BAT 4 H Online Books ee E o Redundancy x ii A Vendor Sample Projects E Quick start WE Learning Center FE Resource Center Controller PLSSampleProject Controller Tags Controller Fault Handler Power Up Handler 8 From the Help Topics dialog box click the I
48. doudtsnnteecomnees 19 Default Parameters ici wien sasecd nh i nae dle eet os 21 ControlNet Network Capacity and Topology 0 0005 21 WOpolosy s aenea a EE EERE AEEA eke ae 21 Number of Nodes lt 2 avaricacads ion newts idweaadneetaediaate 24 Lengthsreno fester iuh gue As aii Reheat Ake Malls 5 Aes Madea 24 Chapter 2 Configure the ControlNet Communication Driver in RSLinx Classic Sottwatesutc ai ceee eek onthe kee eee el clay 26 Chapter 3 Use RS Logix 5000 Softwatess ey stte ssatescns mance eeenssewstnanknss 29 Configure the I O Configuration Tree in Your Project 29 Add and Configure a Local ControlNet Module 30 Add and Configure a Remote ControlNet Module 33 Download the Project to the Logix5000 Controller 36 Electronic Keying eiee Sx aiiwds E by OaE LEELEE 37 Use RSNet Worx for ControlNet Software 00 cece cece eee 44 Schedule a ControlNet Network for the First Time 44 Schedule the Network Offline 0 ccc cece cece eeeeees 45 Schedule the Network Online 0 cece ce ccc ceeeeeees 49 Reschedule a ControlNet Network that has Previously been Scheduled i ccccuesudds dete peeks 53 Rockwell Automation Publication CNET UMO001D EN P June 2011 5 Table of Contents Control 1 0 Produce and Consume Tags interlock controllers Messaging Communicate with PanelView Terminals Index Chapter 4 Set Up the Hardware yc 2v
49. e communication format and RPI b Click Next to proceed through subsequent screens to configure additional parameters such as filter times and fault actions 64 Rockwell Automation Publication CNET UM001D EN P June 2011 Access Distributed 1 0 Control O Chapter 4 Distributed 1 0 Communication Formats Your selection of communication format when you add distributed I O modules is based on whether you want rack optimized or direct connections to each distributed I O module and corresponds directly with the communication format you chose for your remote adapter Remote Adapter Communication Format Distributed 1 0 Communication Format Rack Optimization Rack Optimization None An appropriate direct connection format I O information is presented as a structure of multiple fields dependent on the specific features of the I O module The name of the structure is based on the location of the I O module in the system Each I O tag is automatically created when you configure the I O module in RSLogix 5000 software Each tag name follows this format Location SlotNumber Type MemberName SubMemberName Bit Address Variable Definition Location Identifies the network location by using one of these values e LOCAL Local DIN rail or chassis e ADAPTER_NAME Remote adapter or bridge that you specify SlotNumber Slot number of 1 0 module location in its chassis Type Identifies one of these types of data e I
50. e interval to produce the 20 ms API Similarly if you specify an RPI of 150 ms the network produces an API of 80 ms Schedule the Network Connections over a ControlNet network can be one of the following e Scheduled Data transferred at specific times e Unscheduled Data transferred when the network can accommodate the transfer To use scheduled connections you must schedule the ControlNet network via RSNetWorx for ControlNet software For more information on how to schedule a ControlNet network with RSNetWorx for ControlNet software see the section Use RSNetWorx for ControlNet Software on page 44 You must use RSNetWorx for ControlNet software to enable any connection in a remote chassis In addition RSNetWorx software transfers configuration information for the remote modules verifies and saves NUT and other user specified network parameters and establishes a schedule that is compliant with the RPI and other connection options specified for each module Rockwell Automation Publication CNET UM001D EN P June 2011 ControlNet Overview Chapter 1 IMPORTANT RSNetWorx for ControlNet software must be run whenever a scheduled connection is added to removed from or changed in your system Control of Scheduled 1 0 Scheduled connections let you send and 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
51. ections used 7 1 In this example the remote ControlNet adapter uses the communication format of None TIP Direct connections to many modules may not be feasible because the module supports a finite number of connections and direct connections may require more resources than the module has available In this case use rack optimized connections Refer to Rack optimized Connections for I O Modules on page 60 for more information on how to limit connection use and network traffic Rockwell Automation Publication CNET UM001D EN P June 2011 59 Chapter4 Control 1 0 Rack optimized Connections for 1 0 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 ControlNet Network Controller with ControlNet Communication Module Three Digital 1 0 Modules Two Analog 1 0 ControlNet Adapter with ControlNet Adapter with Modules ControlNet Adapter with Two Digi al 1 0 Modules This table calculates the connections in this example Table 12 Connection Calculations System Connections Amount Controller to local ControlNet communication module 0 Controller to ControlNet adapters with digital modules rack 2 optimized connection to each adapter Controller to ControlNet adapter with analog modules d
52. er of the controller Within the folder you organize modules into a hierarchy of tree branch and parent child Controller and Local Remote Adapter Communication Modules and 1 0 Modules Controller Organizer EX al B Fj O mar Controller ControlNet_Controller I Controller Tags Controller Fault Handler Power Up Handler P Sj Tasks Device a MainTask E 3 MainProgram Gi Unscheduled Programs Phases Jj Motion Groups Ungrouped Axes Add On Instructions B Data Types i User Defined amp oe Strings oa Add On Defined E3 Ep Predefined E E Module Defined Trends amp Yo Configuration 1756 Backplane 1756 410 fa 0 1756 L75 ControlNet_Controller S 1 1756 CN2 A ControlNet_Module Ss ControlNet Local Communication Bridge Module 1 1756 CN2 A ControlNet_Module amp g 2 1734 ACNR A Remote_CNET amp PointIO 3 Slot Chassis pe 0 1734 ACNR A Remote_CNET due i 1 1734 IB2 C Remote_Input Distributed 10 Module gt 2 1734 IB8 C Remote _Input_Sink 1756 175 164 till 1756 CN2R 1756 CN2 Remote Adapter for the Distributed 1 0 Chassis or DIN Rail Rockwell Automation Publication CNET UM001D EN P June 2011 63 Chapter4 Control 1 0 To add distributed I O to your RSLogix 5000 project perform this procedure 1 Add the
53. erly connected e The communication driver is configured for the programming workstation When you configure an I O module you define the RPI for the module The RPI specifies the interval at which data updates over a connection For example an input module sends data to a controller at the RPI that you assign to the module Configure the RPI in milliseconds RPI is used only for a module that produces or consumes data For example a local ControlNet communication module does not require an RPI because it is not a data producing member of the system but only a bridge In Logix5000 controllers I O values update at an interval that you configure via the I O configuration folder of the project The values update asynchronously to the execution of logic At the specified interval the controller updates a value independently from the execution of logic 56 Rockwell Automation Publication CNET UM001D EN P June 2011 Communication Format Table 9 Communication Formats Control O Chapter 4 When you configure a remote ControlNet communication module or an I O module you choose a communication format The chosen communication format determines the data structure for tags associated with the module Many I O modules support different formats Each format uses a different data structure The chosen communication format also determines the following e Direct or rack optimized connection e Ownership of outputs Communication Fo
54. essage reaches its consumers For a full explanation of unscheduled and scheduled data see Network Update Time NUT on page 16 Because the producing module holds this information other modules along the path simply pass the information along and do not need to store it The significant benefits include the following e You do not need to configure routing tables in the bridging module which greatly simplifies maintenance and module replacement e You maintain full control over the route taken by each message which enables you to select alternative paths for the same end module Scheduled data in Logix based systems use the producer consumer networking model instead of a source destination master slave model The producer consumer model reduces network traffic and increases transmission speed 14 Rockwell Automation Publication CNET UM001D EN P June 2011 ControlNet Overview Chapter 1 In traditional I O systems controllers poll input modules to obtain their input status In a Logix system digital input modules are not polled by a controller Instead they produce multicast their data either upon a change of state COS or periodically The frequency of update depends upon the options chosen during configuration and where on the network the input module resides The input module therefore is a producer of input data and the controller is a consumer of the data The controller can also produce data for other contro
55. evision 3 Minor Revision 2 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 EXAMPLE In the following scenario Compatible Keying allows 1 0 communication The module configuration is for a 1756 IB16D module with module revision 2 1 The physical module is a 1756 IB16D module with module revision 3 2 In this case communication is allowed because the major revision of the physical module is higher than expected and the module determines that it is compatible with the prior major revision Module Configuration Vendor Allen Bradley 17561816D 16 Point 10V 30V DC Diagnostic Input AllersBradley Local Product Type Digital Input gt oe Module Catalog Number 1756 IB16D S mer ot 4 Electoric Keying ConpatbieKeya Major Revision 2 Minor Revision 1 I Open Module Properties Cancel Help Communication is allowed Physical Module Vendor Allen Bradley Product Type Digital Input Module Catalog Number 1756 IB16D Major Revision 3 Minor Revision 2 IMPORTANT Changing electronic keying selections online may cause the 0 communication connection to the module to be disrupted and may result in a loss of data Disabled Keying Disabled Keying indicates the keying attributes are not considered when attem
56. ew Tag Ctrl Ww 8 Tasks Monitor Tags Sa MainTask Edit Tags MainProgra R ad P Verify 3 From the Controller Tags dialog box type the name of the new tag in an available Tag Name field f RSLogix 5000 ControlNet 1769 L35CR 19 11 File Edit view Search Logic Communications Tools wi fa ControlNet All Tags Name zals Alias For MQ 42 O4yUO gt Tag Name Field Rockwell Automation Publication CNET UM001D EN P June 2011 71 Chapter 5 78 Produce and Consume Tags interlock controllers 4 Right click the new tag name and choose Edit Tag Properties Scope a ControiNet All Tags N ame Consumed tag o Ee A Monitor Produced_tag New Tag which aliases Produced_tag oO 2 g Q fa a N amp ial Edit Produced_tag Properties Alt Enter Edit Produced_tag Description Ctrl D 5 On the Tag Properties dialog box from the Type pull down menu choose Produced f Tag Properties Produced_tag General Name Produced_tag Description Alias For Data Type CJ Scope fa ControlNet Extemal Read Write Access Style Decimal C Constant 6 In the Data Type field type a data type that the controller can produce A controller cannot produce a tag by using MSG or INT data types 7 Click the Connection
57. he RPI field enter the rate at which the tag will be produced Consumed Tag Connection Connection Status Produce ie Remote Data Tag Name or Instance Number 200 ill ns Cancel Help 10 Click OK 11 Use RSNetWorx for ControlNet software to schedule the network Rockwell Automation Publication CNET UM001D EN P June 2011 81 Chapter 5 Produce and Consume Tags interlock controllers Notes 82 Rockwell Automation Publication CNET UM001D EN P June 2011 Chapter 6 Messaging This chapter explains how to use MSG instructions to send data to and receive data from other modules on a ControlNet network Topic Page Set Up the Hardware 84 Guidelines for MSG Instructions 85 Determine Connections for Messages 86 Enter Message Logic 86 Configure a Message Instruction 88 Stagger the Messages 90 Use peer to peer messaging when these conditions apply Data is sent when a specific condition occurs in your application Data is sent at a slower rate than is required by produced and consumed tags Data is sent to devices that communicate only with unscheduled data Rockwell Automation Publication CNET UMO001D EN P June 2011 83 Chapter6 Messaging Set Up the H ardware In this example the controller in the local chassis uses a MSG instruction to send a message to another module which can be a controller on the ControlNet network Figure 12 Peer
58. he data into the DeviceNet I O image and then use RSLinx OPC to send the data to the Logix5000 controller over the ControlNet network This method conserves the limited bridging resources of your CompactLogix controller 12 Rockwell Automation Publication CNET UM001D EN P June 2011 ControlNet Overview Chapter 1 The following example shows how a DeviceNet bridge links to an EtherNet IP network in RSLinx software Figure 3 EtherNet IP Bridge Linking to a ControlNet Network RSLinx Classic Gateway RSWho 1 s5 Eile Edit view Communications Station DDE OPC Security Window Help Bliz vy V Autobrowse Reres 2o EE Browsing node 55 not found EE workstation USMAYCCIANCI Linx Gateways Ethernet ed 1 Sa AB_ETHIP 1 Ethernet es A a 2 E la 10 88 92 10 1756 EN2T A 1756 EN2T A 1756 CNB 1756 CN2R B 1794 ACN1 1734 AC amp Backplane 1756 A10 4 f 00 1756 CN2R 1756 CN2R B 3 01 1756 CNBR D 1756 CNBR D D05 40 4 F 01 1756 CNBR D 1756 CNBR D H 02 1756 CN2R 1756 CN2R B 03 1794 ACN15 FLEX I O Contre E 04 1734 ACNR ControlNet Adap 03 1756 L73 LOGIX5573 1756 L73 A LC f 04 1756 EN2T A 1756 EN2T A i as AB_ETHIP 2 Ethernet AB_ETHIP 3 Ethernet AB_VBP 1 1789 A17 4 Virtual Chassis For Help press F1 04 27 11 01 20PM 1 EtherNet IP network 3 ControlNet Bridge in 1756 system 2 EtherNet IP bridge in 1756 system 4 ControlNet network The following tables list
59. he module p Listen only Controlling input modules differs from controlling output modules Table 14 Module Ownership Control Module Type Input modules Ownership Owner Description The contro ler that establishes an owner connection to an input module configures that module This configuring controller is the first controller to establish an owner connection Once a controller owns and configures an input module other controllers can establish owner connections to that module This lets additional owners continue to receive multicasted data if the original owner controller s connection to the module breaks All other additional owners must have the identical configuration data and communication format as the original owner controller or the connection attempt is rejected Listen only Once a con to that mod owner con receive mul ule These controllers can receive m ticast data roller owns and configures an input module other controllers can establish a listen only connection ulticast data while another controller owns the module If all ollers break their connections to the input module controllers with listen only connections no longer Output modules 62 Owner The contro connection connection er that establishes an owner connection to an output module configures that module Only one owner is allowed for an output module If another controller attempts to establ
60. ilable Media Media Configuration Description Quantity Description 1786 APA Repeater Adapter 1000 meters RAGE Coax Cable 1786 APFS Short Distance Fiber bv 1786 RPFM Medium Distance Fibe 1786 Long Distance Fiber Module 1797 RPA Repeater Adapter IS ve 1797 RPFM Medium Distance Fibe Glass Fiber Cable 9904 RPA Repeater Adapter 9904 RPFS Short Distance Fiber bv 9904 RPFM Medium Distance Fibe 9904 Long Distance Fiber Module 1786 RPT Coax Repeater 1786 RPTD Coax Repeater 24VD 9904 RPT Coax Repeater 9904 RPTD Coax Repeater 24D AGE Coax Cable 1786 RPFRL Long Fiber Ring Rep 1786 RPFRXL Extra Long Fiber Ri a js From the File menu choose Save From the Save Configuration dialog box click Optimize and rewrite the schedule for all connections Save Configuration Either of the following choices will save the updated schedule OK to the file and to the online network if you are online Save Type Cancel Optimize and re write schedule for all connections c Help Click OK IMPORTANT Itis better to optimize connections However in some cases involving multiple controllers the Merge changes option is available This option lets controllers whose connections have not changed to continue uninterrupted operation When you merge changes into the existing schedule those controllers whose connections have not changed remain in Run mode rather than changing to Program mode In RSLogi
61. irect 2 connection for each analog 1 0 module Total connections used 4 The rack optimized connection limits connections but can also limit the status and diagnostic information that is available from the digital I O modules To increase the number of available connections use a rack optimized connection to any remote adapter with multiple digital I O modules that permit rack optimized connections instead of direct connections to those I O modules 60 Rockwell Automation Publication CNET UM001D EN P June 2011 Type of Ownership Owner controller Ownership Control O Chapter 4 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 Definition The controller that creates the primary configuration and communication connection to a module The owner controller writes configuration data and can establish a connection to the module The owner controller is the only device that controls the outputs Module Properties Local 1756 IB16 2 1 Type Vendor Parent Name Description An owner connection is any connection that does not include listen only in its j Comm Format communication format Revision 1756 IB16 16 Point 10 31 2 DC Input Allen Bradley Local Sl
62. ish an owner connection the attempt Is rejected Listen only Once a con roller owns and configures an output module other controllers can establish listen only connections to that module These controllers can receive multicast data while another controller owns the module If the owner controller breaks its connection to the output module all controllers with listen only connections no longer receive multicast data Rockwell Automation Publication CNET UM001D EN P June 2011 Control O Chapter 4 Add a Remote Ad apter The type of distributed I O determines your choice of a remote ControlNet adapter Before choosing a remote adapter you must add local and remote ControlNet modules to an RSLogix 5000 project For more information on adding ControlNet modules to a project see Add and Configure a Local ControlNet Module on page 30 and Add and Configure a Remote ControlNet Module on page 33 Table 15 Remote Adapter Options Type of Distributed 1 0 Required Remote Adapter Configuration Method 1756 ControlLogix 1 0 1756 CN2 1756 CN2R RSLogix 5000 software 1756 CNB 1756 CNBR 1768 CompactLogix 0 1768 CNB 1768 CNBR 1794 FLEX 1 0 1794 ACN15 1794 ACNR15 1797 FLEX Ex 1 0 1797 ANCR 1734 POINT 1 0 1734 ACNR 1738 ArmorPOINT 1738 ACNR Add Distributed 1 0 To communicate with I O modules in your system you add a bridge adapter and I O modules to the I O Configuration fold
63. j N oy A wy N ControlLogix controller with 1756 CN2 1756 CN2R 1756 CNB or 1756 CNBR module as the scanner IMPORTANT Foran enhanced redundancy system you must use a 1756 CNB 1756 CNBR 1756 CN2 series B or 1756 CN2R series B communication module The 1756 CN2 or 1756 CN2R series A module does not support enhanced redundancy For more information refer to the ControlLogix Enhanced Redundancy System User Manual publication 1756 UM535 10 Rockwell Automation Publication CNET UM001D EN P June 2011 ControlNet Overview Chapter 1 Bridge Across Networks Some ControlNet modules support the ability to bridge or route communication to and from different networks depending on the capabilities of the platform and communication devices IMPORTANT You can only bridge across networks to communicate with devices You cannot bridge across networks to control 1 0 even though RSLogix 5000 software can accept such a configuration in the I O Configuration folder All 1 0 control must originate and end on the same physical network The following table describes how communication can bridge across networks Table 1 Bridging Across Networks A device on this network Can communicate with a device on this network EtherNet IP ControlNet DeviceNet RS 232 EtherNet IP Yes Yes Yes Yes ControlNet Yes Yes Yes Yes DeviceNet No No Yes No RS 232 Yes Yes Yes Yes 1 To use RSNetWorx for ControlNet software to
64. k Edits Enabled Network schedule xc RSNetWorx for ControlNet File Edit View Network Device Diagnostics Tools Help BS n S Bele eael T Edits Enabled EA Network Update Time ms 5 00 Unscheduled Bytes Per Sec 544057 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 9 To change the network properties from default settings to those that best fit your network from the Network menu choose Properties Network schedule xc RSNetWorx for ControlNet Edit Yiew Network Device Diagnostics Tools Help 2 a bel J5 J Edits Ene s Online Network Up Unschedule Network Usage Hardware A Controle Enable Edits Upload from Network Download to Network Download Minimum to Network Keeper Status Scanner Signature Status 10 On the Network Parameters tab configure the network parameters as described in the table below and click OK Parameter Network Update Time ms Description The smallest user configurable repetitive time cycle at which data can be sent on a ControlNet network Max Scheduled Address This is the node with the highest network address that can use scheduled time on a ControlNet link 1 0 data is transferred during scheduled time RSNetWorx for ControlNet software sets this value We recommend that you not change it Max Unscheduled Address Node with the highest network address
65. l bits of a message instruction Configure a Message To configure a MSG instruction perform this procedure Instruction 1 Click E in the MSG box The Module Configuration dialog box appears Message Configuration message Configuration Communication Tag Message Type CIP Data Table Read i Source Element temperature Number Of Elements 1 Destination Element local_array Y Index 0 O Enable Enable Waiting Start Done Done Length 0 Error Code Extended Error Code C Timed Out Error Path Error Text 2 From the Message Type pull down menu choose a message type 3 In the Source Element field type the appropriate information 4 In the Number of Elements field enter the number of elements 88 Rockwell Automation Publication CNET UM001D EN P June 2011 Function Read receive the data Configuration Box Message Type Messaging Chapter 6 5 From the Destination Element pull down menu choose the instruction s destination element The message instruction s destination determines how the message is configured Required Information CIP Data Table Read Source Element First element of the tag that contains data in the other controller Number of Elements Number of elements to transfer Destination Tag First element of the controller scoped tag in this controller for the data Write send the data Message Ty
66. le on all ControlNet communication modules The communication module creates a rack image and returns I O input data in the rack image to the owner controller The difference between this choice and rack optimized is that the 1 0 data in the rack image is returned to a controller that does not control the outputs but is listening only to its input data Effect on RPI You can specify an RPI that meets this criteria e Equal to or greater than the NUT e Inthe range permitted by RSLogix 5000 programming software for example 2 750 ms When you set the RPI for a remote ControlNet communication module we recommend you use a rate that is a power of two times the NUT For example if your NUT 5 ms we recommend these RPI values Optimal RPI values None No RPI is required The RPI field is dimmed 4 On the Module Properties dialog box configure the connection properties and then click Apply Connection Property Action Requested Packet Interval RPI Type the requested packet interval between 2 0 750 0 ms If your module uses one of the rack optimized communication formats the RP must be equal to or greater than the ControlNet Network Update Time NUT Inhibit Module If the module does not need or IMPORTANT When you tes o communicate with the controller check the checkbox If the module needs to communicate with the controller leave the checkbox cleared this porti
67. llers to consume The produced and consumed data is accessible by multiple controllers over the Logix backplane and the ControlNet network This data exchange conforms to the producer consumer model A ControlNet network link s most important function is to transport time critical control information such as I O data and control interlocking Other information that is not time critical such as program uploads and downloads is also transported but does not interfere with time critical messages because a ControlNet network can transmit scheduled and unscheduled data On a ControlNet network link nodes transfer information by establishing connections Each message sent by a producer contains a Connection ID CID Nodes that have been configured to recognize the CID consume the message becoming consumers themselves Media access to the network is controlled by a time slice access algorithm Concurrent Time Domain Multiple Access CTDMA which regulates a node s opportunity to transmit in each network update interval NUI You configure how often the NUI repeats by selecting a network update time NUT in milliseconds Rockwell Automation Publication CNET UMO001D EN P June 2011 15 Chapter 1 ControlNet Overview Network Update Time NUT The network update time NUT is the shortest interval in which data can be sent on a ControlNet network It represents the fastest possible update rate for scheduled data transfers on that netw
68. mestamped Input Data communication format Connection for listening to data from the module A listen only communication format that matches the data the 1 0 module is broadcasting to other controllers Analog module Direct connection or to use specialty features of The data your controller needs from the 1 0 module For example if your electronic fuses or the module such as diagnostics timestamps or application uses a 1756 OF6CI module in a remote chassis that mus provide floating point output data choose the Float Data communication format Connection for listening to data from the module A listen only communication format that matches the data the 1 0 module is broadcasting to other controllers Rockwell Automation Publication CNET UM001D EN P June 2011 57 Chapter 4 Control 1 0 Term Direct connection Direct or Rack optimized Connections Logix5000 controllers use connections to transmit I O data These connections can be direct or rack optimized connections Definition A direct connection is a real time data transfer link between the controller and an analog or digital 1 0 module that enables your controller to collect more data from an I O module For example with a direct connection the controller can collect diagnostic status data from a 1756 IA8D module that would not be collected in a rack optimized connection The controller maintains and monitors the connecti
69. minal Name of the instance in the 1 0 configuration of the controller X Element of the input I or output 0 structure y Bit number within the input or output element 96 Rockwell Automation Publication CNET UM001D EN P June 2011 A access distributed 1 0 data 65 67 produced and consumed data 15 scheduled 1 0 tags 96 actual packet interval 17 18 adjust media configuration 48 52 tags for bandwidth limitations 76 API See actual packet interval bandwidth limitations 76 rack optimized communication format 57 requested packet interval rate 17 unscheduled maximum node address 21 bridge across networks 11 14 C cache message connections 86 capacity of ControlNet network 24 communicate across networks 11 14 between computer and devices 25 between controller and devices 68 with 1 0 modules 63 with PanelView products 91 96 communication driver 26 communication format distributed 1 0 65 effect on requested packet interval 34 rack optimized 60 select 57 65 communication path 50 configure ControlNet communication driver 26 ControlNet module 29 54 message instructions 88 89 connection between computer and ControlNet network 25 for produced and consumed tags 73 validate 68 consumed tags creating in RSLogix 5000 software 79 81 defined 71 determine connections 73 guidelines 75 organize tag data 75 control 1 0 55 69 ControlNet module bridge across networks 11 14 configure 29 54 overview 9 10 Index Contr
70. n Bradley 1756 CNB D 1756 ControlNet Bridge Allen Bradley 1756 CNB E 1756 ControlNet Bridge Allen Bradley 1756 CNBRJA 1756 ControlNet Bridge Redundant Media Allen Bradley ki Add Favorite By Category i By Vendor Favorites IMPORTANT This procedure shows the New Module dialog box for a 1756 CN2R B However various dialogs appear during configuration depending on the ControlNet module you select For help configuring a module refer to the online help in RSLogix 5000 software Rockwell Automation Publication CNET UM001D EN P June 2011 33 Chapter3 Configure a ControlNet Module 3 Complete the fields on the New Module dialog box and then click OK Field Action Name Type a name for the local ControlNet module Node Enter the module s node number on the network Description Type a description of the local ControlNet module Chassis Size Enter the total number of slots in the chassis Comm Format Format below Choose a communication format as described in Communication You do not need to assign a communication format for 1784 PCIC 1784 PCICS or 1788 CNx cards Slot Enter the module s slot number in the chassis Revision Choose a major and minor revision of RSLogix 5000 software Electronic Keying Choose a keying option as described in Electronic Keying on page 37 Open Module Properties Leave the box checked to configure connecti
71. nce Ctri amp Properties N Alt Enter operties for selected component Rockwell Automation Publication CNET UM001D EN P June 2011 45 Chapter 3 46 Configure a ControlNet Module 2 From the Module Properties dialog box click the RSNetWorx tab E Module Properties Local 2 1756 CN2R B 20 1 General Connection RSNetWorx Module Info Backplane ControlNet file xc Launch RSNetWorx for ControlNet ae View and edit the ControlNet network Schedule the ControlNet network RSNetWors for ControlNet cannot be launched until a ControlNet file is specified above 3 In the ControlNet file field type a name for a new ControlNet file 4 Click Apply 5 When a message appears prompting you to create the file click Yes This action creates the file that RSNetWorx for ControlNet software uses offline to browse and schedule the network 6 Click Schedule the ControlNet network 7 Click the icon circled below to launch RSNetWorx for ControlNet software E Module Properties Local 2 1756 CN2R B 20 1 General Connection RSNetWors Module Info Backplane ControlNet file xc Network schedule xc Found in C ASLogix 5000 Projects Launch RSNetWorx for ControlNet View and edit the ControlNet network Schedule the ControlNet network Status Offline Apply 8 To enable edits in the schedule in RSNetWorx for ControlNet software chec
72. ndex tab Contents Index Find 1 Type the first few letters of the word you re looking for module fault 9 Type module fault 10 In the list of module fault codes select the range for the fault code you just identified and click Display Help Topics RSLogix 5000 Online Help x Contents Index Find 1 Type the first few letters of the word you re looking for Module Faults 16 0300 16 03FF 2 Click the index entry you want and then click Display module fault Module Faults 160001 16 00ff 16 0100 16 01ff 16 0200 16 02FF 16 0fd03 16 fd05 16 fe02 16 feOc 16 ff00 16 ff0e module features 1756 analog 1 0 1756 specialty 1 0 1756 CNB 1756 CNBR 1756 DHRIO 1756 DNB 1756 ENET A Eime Cancel 11 Follow the recommendations for your fault code Rockwell Automation Publication CNET UM001D EN P June 2011 69 Chapter4 Control 1 0 Notes 70 Rockwell Automation Publication CNET UM001D EN P June 2011 Chapter 5 Terminology Produce and Consume Tags interlock controllers This chapter explains how to interlock produce and consume tags controllers via a ControlNet network Topic Page Teminloy S oo Set Up the Hardware 72 Determine Connections for Produced and Consumed Tags 73 Organize Tags for Produced or Consumed Data 75 Adjust for Bandwidth Limitations 76 Produce a Tag 77 Consume a Tag 79 Interlocking controllers is the preferred meth
73. nput O Output C Configuration S Status MemberName Specific data from the 1 0 module depending on the type of data the module can store For example Data and Fault are possible fields of data for an I O module Data is the common name for values that are sent to or received from I O points SubMemberName Specific data related to a MemberName Bit optional Specific point on the I O module depending on the size of the 1 0 module 0 31 for a 32 point module Rockwell Automation Publication CNET UM001D EN P June 2011 65 Chapter 4 66 Control 1 0 I O information is available in the Controller Tags portion of your RSLogix 5000 project You can monitor or edit the tags To access distributed I O within the Controller Organizer of RSLogix 5000 software double click Controller Tags amp Controller PLSSampleProject aoe E Controller tault Handler The Controller Tags dialog box appears Scope ControlNet controller z Show hwa Sort TagName E Tag Name Value Force Mask Style Ge us 0 Decimal 0 Decimal 0 Decimal Remote_FLEX_CNET_adapter 1 C 5SData 2 0000_000 Binary Remote_FLEX_CNET_adapter 1 C SSData 0 0 Decimal Remote_FLEX_CNET_adapter 1 C SSData 1 0 Decimal Remote_FLEX_CNET_adapter 1 C SSData 2 0 Decimal Remote_FLEX_CNET_adapter 1 C SSData 3 0 Decimal Rem
74. nt or software described in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations WARNING Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss ATTENTION Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you identify a hazard avoid a hazard and recognize the consequence SHOCK HAZARD Labels may be on or inside the equipment for example a drive or motor to alert people that dangerous voltage may be present BURN HAZARD Labels may be on or inside the equipment for example a drive or motor to alert people that surfaces may reach dangerous temperatures PP gt gt IMPORTANT Identifies information that is critical for successful application and understanding of the product Allen Bradley ArmorP OINT CompactLogix ControlLogix Data Highway Plus DriveLogix FlexLogix FLEX Ex FLEX I O Logix 5000 PanelView PanelView Plus POINT I O PowerFlex 700S Rockwell Software Rockwell Automation RSLinx RSLinx Classic RSLogix RSLogix 5000 RSNetWorx RSNetWorx for ControlNet RSView SoftLogi
75. od of sharing scheduled data between controllers when data needs to be delivered regularly quickly and at a set interval A Logix5000 controller lets you produce broadcast and consume receive system shared tags Term Definition Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume receive the data A produced tag sends its data to one or more consumed tags consumers without using logic The produced tag sends its data at the RPI of the fastest consuming tag Consumed tag A tag that receives a produced tag s data The data type of the consumed tag must match the data type including any array dimensions of the produced tag The RPI of the fastest consumed tag determines the rate at which the produced tag is produced For two controllers to share produced or consumed tags they must reside on the same ControlNet network Rockwell Automation Publication CNET UM001D EN P June 2011 n Chapter 5 Produce and Consume Tags interlock controllers Set Up the Hardware In this example the controller in the first chassis produces a tag that is consumed by the controller in the second chassis Figure 11 Interlocking Controllers Example EIEN Data f 1756 EN2T 1756 CN2R ControlNet Network o9 Item Description 1 Chassis 1 can contain any of these combina
76. of INTs with an combinations of both even number of elements such as INT 2 Only one REAL value Use the REAL data type in than one REAL Create a user defined data type that contains an array of REALs value Consume Integers Create a user defined data type that contains these members Data type Description DINT Status BIT 0 e 0 PLC5 in PROG mode e 1PLC5 in RUN mode INT x where x is the output size of the data from the PLC 5C controller If you are consuming only one INT omit x Data produced by a PLC 5C controller Use the highest permissible RPI for your application If the controller consumes the tag over a ControlNet network use a binary m ultiple of the ControlNet network update time NUT For example if the NUT is 5 ms use an RPI of 5 10 20 or 40 ms Combine data that goes to the same controller If you are producing several tags for the same controller group the data in th e To reduce the number of connections group the data into one or more use ese ways r defined data types e To conserve network bandwidth group the data according to similar upda e intervals Rockwell Automation Publication CNET UM001D EN P June 2011 75 Chapter 5 Produce and Consume Tags interlock controllers Adjust for Bandwidth Limitations Table 20 Tag Adjustments When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network e As
77. of attributes unique to each product revision When a Logix5000 controller begins communicating with a module this set of keying attributes is considered Table 8 Keying Attributes Attribute Description Vendor The manufacturer of the module for example Rockwell Automation Allen Bradley Product Type The general type of the module for example communication adapter AC drive or digital 1 0 Product Code The specific type of module generally represented by its catalog number for example 1756 IB161 Major Revision A number that represents the functional capabilities and data exchange formats of the module Typically although not always a later that is higher Major Revision supports at least all of the data formats supported by an earlier that is lower Major Revision of the same catalog number and possibly additional ones Minor Revision A number that indicates the module s specific firmware revision Minor Revisions typically do not impact data compatibility but may indicate performance or behavior improvement You can find revision information on the General tab of a module s Properties dialog box Figure 9 General Tab Revision fiz 1 4 Electronic Keying Compatible Keying v Compatible Keying Disable Keying Exact Match IMPORTANT Changing electronic keying selections online may cause the 1 0 communication connection to the module to be disrupted and may result in a loss of data
78. of the following e The ControlNet communication modules are connected to a scheduled ControlNet network e All wiring and cabling are properly connected e The communication driver is configured for the programming workstation TIP If you are sharing tags only between ControlLogix controllers the controllers are not controlling any I O modules You can set the communication format of the 1756 CN2 1756 CN2R 1756 CNB or 1756 CNBR modules in the remote chassis to None This limits connection usage and network traffic Determine Connections for Logix controllers can produce broadcast and consume receive system shared Produced and Consumed tags that are sent and received via the ControlNet communication module Each Tags produced and consumed tag requires connections Table 17 Tag Type and Connections Tag Type Required Connections Produced The produced tag requires two connections The producing controller must have one connection for the produced tag and the first consumer and one connection for each additional consumer heartbeat The heartbeat is a small scheduled packet the consumer sends to indicate that it is getting the produced data As you increase the number of controllers that can consume a produced tag you also reduce the number of available controller connections for other operations such as communication and 1 0 Consumed Each consumed tag requires one connection for the controller that is consuming the t
79. olNet network capacity 24 connect a computer 25 schedule 18 44 54 topology 21 23 D data types 71 75 78 81 distributed 1 0 access data 65 67 add to RSLogix 5000 project 63 communication formats 65 download RSLogix 5000 project 36 E electronic keying 37 43 enter message logic 86 88 1 0 control 55 69 rack optimized connections 60 scheduled 19 interlocking controllers See produced tags or consumed tags K keeper network 19 keying electronic 37 43 L local ControlNet module 30 32 Logix5000 controller consumed tags 79 81 direct or rack optimized connections 58 local ControlNet module 30 32 produced tags 77 79 remote ControlNet module 33 35 media configuration 48 52 message instructions cache message connections 86 configure 88 89 guidelines 85 staggering messages 90 message logic 86 88 network keeper 19 network update time 15 18 21 35 75 76 Rockwell Automation Publication CNET UM001D EN P June 2011 97 Index 98 NUT See network update time 0 ownership types 61 62 P PanelView terminal connection to Logix5000 controller 93 controller data 96 hardware setup 92 RSLogix 5000 software setup 94 96 select 95 peer to peer messaging 83 produced tags defined 71 determine connections 73 guidelines 75 Logix5000 controller 77 79 organize tag data 75 rack optimized communication format 60 remote ControlNet module 33 35 requested packet interval 17 56 RPI See reques
80. on of the system leave the checkbox cleared Major Fault On Controller If Connection Fails While In Run Mode or connection If you want the controller to produce a major fault if the connection to the local communication module fails in Run mode check the checkbox If you want the controller to continue operating if the connection to the local communication module fails in Run mode leave the checkbox cleared Use ladder logic to monitor the Use Scheduled Connection over ControlNet Note the following must be scheduled Check the box if you want to explicitly schedule the network connection e The checkbox is enabled when the connection for the module crosses ControlNet and the module supports unscheduled connections e The checkbox is checked and disabled when the connection to the module crosses ControlNet and the module does not support unscheduled connections and therefore e The checkbox is cleared and disabled when the connection to the module does not cross ControlNet or the connection crosses ControlNet but does not need to be scheduled Rockwell Automation Publication CNET UM001D EN P June 2011 35 Chapter3 Configure a ControlNet Module E Module Properties ControlNet_Module 3 1756 CN2R B 20 1 General Connection Module Info Backplane Requested Packet Interval RPI 20 0 Sms 20 750 0 ms C Inhibit Module C Major Fault On Controller If Connection Fails While in Run
81. on properties in the next step New Module Type Vendor Parent Name Description Comm Format Revision 1756 CN2R B 1756 ControlNet Bridge Allen Bradley ControlNet_Module Rack Optimization v 20 v i Open Module Properties Communication Format Node Chassis Size Slot Electronic Keying Compatible Keying Cancel Help The communication format determines the following e What configuration options are available For example if the module uses None then you do not have to configure an RPI rate on the Module Properties dialog box e What type of data is transferred between the owner controller and I O connected via the communication module e What tags are generated when configuration is complete e The type of connection between the owner controller and the I O connected via the communication module 34 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 The communication format setting also affects the RPI rate Table 7 Communication Formats Communication Format Function Rack optimized The communication module creates a rack image and returns I O data in the rack image to the owner controller This option is available only for digital I O modules Remember that diagnostic I O modules will not return diagnostic data when you use this format Listen only rack optimized not availab
82. on with the 1 0 module Any break in the connection such as a module fault or the removal of a module while under power sets fault bits in the data area associated with the module Module Properties Local 1756 IB16 2 1 Type 1756 1B16 16 Point 10 31 2 DC Input Vendor Allen Bradley Parent Local Name Slot fi a A direct connection is any connection E that does not use the Rack ere ae Comm Format input Data Optimization communication format Revision 2 fi 4 Electronic Keying Compatible Module Description Rack optimized connection 58 Digital 1 0 modules only A rack optimized connection consolidates connection usage between the controller and all the digital 1 0 modules in the chassis or DIN rail Instead of a direct connection for each I O module the entire chassis or DIN rail has one connection Anytime a remote chassis houses 1 0 modules that use rack optimized connections the remote ControlNet communication module connecting these modules to their owner controller must also use a rack optimized connection However you can use both direct and rack optimized connections to the same remote chassis For example if your remote chassis houses six digital 1 0 modules and your application requires direct connections for three and rack optimized connections for the others you can choose direct connections for the first three and rack optimized connections for the second three In this case even though you
83. ork For example a network that runs with a five ms NUT cannot send scheduled data at a rate faster than five ms It can however send data at a slower rate The minimum NUT you can specify is two ms The NUT is divided into a three part structure Table 4 NUT Structure Parts of NUT Scheduled Functions On a sequential rotating basis every scheduled node can transmit data once per NUT Time critical information is sent during this part of the interval Unscheduled All nodes transmit on a sequential rotating basis the rotation repeating itself until the time allotted for this portion is used up The number of scheduled transmissions determines the time available for unscheduled transmissions On a ControlNet network at least one node can transmit unscheduled data every NUT Information that can be delivered without time constraints is sent during this part of the interval Maintenance The node with the lowest address transmits information to keep the other nodes synchronized This time is automatically subtracted from your NUT However the time required for network maintenance is brief microseconds when compared to that used for the scheduled and unscheduled portions of the NUT Figure 4 NUT Structure Item 1 a wo _P Description Boundary moves according to scheduled traffic load Unscheduled traffic Network maintenance Scheduled traffic Each device transmits onl
84. ork control system Topic Page Use ControlNet Communication Modules in a Control System 9 Bridge Across Networks 11 Exchange Information on a ControlNet Network 14 ControlNet Network Capacity and Topology 21 You can fit various ControlNet modules into your control system Figure 1 on page 10 shows the following The controllers produce and consume tags among themselves e The controllers initiate MSG instructions that send receive data or configure devices e The computer uploads and downloads projects to the controllers e The computer configures devices on the ControlNet network and configures the network itself Rockwell Automation Publication CNET UM001D EN P June 2011 9 Chapter 1 ControlNet Overview Figure 1 ControlNet Modules and the Control System Overview 0 ozm ap a es Control Net Network Item co ik Description Personal computer running SoftLogix5800 controller with 1784 PCICS card 1756 CNB module as an adapter with 1756 1 0 modules PowerFlex 700S drive 1794 ACN15 adapter with 1794 I O modules 1734 ACNR adapter with 1734 1 0 modules PanelView terminal CompactLogix 1769 L35CR controller with local 1769 1 0 modules o
85. ot fi fe Input Data e fi 4 Electronic Keying Compatible Modul Listen only connection An 1 0 connection where another controller provides the configuration data for the 1 0 module A controller using a listen only connection only monitors the module It does not write configuration data and can maintain a connection to the I O module only when the owner controller is actively controlling the 1 0 module Module Properties Local 1756 IB16 2 1 Type Vendor Parent Name Description Listen only Connection Comm Format Revision 1756 1B16 16 Point 10 31 2 DC Input Allen Bradley Local 3 Listen Only Input Data e fi a Electronic Keying Compatible Modul Rockwell Automation Publication CNET UM001D EN P June 2011 61 Chapter4 Control 1 0 Table 13 Module Ownership Module Type Input module Controller Does not own the module Desired Function p Choose the Type of Ownership for a Module Required Connection Type Owner such as not listen only Owns the module Maintain communication with the module if it loses communication with the other controller Owner such as not listen only Use the same configuration as the other owner controller Stop communication with the module if it loses communication with the other controller Listen only Output module Does not own the module p Owner such as not listen only Owns t
86. ote_FLEX_CNET_adapter 1 C SSData 4 0 Decimal Remote_FLEX_CNET_adapter 1 C SSData 5 0 Decimal _ HRemote_FLEX_CNET_adapter 1 C 5SData 6 0 Decimal _ HRemote_FLEX_CNET_adapter 1 C 5SData 7 o Decimal m Remote_FLEX_CNET_adapter 1 C SSData 8 0 Decimal j Remote_FLEX_CNET_adapter 1 C SSData 9 0 Decimal 4 gt Monitor Tags CE This example contains a tag named Remote FLEX CNET _adapter 1 C Filter_0 Address Variable Definition Location Remote_FLEX_CNET_adapter SlotNumber 1 Type Configuration MemberName Filter _0 Rockwell Automation Publication CNET UM001D EN P June 2011 Control 1 0 Chapter 4 This example shows an I O tree configured with a remote FLEX I O adapter and two remote FLEX I O modules EXAMPLE pores amp 1756 Backplane 1756 410 S 0 1756 CN2R B ControlNet_Module Ses ControlNet i 1 1756 CN2R B ControlNet_Module 4 2 1756 CN2R B Remote_Module amp 3 1794 ACNR15 D FLEX_Adapter 4 FlexBus amp 1 1794 1416 4 Input_Module amp 2 1794 0B16D 4 Output_Module fa 3 1756 L73 ControlNet_Controller Table 16 Example Tag Names Example Example Module Example Tag Names Created by Tag RSLogix 5000 Software 1 Example 1 Remote 1794 ACN15 FLEX_adapter adapter FLEX_adapter FLEX_adapter SlotStatusBits FLEX_adapter Data FLEX_adapter 0 FLEX_adapter 0 Data 2 Example 2 Remote 1794 IA16 FLEX_adapter 1 C Input_module in slot
87. other uses such as produced or consumed tags Separate the tag into two or more smaller tags 1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical 2 Assign a different RPI to each tag Create logic to transfer the data in smaller sections packets For information on how to do this see the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 76 Rockwell Automation Publication CNET UM001D EN P June 2011 Produce and Consume Tags interlock controllers Chapter 5 Produce a Tag A Logix5000 controller can produce only controller scoped user created tags in the local controller s tag structure Logix5000 controllers cannot produce I O tags or tags aliased to I O tags To produce a tag perform this procedure 1 Open the RSLogix 5000 project containing the tag you want to produce IMPORTANT You can create produced tags only when your RSLogix 5000 project is offline 2 Within the Controller Organizer of RSLogix 5000 software right click Controller Tags and choose Edit Tags ft RSLogix 5000 ControlNet 1769 L35CR 19 11 File Edit View Search Logic Communications Tools Windo ae amp e Offline fl E RUN No Forces Controller Organizer Controller ControlNet Controller Tags GB Power Up Hand sazIUeBAQ 43 04qU07 Controller Fault 3 N
88. pe CIP Data Table Write Source Tag First element of the controller scoped tag in this controller that contains the data Number of Elements Number of elements to transfer Destination Element First element of the tag for the data in the other controller 6 Click the Communication tab Message Configuration message Configuration Communication Tag Pan T2 IEZ Communication Method Connected C Cache Connections e O Enable Enable Waiting Start O Done Done Length 0 Error Code Extended Error Code C Timed Out Error Path Error Text OK Cancel Apply Help 7 Specify the path of the module for which you sent the message instruction to the I O configuration tree e Ifthe module has been added click Browse to the choose the path e Ifthe module has not been added type the path in the Path field 8 Click OK Rockwell Automation Publication CNET UM001D EN P June 2011 89 Chapter6 Messaging Stagger the Messages 90 As you add messages to your project you may have to coordinate the execution of the messages To avoid errors and assure that each message is processed follow these rules Rule 1 Enable no more than 16 messages at one time including block transfers Rule 2 Enable no more than 10 of these types of messages at one time e CIP data table reads or writes that are not cached e CIP generic e PLC 2 PLC 3 PLC 5 or SLC all ty
89. pes e Block transfer reads or writes that are not cached If the number of messages in your application exceeds rules 1 and 2 then stagger the execution of your messages Here are some options e Send each message in sequence e Send the messages in groups that are within the limits of rules 1 and 2 e Program a message to communicate with multiple devices Rockwell Automation Publication CNET UM001D EN P June 2011 Chapter 7 Communicate with PanelView Terminals This chapter explains how a controller uses a ControlNet communication module to communicate with PanelView software products over a ControlNet network Topic Page Set Up the Hardware 92 Determine Connections to PanelView Terminals 93 Add a PanelView Terminal 94 Organize Controller Data for a PanelView Terminal 96 Rockwell Automation Publication CNET UM001D EN P June 2011 91 Chapter 7 Communicate with PanelView Terminals Set Up the Hardware In this example the controller in the local chassis shares data with an HMI application on a ControlNet network This application could be running any of these e PanelView terminal e PanelView Plus terminal e Workstation running RSView 32 software e Workstation running an RSView Enterprise application such as RSView Machine Edition software or RSView Supervisory Edition software Figure 14 Example of Communication with PanelView and RSView Products O mmm S El
90. pplication is online go offline 2 In RSLogix 5000 software right click I O Configuration and choose New Module Controller S E Controller ControlNet_Controller Controller Tags Controller Fault Handler Power Up Handler amp amp Tasks Maintask E7 amp MainProgram EE Unscheduled Programs Phases 5 6 Motion Groups Ungrouped Axes Add On Instructions amp Data Types i User Defined E oa Strings iG Add On Defined B oe Predefined ER Module Defined Gi Trends Ege Configuration 1756 Baca S f 0 1756 ds Contry 3 From the Select Module dialog box select a local ControlNet communication module type and click OK E Select Module E Communications 56AMXN DCSNet Interface llen Bradl 1756 ControlNet Bridge llen Bradl 7 1756 ControlNet Bridge Allen Bradley 1756 CN 1756 ControlNet Bridge llen Brad 1756 CN2R B 1756 ControlNet Bridge llen Bradl 1756 CNB A 1756 ControlNet Bridge llen Bradl 1756 CNB B 1756 ControlNet Bridge llen Bradl 1756 CNB D 1756 ControlNet Bridge llen Bradl 1756 CNB E 1756 ControlNet Bridge llen Bradl 1756 CNBR A 1756 ControlNet Bridge Redundant Media llen Brad 1756 CNBR B 1756 ControlNet Bridge Redundant Media llen Bradl 1756 CNBR D 1756 ControlNet Bridge Redundant Media llen Bradl gt Add Favorite By Category i By Vendor Favorites Cancel Help j Logix5000 Controller Local ControlNet Communication Modules 1768 CompactLogix 1768
91. pting to communicate with a module Other attributes such as data size and format are considered and must be acceptable before I O communication is established With Disabled Keying I O communication may occur with a module other than the type specified in the I O Configuration tree with unpredictable results We generally do not recommend using Disabled Keying ATTENTION Be extremely cautious when using Disabled Keying A if used incorrectly this option can lead to personal injury or death property damage or economic loss Rockwell Automation Publication CNET UM001D EN P June 2011 4 Chapter3 Configure a ControlNet Module If you use Disabled Keying you must take full responsibility for understanding whether the module being used can fulfill the functional requirements of the application EXAMPLE In the following scenario Disable Keying prevents 1 0 communication The module configuration is for a 1756 IA16 digital input module The physical module is a 1756 IF16 analog input module In this case communication is prevented because the analog module rejects the data formats that the digital module configuration requests Module Configuration Vendor Allen Bradley Bee ne ens aaa hes Product Type Digital Input se SAE x Sl Module Catalog Number 1756 IA16 Major Revision 3 Minor Revision 1 Electronic Keying Disable Keying Open Module Properties Communication is preven
92. rmat with a Criteria for Use Remote ControlNet Communication Module None When all of the remote I O communicating with a controller via the remote ControlNet communication module use a Direct Connection communication format When the connection is used for scheduled peer interlocking When 1 0 will be mostly direct connections When multiple controllers control the outputs in the chassis Rack optimized 3 When some or all of the remote 1 0 communicating with a controller via the remote ControlNet communication module use a rack optimized communication format To minimize ControlNet network bandwidth when using large volume of digital 1 0 If only one controller will control the 1 0 Rack optimized Listen only When some or all of the remote 1 0 communicating with a controller via the remote ControlNet communication module use a rack optimized communication format I O module type determines the available communication formats Table 10 Communication Format for Module Types 1 0 Module Type Desired Connection Required Communication Format Digital module Rack optimized connection Rack optimized electronic fuses or Direct connection or to use specialty features of The data your controller needs from the I O module For example if your the module such as diagnostics timestamps or application uses a 1756 IA161 module in a remote chassis that must provide timestamped input data choose the CST Ti
93. rties Cancel Help Communication is prevented Physical Module Vendor Allen Bradley Product Type Digital Input Module Catalog Number 1756 IB16D g Major Revision 3 F i Minor Revision 2 o eo a oa IMPORTANT Changing electronic keying selections online may cause the 1 0 Communication connection to the module to be disrupted and may result in a loss of data Compatible Keying Compatible Keying indicates that the module determines whether to accept or reject communication Different module families communication adapters and module types implement the compatibility check differently based on the family capabilities and on prior knowledge of compatible products Compatible Keying is the default setting Compatible Keying allows the physical module to accept the key of the module configured in the software provided that the configured module is one the physical module is capable of emulating The exact level of emulation required is product and revision specific Rockwell Automation Publication CNET UM001D EN P June 2011 39 Chapter 3 Configure a ControlNet Module 40 With Compatible Keying you can replace a module of a certain Major Revision with one of the same catalog number and the same or later that is higher Major Revision In some cases the selection makes it possible to use a replacement that is a different catalog number than the original For example you can replace a 1756 CNB
94. software and created a controller project you can add ControlNet communication modules A local ControlNet module is a module that resides in the same chassis as the controller IMPORTANT When you create a new RSLogix 5000 project with the CompactLogix 1769 L32C or 1769 L35CR controller the Controller Organizer creates a ControlNet port in the local chassis In this case you do not need to add a separate local communication module To add a local ControlNet module follow this procedure 1 In RSLogix 5000 software right click I O configuration and choose New Module Sc canteens M 5 New Hyla a 2 From the Select Module Type dialog box expand Communications choose the local ControlNet communication module and then click OK E Select Module Module Description endor Communications a 56AMXN DCSNet Interface en Bradley 1756 CN2 A 1756 ControlNet Bridge len Bradley 1756 CN2 B 1756 ControlNet Bridge len Bradley 1756 CN2R A 1756 ControlNet Bridge len Bradley 1756 CN2R B 1756 ControlNet Bridge llen Bradley i 1756 CNB A 1756 ControlNet Bridge len Bradley 1756 CNB B 1756 ControlNet Bridge llen Bradley len Bradley len Bradley llen Bradley len Bradley len Bradley 1756 CNB D 1756 ControlNet Bridge 1756 CNB E 1756 ControlNet Bridge 1756 CNBR A 1756 ControlNet Bridge Redundant Media 1756 CNBR B 1756 ControlNet Bridge Redundant Media 1756 CNBR D 1756 ControlNet Bridge Redundant Media rPrREEPEEPEERErEE LE
95. t supported Supported Unscheduled unconnected Supported Not supported A Logix controller supports up to 40 outgoing and 3 incoming unconnected buffers This limited number of incoming unconnected buffers limits how many PanelView Standard terminals can request data from a controller When you use Panel View terminals with Logix5000 controllers over a ControlNet network remember these limitations e A maximum of four PanelView Standard terminals can request data from a Logix5000 controller The number of PanelView Plus terminals that can request data from a Logix5000 controller is dependent on the number of available unconnected buffers in the Logix5000 controller A typical PanelView Plus application uses 5 unconnected buffers in a Logix5000 controller With 32 unconnected buffers available at any time in a Logix5000 controller a maximum of 6 PanelView Plus terminals can request data from a Logix5000 controller Keep in mind however that if 6 PanelView Plus terminals are requesting data from a single Logix5000 controller few unconnected buffers remain for anything else For scheduled connected communication you must add the PanelView or PanelView Plus terminal to the I O configuration tree for the controller project Rockwell Automation Publication CNET UM001D EN P June 2011 93 Chapter 7 Communicate with PanelView Terminals Add a PanelView Terminal To adda PanelView terminal perform this procedure 1 Ifyour a
96. ted Physical Module Vendor Allen Bradley Product Type Analog Input Module Catalog Number 1756 IF16 Major Revision 3 Minor Revision 2 42 Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 EXAMPLE In the following scenario Disable Keying allows 1 0 communication The module configuration is for a 1756 IA16 digital input module The physical module is a 1756 IB16 digital input module In this case communication is allowed because the two digital modules share common data formats Module Configuration Vendor Allen Bradley Pi ames oe oe Product Type Digital Input SS ENEN Ge Module pe e or at Input Data Catalog Number 1756 IA16 a AL ere Major Revision 2 Minor Revision 1 Open Module Properties Communication is allowed Physical Module Vendor Allen Bradley Product Type Digital Input Major Revision 3 Minor Revision 2 Module f E Catalog Number 1756 IB16 IMPORTANT Changing electronic keying selections online may cause the 1 0 communication connection to the module to be disrupted and may result in a loss of data Rockwell Automation Publication CNET UM001D EN P June 2011 43 Chapter3 Configure a ControlNet Module Use RSNetWorx for ControlNet Software You must use RSNetWorx for ControlNet
97. ted packet interval RSLinx Classic software 26 RSLogix 5000 software add distibuted 0 63 add PanelView terminal 94 96 communication format 34 configure ControlNet module 29 35 create consumed tag 79 81 create produced tag 77 79 download project 36 RSNetWorx for ControlNet software configure network keeper 19 schedule network 44 54 RSView software 92 S schedule ControlNet network 18 44 54 scheduled 1 0 19 scheduled maximum node address 21 select communication driver 26 communication format 57 65 communication path 50 local communication module 30 94 PanelView terminal 95 remote communication module 33 set communication format 35 network schedule parameters 47 51 requested packet interval 56 scheduled maximum node address 21 unscheduled maximum node address 21 SMAX See scheduled maximum node address staggering messages in RSLogix 5000 90 T tags See produced tags or consumed tags terminal connections PanelView 93 topology of ControlNet network 21 23 U UMAX See unscheduled maximum node address unscheduled maximum node address 21 V validate connections 68 Rockwell Automation Publication CNET UM001D EN P June 2011 Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products At http www rockwellautomation com support you can find technical manuals a knowledge base of FAQs technical and application notes sample
98. the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time NUT e A ControlNet node can transmit approximately 500 bytes of scheduled data in a single NUT Depending on system size your ControlNet network may lack the bandwidth for large tags If a tag is too large for your ControlNet network make one or more of these adjustments Adjustment Increase the requested packet interval RPI of your connections This is the recommended method Description At higher RPls connections can take turns sending data during an update period Reduce your network update time NUT Ata faster NUT fewer connections have to share an update period For a ControlNet 1756 CN2 1756 CN2R 1756 CNB or 1756 CNBR bridge module in a remote chassis choose the most efficient communication format for that chassis Then choose this communication format for the remote 1756 CN2 or 1756 CNB module Are most of the modules in the chassis nondiagnostic digital 1 0 modules Yes No Rack optimization None The rack optimization format uses an additional eight bytes for each slot in its chassis Analog modules or modules that are sending or receiving diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting None frees up the eight bytes per slot for
99. tions e 1756 ControlLogix controller with a 1756 CN2 or 1756 CN2R communication module in the chassis e 1756 ControlLogix controller with a 1756 CNB or 1756 CNBR communication module in the chassis e 1768 L43 CompactLogix controller with a 1768 CNB or 1768 CNBR communication module in the chassis e 1769 L32C or 1769 L35CR CompactLogix controller e 1789 SoftLogix controller with a 1784 PCICS communication card e PowerFlex 700S with DriveLogix controller and a 1788 CNx ControlNet communication card e Non Logix5000 controller or other device connected to ControlNet via a ControlNet scanner card 2 Chassis 2 can contain any of these combinations e 1756 ControlLogix controller with a 1756 CN2 or 1756 CN2R communication module in the chassis e 1756 ControlLogix controller with a 1756 CNB or 1756 CNBR communication module in the chassis e 1768 L43 CompactLogix controller with a 1768 CNB or 1768 CNBR communication module in the chassis e 1769 L32C or 1769 L35CR CompactLogix controller e 1789 SoftLogix controller with a 1784 PCICS communication card e PowerFlex 700S with DriveLogix controller and a 1788 CNx ControlNet communication card e Non Logix5000 controller or other device connected to ControlNet via a ControlNet scanner card 3 Programming termina 72 Rockwell Automation Publication CNET UM001D EN P June 2011 Produce and Consume Tags interlock controllers Chapter 5 Make sure
100. ublication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 Add and Configure 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 chassis separate from the controller To add a remote ControlNet module perform this procedure 1 In RSLogix 5000 software right click the local ControlNet communication module and choose New Module 5 8 1 0 Configuration 1756 Backplane 1756 47 fa 0 1756 L63 CNET_messaging 4 1 1756 CNB D LocalCNB 2 ontrolNet_ Module amp ControlNet a New Module 2 From the Select Module Type dialog box expand Communications select a remote ControlNet communication module and then click OK You can connect any remote ControlNet communication module to a local ControlNet communication module E Select Module Communications 1440 ACNR A 1440 ControlNet Adapter Redundant Media Allen Bradley 1734 ACNR 1734 ControlNet Adapter Redundant Media Allen Bradley 1738 ACNR 1738 ControlNet Adapter Redundant Media Allen Bradley 1756 CN2 4 1756 ControlNet Bridge Allen Bradley 1756 CN2 B 1756 ControlNet Bridge Allen Bradley 1756 CN2R A 1756 ControlNet Bridge Allen Bradley 1756 CN2R B 1756 ControlNet Bridge Allen Bradley 1756 CNB A 1756 ControlNet Bridge Allen Bradley 1756 CNB B 1756 ControlNet Bridge Alle
101. unding Provides general guidelines for installing a Rockwell Guidelines publication 1770 4 1 Automation industrial system Product Certifications website Provides declarations of conformity certificates and http www ab com other certification details You can view or download publications at http www rockwellautomation com literature To order paper copies of technical documentation contact your local Allen Bradley distributor or Rockwell Automation sales representative Rockwell Automation Publication CNET UMO001D EN P June 2011 7 Preface Notes 8 Rockwell Automation Publication CNET UM001D EN P June 2011 Use ControlNet Communication Modules in a Control System Chapter 1 ControlNet Overview The ControlNet network provides high speed transmission of time critical I O and interlocking data and messaging data This data transfer capability enhances I O performance and peer to peer communication in any system or application The ControlNet network is highly deterministic and repeatable and remains unaffected as devices are connected or disconnected from it This ensures dependable synchronized and coordinated real time performance The ControlNet network is most often used in these ways e As the default network for the ControlLogix platform e Asa backbone to multiple distributed DeviceNet networks e Asa peer interlocking network This chapter describes how you can use ControlNet modules in a netw
102. uring scheduled time RSNetWorx for ControlNet software sets this value We recommend that you do not change it Max Unscheduled Address time on a ControlNet unscheduled time RSLinx software The node with the highest network address that can use unscheduled ink Messaging data is transferred during Nodes set at addresses higher than the maximum unscheduled node do not communicate on the network For example they will not display in Media Redundancy Designates if the network uses media redundancy on any of the network communication modules Network Name Network schedule Network Parameters Media Configuration General Network Update Time ms I Max Scheduled Address 2 Max Unscheduled Address Current A user defined name for the network Media Redundancy Network Name _ Rockwell Automation Publication CNET UM001D EN P June 2011 51 Chapter 3 Configure a ControlNet Module 52 9 10 11 12 13 Click the Media Configuration tab modify the settings if needed and click OK Generally you can use the default media configuration Adjust the configuration if your network is longer or uses repeaters IMPORTANT Ifthe media configuration does not accurately represent the maximum propagation delay between any two nodes your network may experience errors Network schedule Network Parameters Media Configuration General Ava
103. ver Compact 1 0 modules that are local to the 1769 L32C and 1769 L35CR controllers are not accessible to other Logix5000 controllers 84 Rockwell Automation Publication CNET UM001D EN P June 2011 Messaging Chapter 6 Make sure of the following Guidelines for MSG Instructions Table 21 Guidelines for MSG Instructions Function For each MSG instruction create a control tag e The ControlNet modules are connected to a ControlNet network e All wiring and cabling are properly connected e The communication driver is configured for the programming workstation Follow these guidelines as you work with message instructions Guidelines Each MSG instruction requires its own control tag This tag contains control elements for messages such as DN and EN error codes and information to execute the message such as destination path and number of words to transfer e Data type MESSAGE Scope controller e The tag cannot be part of an array or a user defined data type Keep the source or destination data at the controller scope A MSG instruction can access only tags that are in the Controller Tags folder controller scope If your MSG is to a module that uses 16 bit integers use a buffer of INTs in the MSG and DINTs throughout the project If your message is to a module that uses 16 bit integers such as an SLC 500 controller and it transfers integers not REALs use a buffer of INTs in the message an
104. vices on the network by using RSLogix 5000 software and RSLinx software IMPORTANT To improve performance configure a ControlNet network with RSNetWorx for ControlNet software We recommend these settings e Set the Unscheduled Maximum Node Address UMAX equal to the highest node address on the network Leaving this parameter at the default value of 99 wastes bandwidth and reduces system performance e Set the Scheduled Maximum Node Address SMAX to a value three or four above the highest scheduled node address so you can expand the network in the future Also be aware that each skipped node will subtract a small amount of bandwidth from the network When planning a ControlNet network consider these factors e Topology e Number of nodes e Distances e Connections Topology A ControlNet network supports a variety of topologies including trunkline dropline star tree and ring redundancy In its simplest form a ControlNet network is a trunkline to which you connect nodes with a tap and a one meter dropline Rockwell Automation Publication CNET UM001D EN P June 2011 21 Chapter 1 ControlNet Overview Figure 5 Example ControlNet Network Trunkline Dropline Topology jooo Item Description 1 Trunkline 2 Node 3 Tap with dropline Figure 6 Example ControlNet Network Star Topology eee
105. w these guidelines to determine whether to cache a connection Message Execution Appropriate Action Repeated Cache the connection This keeps the connection open and optimizes message completion time Opening a connection during the execution of each message increases execution time Infrequent Do not cache the connection This closes the connection upon completion of the message freeing up that connection for other uses To send or receive data from a ControlNet module via a message you must program a MSG instruction in the local controller s logic If the target module is configured in the I O Configuration folder of the controller browse to choose the module or manually type the message path in the MSG instruction 86 Rockwell Automation Publication CNET UM001D EN P June 2011 Messaging Chapter 6 Add the ControlNet Modules and Remote Devices to the Local Controller s 1 0 Configuration Browse to choose the target device of a MSG instruction and add that remote device to the I O configuration folder of the local controller Within the I O configuration folder organize the local and remote devices into a hierarchy of tree branch and parent child Figure 13 1 0 Configuration Order for MSG Instruction Bll g l E Z m E Stas SHS SHAS ols B R BHE 1756 EN2T 1756 CN2R RSLogix 5000 My_Project 1756 L63 File Edit View Search Logic Communications Tools ajaja S ame AAT
106. x and TechConnect are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies Summary of Changes This document contains new and updated information Changes are designated by change bars in the outside margins Updated Information This document contains these changes Topic Chapter Added information about the 1788 CN2DN module Chapter 1 Added modules for a 1769 CompactLogix packaged controller system Chapter 1 Added information about the 1784 U2CN USB to ControlNet cable Chapter 2 Rockwell Automation Publication CNET UMO001D EN P June 2011 Summary of Changes Notes 4 Rockwell Automation Publication CNET UMO001D EN P June 2011 Preface ControlNet Overview Connect a Computer to the ControlNet Network Configure a ControlNet Module Table of Contents Additional Resources ca gal eh era insted BPD Dh ceahe EOS oe aioe aed SR 7 Chapter 1 Use ControlNet Communication Modules in a Control System 9 Bridge Across Networks tiacsusoisasad nd ties eeo eu eeraui aes 11 Exchange Information on a ControlNet Network 14 Network Update Time INU T a is i45 iyo aaah cheese 16 Requested Packet Interval RPU iucg oteini povneatseecaaneines 17 Actual Packet IntervalCAP ls eyeceeskouctvwekwe eee hay oh nau 17 Schedule the Network 23 55 as acacscanad Sarnddea den ae eae oes 18 Understand the Network Keeper c ciesacdiua
107. x 5000 software save the online project Rockwell Automation Publication CNET UM001D EN P June 2011 Configure a ControlNet Module Chapter 3 Reschedule a ControlNet Network that has Previously been Scheduled If you change a previously scheduled network you must reschedule the network to apply the changes For example if you add I O to an existing ControlNet network you must reschedule the network for the I O to become active To reschedule an already scheduled ControlNet network follow this procedure in RSNetWorx for ControlNet software 1 From the File menu choose Open lt Network schedule xc RSNetWorx for Cc File Edit View Network Device Diagnostics Te Ctrl N 2 From the Open dialog box select the ControlNet file that matches the existing network and click Open Look in Projects 0cm D Samples File name Network schedule xc Files of type ControlNet Files xc id Cancel 3 From the Network menu choose Online ControlNet RSNetWorx for ControlNet 4 Check Edits Enabled When you enable edits RSNetWorx for ControlNet software reads data in the ControlNet modules and builds a schedule for the network Network schedule xc RSNetWorx File Edit View Network Device Diagnost H amp BE e M Edits Enabled Current Network Update Time ms 5 00 5 Save the file Rockwell Automation Publication CNET UM001D EN P June 2011 53 Chapter 3
108. y once on AJ j N Start 16 Rockwell Automation Publication CNET UM001D EN P June 2011 ControlNet Overview Chapter 1 Requested Packet Interval RPI The RPI is the update rate specified for a particular piece of data on the network By using a rack optimized connection the RPI can specify the rate for an entire rack of I O With a direct connection the RPI can specify the rate for a particular module or peer to peer data When you add a module to the I O configuration of a controller you must configure the RPI specifying how often to produce data for that module For example if you specify an RPI of 50 ms every 50 ms the I O module sends its data to the controller or the controller sends its data to the I O module Set the RPI only as fast as needed by the application The RPI also determines the number of packets per second that the module will handle on a connection Each module has a limit of how many packets it can handle per second If you exceed this limit the module cannot open any more connections A faster RPI consumes more network bandwidth So to avoid wasting network bandwidth set the RPI only as fast as is necessary For example if your application uses a thermocouple module that has data change every 100 ms do not set the RPI for that node at 5 ms because the network bandwidth is used to transmit mostly old data IMPORTANT You cannot set the RPI to a rate faster than the NUT The network cannot send d

ControlNet Network Configuration User Manual, CNET-UM001D-EN-P

Contents

Download Pdf Manuals

Related Search

Related Contents