Allen-Bradley 1756-CNB User Manual
  1. Manuals
  2. Brands
  3. Allen-Bradley Manuals
  4. Control Systems
  5. ControlLogix 1756-CNB
  6. User manual

Allen-Bradley 1756-CNB User Manual

Controllogix redundancy system
Hide thumbs Also See for 1756-CNB:
Table of Contents

Quick Links

See also: Instruction and Installation Manual
ControlLogix
Redundancy
System
Catalog Numbers 1756-CNB/D/E,
1756-CNBR/D/E, 1756-ENBT,
1756-EWEB, 1756-L55,
1756-L55M12, 1756-L55M13,
1756-L55M14, 1756-L55M16,
1756-L55M22, 1756-L55M23,
1756-L55M24, 1756-L61, 1756-L62,
1756-L63, 1757-SRM
User Manual
Table of Contents
loading

Related Manuals for Allen-Bradley 1756-CNB

Summary of Contents for Allen-Bradley 1756-CNB

  • Page 1 ControlLogix Redundancy System Catalog Numbers 1756-CNB/D/E, 1756-CNBR/D/E, 1756-ENBT, 1756-EWEB, 1756-L55, 1756-L55M12, 1756-L55M13, 1756-L55M14, 1756-L55M16, 1756-L55M22, 1756-L55M23, 1756-L55M24, 1756-L61, 1756-L62, 1756-L63, 1757-SRM User Manual...
  • Page 2 Allen-Bradley, RSLogix, RSLogix 5000, RSView, RSLinxRSNetworx, DH+, PanelView, PanelViewPlus, Rockwell Automation, TechConnect, and VersaView are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies.
  • Page 3 Updated Information The document contains these changes. Topic Page Series E information for 1756-CNB and -CNBR modules Throughout manual Redundant System Firmware Combinations Revised Procedure for Setting the Minimum Value for the Watchdog Time Restrictions and Known Anomalies...
  • Page 4 Summary of Changes Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 5: Table Of Contents

    Table of Contents Preface Purpose of this Manual ......11 Who Should Use this Manual......11 When to Use This Manual .
  • Page 6 Table of Contents Install the Remote Chassis or Rails ....49 Configure EtherNet/IP Modules ..... . 50 Flash the Modules .
  • Page 7 Table of Contents Maintain Data Integrity During a Switchover ... . 82 Look for Array Shift Instructions ....84 Look for Scan-Dependent Logic .
  • Page 8 Table of Contents Check the Allocation of Unused Memory ....123 Adjust CPU Usage for a CNB Module ....123 Use RSLinx Software .
  • Page 9 Table of Contents Appendix C Attributes of the Redundancy Introduction ........169 Attributes of the Redundancy Object .
  • Page 10 Table of Contents Publication 1756-UM523F-EN-P - December 2006...

  • Page 11: Purpose Of This Manual

    Preface Purpose of this Manual This manual guides the design, development, and implementation of a redundancy system for a ControlLogix controller. Who Should Use this This manual is intended for those in these professions who design and develop applications that use ControlLogix controllers: Manual •...

  • Page 12: Related Documentation

    Related Documentation This table lists ControlLogix products and documentation that may be valuable as in programming an application. Catalog Number Title Publication Number 1756-CNB/D and ControlLogix ControlNet Bridge Module Installation Instructions 1756-IN571 1756-CNBR/D ControlLogix ControlNet Interface Module Release Notes 1756-RN587...

  • Page 13: Introduction

    Chapter ControlLogix Redundancy System Overview Introduction This chapter provides an overview of the ControlLogix redundancy system, including commonly used terms. It also answers some common questions about a ControlLogix redundancy system. Topic Page About the Main Parts of a Redundant System Firmware Combinations That Make Up a Redundant System Primary Chassis Switching from One Controller to Another...

  • Page 14: About The Main Parts Of A Redundant System

    Node Numbers ControlLogix Chassis that That are Lower Than Controls a Machine or Those of the Two Process 1756-CNB Modules in the Redundant Chassis Computer That is Connected to the Network Access Port of a Remote Node 43128 Firmware Combinations These firmware combinations make up revisions 15.56 and 15.57 of...

  • Page 15: Important Terms In A Redundant System

    ControlLogix Redundancy System Overview Important Terms in a Redundancy requires no additional programming and is transparent to any devices connected over an EtherNet/IP or ControlNet network. Redundant System Redundancy uses 1757-SRM modules to maintain communication between the pair of redundant chassis. In a redundant system, these terms describe the relationship between the two redundant chassis.

  • Page 16: Network Access Port

    ControlLogix Redundancy System Overview Network Access Port To connect a device to the network access port (NAP) of a 1756-CNB/D/E or 1756-CNBR/D/E module, use an NAP that is outside of a redundant chassis. Use of the Network Access Port (NAP)
  • Page 17 ControlLogix Redundancy System Overview Controller Communication Terms Term Description Crossload The transfer of any or all of the contents of the primary controller to the secondary controller. This could be updated tag values, force values, online edits, or any other information about the project.

  • Page 18: Making Online Edits

    ControlLogix Redundancy System Overview Making Online Edits Online edits automatically crossload to the secondary controller. They become inactive if a switchover happens before you assemble them into the project. This stops a mistake from faulting both the old and new primary controllers. Suppose you test an online edit and it causes the controller to fault.

  • Page 19: Controlnet Network

    ControlLogix Redundancy System Overview ControlNet Network Set each pair of CNB modules to the same node number. Primary Secondary Chassis Chassis CNB modules in the primary chassis CNB modules swap node numbers. use the node number to which they are set. Switchover Secondary Primary...

  • Page 20: Ethernet/Ip Network

    ControlLogix Redundancy System Overview EtherNet/IP Network Set both EtherNet/IP modules to the SAME IP address. Port Configuration Port Configuration Primary Secondary Chassis Chassis 10.10.10. 10.10.10. An EtherNet/IP module in the primary An EtherNet/IP module in the chassis uses the IP address to which secondary chassis uses the IP address it is set.

  • Page 21: Quick Start Checklists

    ControlLogix Redundancy System Overview Quick Start Checklists These checklists provide a summary of the criteria for a successful ControlLogix redundancy system. See the remaining chapters for more information on each parameter. System Layout Parameter Criteria Page • ControlNet networks are the primary networks for the system. ControlNet Networks 28, 31 •...
  • Page 22 • Same type of controller throughout the chassis. • Enough memory for 2 copies of all data. • 7 connections for redundancy. ControlNet Modules 1756-CNB/D/E or 1756-CNBR/D/E module or modules: 29, 107, • CPU usage ≤ 75%. • CNB modules have the same keeper information.
  • Page 23 ControlLogix Redundancy System Overview Redundant Chassis Configuration (Continued) Parameter Criteria Page EtherNet/IP Modules 1756-ENBT or 1756-EWEB modules: 29, 38 • Which modules do you want to use? • If 1756-ENBT, catalog revision greater than or equal to E01 (E01, E02, …, F01). See the label on the side of the module or its box.
  • Page 24 ControlLogix Redundancy System Overview RSLogix5000 Project Parameter Criteria Page Number of Projects Only one RSLogix 5000 project for the pair of redundant controllers. The project automatically crossloads to the secondary controller when the secondary controller synchronizes with the primary controller. •...
  • Page 25 ControlLogix Redundancy System Overview Operator Interface Terminals Parameter Operator Interfaces Criteria Page EtherNet/IP Network PanelView Standard terminal Same as a nonredundant system 28, 32, 38 • PanelView Plus terminal • Use RSLinx Enterprise software revision 3.0 or later. • VersaView industrial computer running a •...
  • Page 26 ControlLogix Redundancy System Overview Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 27: Introduction

    Chapter Design the System Introduction This chapter explains how to design a redundancy system for a ControlLogix controller. Topic Page Laying Out the System Placement of a Pair of Redundant Chassis Placement of the I/O Placement of Operator Interface Terminals Additional Redundant Components Checking Connection Requirements Planning a ControlNet Network...

  • Page 28: Laying Out The System

    Design the System Laying Out the System ControlLogix Redundancy Requirements and Recommendations Use separate networks for unscheduled and scheduled Unscheduled Communication communication. EtherNet/IP ControlNet • For unscheduled communication (HMI, workstations, message instructions), use either an EtherNet/IP or a ControlNet network. •...
  • Page 29 Design the System ControlLogix Redundancy Requirements and Recommendations (Continued) 1756-ENBT or 1756-EWEB modules: 1756-CNB/D/E or 1756-CNBR/D/E module or modules: • 1- 2 in each redundant chassis. • ≤ 5 total communication modules (CNBs and ENBTs) in each • 1-5 in each redundant chassis.

  • Page 30: Placement Of A Pair Of Redundant Chassis

    Design the System Placement of a Pair of With the standard redundancy module cables, a pair of redundant chassis (primary and secondary) can function up to 100 m (300 ft) Redundant Chassis apart. Redundant Chassis Placement • Redundant No Other Modules •...

  • Page 31: Placement Of The I/O

    Design the System Placement of the I/O In a ControlLogix redundancy system, place all I/O in only these locations: • Same ControlNet network as the redundant controllers (no bridging to I/O modules on another ControlNet network) • DeviceNet network • Universal remote I/O network IO Placement Redundant Chassis Pair Remote Chassis...

  • Page 32: Placement Of Operator Interface Terminals

    Design the System Placement of Operator For operator interface terminals, stay within these limitations. Interface Terminals Operator Interface Terminal Limitations Network Operator Interfaces Guidelines EtherNet/IP network PanelView Standard terminal Same as a nonredundant system • PanelView Plus terminal • Use RSLinx Enterprise software revision 3.0 or later.

  • Page 33: Additional Redundant Components

    Design the System Additional Redundant In addition to using redundant pairs of controllers, you may also add these redundant components to your system: Components • Redundant ControlNet Media • Redundant Power Supplies Redundant ControlNet Media Redundant ControlNet media prevents a loss of communication if a trunkline or tap is severed or disconnected.

  • Page 34: Redundant Power Supplies

    Design the System Redundant Power Supplies Redundant power supplies let you maintain power to a ControlLogix chassis if a power supply fails. Redundant power supplies use these supplies: • Two redundant power supplies, any combination of 1756-PA75R and 1756-PB75R. • 1756-PSCA chassis adapter module, in place of the standard power supply.

  • Page 35: Checking Connection Requirements

    Design the System Checking Connection Set aside seven connections in each redundant controller for redundancy communication. Requirements • Two connections for the SRM • Five connections for the partner controller Planning a ControlNet Follow these guidelines to plan a ControlNet network. Network ControlNet Network Guidelines Guideline...
  • Page 36 Design the System Guideline Details • If each redundant chassis has multiple CNB modules, set aside a pair of Set aside 2 consecutive ControlNet addresses for each pair of redundant chassis (for example, nodes 3 and 4). node numbers for each pair of CNB modules (one in each chassis). •...
  • Page 37 Design the System Guideline Details Do the redundant chassis use more than 1 ControlNet The NUT of each network must be within the values indicated on page 29. If network? you use a larger network update time (NUT), the controller could lose its connection with a module during a switchover.

  • Page 38: Planning An Ethernet/Ip Network

    Design the System Planning an EtherNet/IP Follow these guidelines as you plan your EtherNet/IP network. Network EtherNet/IP Network Guidelines Guideline Details Use EtherNet/IP only for HMIs, workstations, and In a redundant system, use an EtherNet/IP network only for HMI, workstation, messaging.

  • Page 39: Worksheet For Ip Swapping

    Design the System Guideline Details Decide how to handle IP addresses. If both redundant chassis are on Then Use IP swapping. Same subnet During a switchover the primary and Switch secondary modules swap IP addresses. This lets you use the same Primary Secondary IP address regardless of which...

  • Page 40: How An Ethernet/Ip Module Handles A Cable Break

    Design the System How an EtherNet/IP Module Handles a Cable Break An EtherNet/IP module looks for a carrier signal only from the closest switch. It does not know the health of the network beyond that point. Data does not have to be flowing. If the EtherNet/IP module: •...

  • Page 41: Additional Design Considerations

    Design the System Additional Design Keep these things in mind as you design your system. Considerations Additional Design Considerations Switchover always triggers an event A switchover triggers an event task under this combination of circumstances: task in a remote, nonredundant •...
  • Page 42 Design the System Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 43: Chapter 3 Introduction

    Use of the Network Access Port (NAP) IMPORTANT Do not connect any device to the network access port (NAP) of a 1756-CNB/D/E or 1756-CNBR/D/E module in a redundant chassis. • If you connect a device to the NAP of a CNB module in a redundant chassis, a switchover will fail to occur if the CNB module is disconnected from the network.
  • Page 44 1756-PA75 or -PB75 power supply ControlLogix Power Supplies Installation Instructions, publication 1756-5.78 ControlLogix controller ControlLogix Controller and Memory Board Installation Instructions, publication 1756-IN101 1756-CNB/D/E or -CNBR/D/E module ControlLogix ControlNet Bridge Installation Instructions, publication 1756-IN571 1756-ENBT module ControlLogix EtherNet/IP Bridge Module Installation Instructions, publication 1756-IN019...

  • Page 45: Install The Chassis For The Controllers

    Install the System Repeated electrical arcing causes excessive wear to contacts on both a module and its mating connector. Worn contacts may create electrical resistance that can affect module operation. Preventing Electrostatic Discharge ATTENTION This equipment is sensitive to electrostatic discharge, which can cause internal damage and affect normal operation.

  • Page 46: Install Modules In The First Redundant Chassis

    The primary node number is the node number of the primary chassis. 1. Set the rotary switches of each of the 1756-CNB/D/E or 1756-CNBR/D/E modules to the primary node number plus one. 42796 For example, modules 3 and 4 have a primary node number of 2.
  • Page 47 Install the System 2. Install a 1756-CNB/D/E or 1756-CNBR/D/E module. See ControlLogix ControlNet Bridge Installation Instructions, publication 1756-IN571. If you connect or disconnect the communications cable with WARNING power applied to this module or any device on the network, an electrical arc can occur.

  • Page 48: Install Modules In The Second Redundant Chassis

    • The modules in each redundant chassis must match each other IMPORTANT slot-by-slot. • Set the rotary switches of the 1756-CNB/D/E or 1756-CNBR/D/E modules for both redundant chassis to the same node address. 1. For each module in the first redundant chassis, install an identical module into the same slot of the second redundant chassis.

  • Page 49: Install The Remote Chassis Or Rails

    Install the System Install the Remote Chassis You must install all I/O modules and additional types of communication modules in remote chassis or on DIN rails. This or Rails example shows a remote 1756 chassis. You can use any type of chassis or device that you can connect to the ControlNet network.

  • Page 50: Configure Ethernet/Ip Modules

    Install the System Configure EtherNet/IP To use an EtherNet/IP module, give it an IP address, subnet mask, and gateway address. Modules Action Details Before you begin. A. Perform these steps if you have not already: • installed and connected both 1757-SRM modules. •...

  • Page 51: Flash The Modules

    Install the System Flash the Modules To flash the modules, perform this procedure. 1. Turn on the power to one of the redundant chassis. Redundancy Module PRIM Only power up one chassis at a time. IMPORTANT PRI COM 2. Wait for the 1757-SRM module to display PRIM. 42801 3.

  • Page 52: Actions

    Install the System Actions 1. Turn on the chassis power to the partner (secondary) chassis. First Chassis Second Chassis Turned On Turned On 2. Wait for the 1757-SRM module to complete its power-up cycle. Redundancy Module Redundancy Module Redundancy Module Redundancy Module •...

  • Page 53: Chapter 4 Introduction

    Chapter Configure the System Redundancy Module Introduction This chapter explains how to set or change the configuration of a 1757-SRM module. The SRM module controls the synchronization and switchover of your redundancy system. Use this chapter after you have installed your system to: •...

  • Page 54: Before You Begin

    Configure the System Redundancy Module Before You Begin RSLinx software includes and automatically installs the 1757-SRM System Redundancy Module configuration tool. Check your revision of the SRM configuration tool when you IMPORTANT open it for the first time. • The revision of tool that you get depends on your version of RSLinx software.

  • Page 55: What To Do Next

    Configure the System Redundancy Module What to Do Next Make sure that you check the revision of your SRM IMPORTANT configuration tool before you use it. Later revisions of the SRM configuration tool are not compatible with earlier revisions of ControlLogix redundancy systems.

  • Page 56: Actions

    Configure the System Redundancy Module Actions Action Details 1. Choose which revision to use. Do you connect your computer to ControlLogix redundancy systems revision 11.x or earlier? • Yes — Use revision 2.5 of the SRM Configuration Tool. Do not use revision 2.6. •...

  • Page 57: Before You Begin

    Configure the System Redundancy Module Before You Begin The SRM clock records when significant events occur. Please note these characteristics of the SRM clock: • Only the primary SRM’s clock requires setting. The secondary SRM’s clock synchronizes itself to the primary SRM’s clock. •...
  • Page 58 Configure the System Redundancy Module Action Details 2. Set the clock. A. Click Configuration. B. Do you want to set the clock of the SRM to the clock of your computer? Then Choose Apply Workstation Time and then Yes. 1. Change the date or time. 2.

  • Page 59: Test A Switchover

    Configure the System Redundancy Module Test a Switchover Use RSLinx software to manually initiate a switchover. Perform this procedure after you have synchronized your system and want to test a switchover. Before You Begin The CNB modules in the new primary chassis show the synchronization progress after a switchover.
  • Page 60 Configure the System Redundancy Module Action Details 2. Start a switchover. A. Click Synchronization. B. Choose Initiate Switchover and then choose Yes to continue. 3. Monitor the synchronization progress. A. Click Synchronization Status. If the controller contains a large project, the system may spend some time synchronizing the secondary controller.

  • Page 61: Change Auto-Synchronization

    Configure the System Redundancy Module Change You can control when the 1757-SRM module tries to synchronize the controllers. Auto-Synchronization Perform this procedure to: • help synchronize the system. • prevent the system from crossloading changes. Actions Action Details 1. Decide when you want the system to Do you plan to manually disqualify a chassis so you can make changes? synchronize.

  • Page 62: Change Program Control

    Configure the System Redundancy Module Action Details 3. Set the auto-synchronization option. A. Click Configuration. B. Select the Auto-Synchronization option. C. Choose Apply and then Yes to continue. D. Choose OK. Change Program Control You can direct the controller to send a message to the 1757-SRM module or block the controller from doing so.

  • Page 63: Actions

    Configure the System Redundancy Module Actions Action Details 1. Open the SRM configuration tool for the A. Start RSLinx software. primary chassis. B. From the Communications menu, choose RSWho. C. Open all the network branches to find the 1757-SRM module in the primary chassis. D.
  • Page 64 Configure the System Redundancy Module Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 65: Introduction

    Chapter Configure and Program the Controller Introduction This chapter explains how to configure and program the controller for redundancy. Create and maintain only one RSLogix 5000 project for the pair IMPORTANT of redundant controllers. When you download the project to the primary controller, the project automatically crossloads to the secondary controller.

  • Page 66: Decide If You Want To Keep Test Edits After A Switchover

    Configure and Program the Controller Decide if You Want to Keep Test Edits after a Switchover When you edit logic while online with the controller, the edits may fault the controller and cause a switchover. Test Edits Test Edits If test edits fault the primary controller, they will likely also fault the secondary controller.

  • Page 67: Be Aware That Finalizing Edits Removes Your Original Logic

    Configure and Program the Controller Be Aware That Finalizing Edits Removes Your Original Logic Finalize all edits in program. The controller removes the original logic when you finalize all edits in a program. If your changes cause a major fault and a switchover, the new primary controller also faults.

  • Page 68: Configure A Controller For Redundancy

    Configure and Program the Controller The controller sets up the quarantine area at the time of download: • The controller divides its memory into two sections: – tags, including a quarantine area – logic • The controller also divides its unused memory. It reserves a specific amount for tags that you create while online.
  • Page 69 Configure and Program the Controller 7. Select Redundancy Enabled. 8. Click Advanced. • We recommend that you not check this box. Leaving it unchecked prevents an incorrect online edit from faulting both the primary and secondary controller. • If you want any test edits to remain active during a switchover, then check this box.

  • Page 70: Configure Communications

    Configure and Program the Controller Configure Communications A redundant system requires some specific configuration choices for successful communications. Use this section to perform these redundancy tasks: • Configure I/O • Configure produced tags • Configure message (MSG) instructions • Configure tags for an HMIConfigure I/O For each module in your system, make sure that the requested IMPORTANT packet interval (RPI) is less than or equal to 375 milliseconds.
  • Page 71 Configure and Program the Controller Produced Tag Configuration Produced Tag To the controller with the consumed tag, this is the remote CNB module. Redundant Chassis Data Consumed Tag Remote Chassis In the I/O configuration of this controller, select a communication format of None for the remote CNB module.

  • Page 72: Configure Message (Msg) Instructions

    Configure and Program the Controller Configure Message (MSG) Instructions If the MSG instruction Then From a redundant In a redundant controller, any MSG instruction that is in progress during a switchover experiences an error. controller (The ER bit of the instruction turns on.) After the switchover, normal communication resumes. To a redundant controller For any MSG instruction from a controller in another chassis to a redundant controller, cache the connection: Properties of the Message to the Redundant Controller...

  • Page 73: Configure Tags For An Hmi

    Configure and Program the Controller Configured Message Instructions, Continued If the message Then instruction is targeted to a redundant controller During the erroring out All backplane communications cease. This stoppage allows the redundant controller to receive the message of a message instruction required to perform a switchover or any diagnostics.

  • Page 74: Estimate The Crossload Time Of A Program

    Configure and Program the Controller Estimate the Crossload You can estimate the crossload time of a program in a redundant controller. Time of a Program By lowering the amount of time you spend crossloading data, IMPORTANT you can reduce your scan time. Perform this procedure to gauge the time a project spends crossloading data.

  • Page 75: Actions

    Configure and Program the Controller Actions Action Details 1. Get the size of your crossload data. Use a Get System Value (GSV) instruction to read the REDUNDANCY object. For this information Get this attribute Data Description Type • Size of the last crossload LastDataTransfer DINT This attribute gives the size of data that was or would have been...

  • Page 76: Minimize Scan Time

    Configure and Program the Controller Minimize Scan Time To minimize a project’s scan time, perform this procedure. Do not try to get the scan time of a ControlLogix redundancy IMPORTANT project down below about 20 milliseconds. At very low scan times, crossload data becomes a bigger performance burden.
  • Page 77 Configure and Program the Controller Action Details 2. Delete unused tags. This reduces the size of the tag database. A smaller database takes less time to crossload. To delete unused tags: A. Open one of the tags folders. B. Click Edit Tags. C.
  • Page 78 Configure and Program the Controller Action Details 4. If you have already created individual If you have already created individual tags, change them to aliases for elements of an tags, change them to aliases. array. Your logic points to the aliases. The controller crossloads the base array. A.
  • Page 79 Configure and Program the Controller Action Details 6. Keep code as compact as possible. Avoid checking the same conditions many times. Each instruction adds scan time to your controller. This is better This rung checks Bool_B and Bool_C only once each scan. Than this This rung checks Bool_B and Bool_C twice each scan.
  • Page 80 Configure and Program the Controller Action Details 7. Execute code only when you need it. The controller crossloads a tag anytime an instruction writes a value to the tag. This happens even if the value stays the same. • Many instructions write a value whenever they run. For example, instructions such as OTL, OTU, and many instructions with Destination operands write a value each time the rung-condition-in is true.
  • Page 81 Configure and Program the Controller Action Details 8. Group your data by how often you need it. To update the secondary controller, the primary controller divides its memory into blocks of 256 bytes. Anytime an instruction writes a value, the primary controller crossloads the entire block that contained the value.

  • Page 82: Maintain Data Integrity During A Switchover

    Configure and Program the Controller Maintain Data Integrity The redundancy system guarantees a bumpless switchover for any logic in the highest priority task. In some cases, a switchover may During a Switchover make lower priority tasks repeat part of their scan. This has to do with how data crossloads from the primary controller to the secondary controller.
  • Page 83 Configure and Program the Controller Interrupted Switchover Interruption by the program End of the program in a in a higher priority task. higher priority task. Start of the program in the lower priority task (for example, the continuous task). • This portion of the task is not executed Primary Controller during this scan.

  • Page 84: Look For Array Shift Instructions

    Configure and Program the Controller Look for Array Shift Instructions These instructions might corrupt data during a switchover: • BSL • BSR • FFU Because these instructions shift data within an array, an interruption by a higher priority task and a subsequent switchover leaves the data with an incomplete shift.

  • Page 85: Take Preventative Actions

    Configure and Program the Controller C. If a higher priority task interrupts the logic, the value of scan_count.ACC is sent to the secondary controller at the end of the program in the higher priority task. D. If a switchover occurs before the EQU instruction, the secondary controller starts its execution at the beginning of the program.
  • Page 86 Configure and Program the Controller Use UID and UIE Instruction Pairs Bound critical rungs with UID and UIE instruction pairs. This prevents the higher priority task form interrupting the scan-dependent logic. Buffer Critical Data This example shows the use of a buffer together with a BSL instruction.

  • Page 87: Determine The Status Of Your Redundant System

    Configure and Program the Controller Determine the Status of You can write code that determines the status of your redundant system. Your Redundant System Perform this procedure to: • show system status on an HMI screen. • condition code to execute based on system status. •...

  • Page 88: Check Your Work

    Configure and Program the Controller Check Your Work Use the Redundancy tab of the Controller Properties window to check the code attributes. It does not show all the attributes, but it shows the more common attributes. 1. Download and run your project. 2.

  • Page 89: Condition Logic To Run After A Switchover

    Configure and Program the Controller Condition Logic to Run After You can condition a section of your logic to run after a switchover. a Switchover Follow these examples to create logic in preparation for a possible switchover. Example 1: Ladder Diagram Get the ID of the primary chassis.

  • Page 90: Example 2: Structured Text

    Configure and Program the Controller If Switchover_Happened = on, then 1. Execute the instructions that you want to execute after a switchover. 2. Turn off the Switchover_Happened bit. Put your instructions here. Example 2: Structured Text comment //Get the ID of the primary chassis. comment //That is always the chassis that runs the code.

  • Page 91: Send A Message To The Srm

    Configure and Program the Controller If Chassis_ID_Now <> Chassis_ID_Last then Switchover_Happened := 1; Chassis_ID_Last := Chassis_ID_Now; End_If; //If Switchover_Happened = on //Then //Execute the instructions that you want to execute after a switchover. //Turn off the Switchover_Happened bit. If Switchover_Happened then Put your statements here.

  • Page 92: Before You Begin

    Configure and Program the Controller Before You Begin Before sending a message to an SRM, make sure that: • the SRM is configured for program control. • the message is unconnected. Leave the Connected check box clear (unchecked). Publication 1756-UM523F-EN-P - December 2006...

  • Page 93: Actions

    Configure and Program the Controller Actions Use this table to configure a message to an SRM module. Configuring a Message to an SRM If you want to On this tab For this item Type or select Initiate a switchover Configuration Message Type CIP Generic Service Code...
  • Page 94 Configure and Program the Controller Configuring a Message to an SRM (Continued) If you want to On this tab For this item Type or select Synchronize the secondary Configuration Message Type CIP Generic controller Service Code Class name Instance name Attribute name Leave blank Source...

  • Page 95: Download The Project To The Primary Controller

    Configure and Program the Controller Download the Project to the You only have to download the project to the primary controller. When the secondary controller is synchronized, the system Primary Controller automatically crossloads the project to the secondary controller. If the secondary chassis becomes disqualified after you IMPORTANT download the project, make sure that you: •...
  • Page 96 Configure and Program the Controller b. Choose Advanced. c. Leave unchecked Match Project to Controller. If you match your downloaded project to your controller, you tie IMPORTANT your project to your controller’s serial number. If you then switch over to a controller in a different chassis, your project will not match the new controller’s serial number, disabling the controller functions originally specified under the Advanced tab of Controller Properties...

  • Page 97: Schedule A Controlnet Network

    Configure and Program the Controller Schedule a ControlNet Network Before you schedule a ControlNet network, turn on the power IMPORTANT to both redundant chassis. If you schedule a ControlNet network while the secondary chassis is off, the keeper signature of a CNB module may not match its partner, and the secondary chassis will fail to synchronize.

  • Page 98: Update The Schedule Of An Existing Network

    Configure and Program the Controller 10. From the Network menu, choose Single Pass Browse. 11. From the File menu, choose Save. 12. Type a name for the file that stores the network configuration, then choose Save. 13. Select the Optimize and rewrite Schedule for all Connections button (default) and choose OK.

  • Page 99: Check The Keepers

    Configure and Program the Controller Check the Keepers To check the keepers, perform this procedure. On a ControlNet network, each keeper must: • take over the keeper duties if the current keeper drops off the network. • use the same configuration regardless of which keeper first comes online after a major network disturbance, such as a cable short or system power cycle.

  • Page 100: Set Task Watchdog Times

    Configure and Program the Controller Set Task Watchdog Times To give a redundant controller longer watchdog times than a nonredundant controller, perform this procedure. • After a switchover, the secondary controller starts the scan at the beginning of the program that was running in the primary controller at the time of the switchover.
  • Page 101 Configure and Program the Controller Action Details 3. Determine the real scan time of a task. Complete these steps while the controller is running. Controller Primary − Tasks MainTask A. Right-click the task and choose Properties. B. Click Monitor. C. Look at the scan times. Longest time it has taken in microseconds to scan this task.
  • Page 102 Configure and Program the Controller Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 103: Maintain And Troubleshoot The System

    Chapter Maintain and Troubleshoot the System Introduction This chapter explains how to commission, maintain, and troubleshoot your redundancy system. Simultaneous power of redundant Under this combination of conditions (all must apply), duplicate IP addresses on your EtherNet/IP chassis pair may bump another network will cause you to lose communication with a redundant chassis pair over that EtherNet/IP redundant chassis pair off the network.

  • Page 104: Diagnose A Switchover Or Disqualification

    • an unplanned switchover happens. • a chassis that was synchronized becomes disqualified. Actions • Do the 1756-CNB/D/E or 1756-CNBR/D/E modules in the Start here. primary chassis show PwQS? • Yes — Go to Interpret the SRM Event Log on page 109.

  • Page 105: Troubleshoot A Failure To Synchronize

    Maintain and Troubleshoot the System 2. Wait several minutes for the system to try to synchronize. What do the CNB modules in the primary chassis show? • PwQS — Stop. Your system is synchronized. • PwDS — Go to step 3. 3.
  • Page 106 Maintain and Troubleshoot the System 1. Observe the 1756-CNB/D/E or 1756-CNBR/D/E modules in the primary chassis. Primary CNB Front panel It means So do this PwQS Primary with Synchronized Stop. The redundant chassis are (Qualified) Secondary synchronized. Look here. PwDS Primary with Disqualified Secondary Go to step 2.

  • Page 107: Update A Keeper Signature

    Maintain and Troubleshoot the System Update a Keeper Signature To see if the keeper signature of a CNB module is stopping the secondary chassis from synchronizing, you need to update the keeper signature. To update the keeper signature, perform this procedure when a Secondary Chassis secondary chassis will not synchronize and its CNB modules show !CPT.

  • Page 108: Edit Sessions In Progress

    Maintain and Troubleshoot the System 4. Make sure that each node has a valid keeper signature. If the Valid Keeper column shows Then The node has a valid keeper signature. Select the node and choose Update Keeper. 5. Choose Close. Edit Sessions in Progress To see if a computer is stopping the secondary chassis from synchronizing, you must see if an edit session is in progress.

  • Page 109: Interpret The Srm Event Log

    Maintain and Troubleshoot the System Action Details 2. Check the recent synchronization attempts. A. Click Synchronization. B. Do you see Edit Session In Progress under Recent Synchronization Attempts? • Yes — Go to step 3. • No — An edit session did not stop synchronization.

  • Page 110: Before You Begin

    Maintain and Troubleshoot the System Before You Begin The SRM clock is accurate only if you: • initially set it after you installed your system. • reset it after any power loss to both chassis. Actions Action Details 1. Open the SRM configuration tool for the A.
  • Page 111 Maintain and Troubleshoot the System Action Details 3. Look through the events of the secondary A. Start with the secondary chassis. chassis for a substantial change in log • The lower list is the secondary chassis. times. • The cause of the switchover probably happened to secondary chassis while it was the primary chassis.
  • Page 112 Maintain and Troubleshoot the System Action Details 4. Double-click and event for more A. Double-click an event to see if it gives more information. information. The Extended Information Definition dialog opens. B. Click OK when you are done to close the Extended Information Definition dialog. Example Someone removed the module for slot 2.

  • Page 113: Interpret Srm Events

    Maintain and Troubleshoot the System Interpret SRM events Use this table to interpret events recorded in the SRM’s event log. SRM Event Descriptions Event Description Meaning Autoqualification Trigger Something happened that caused the system to try and synchronize again. Double-click the event to see what happened.
  • Page 114 Maintain and Troubleshoot the System Event Description Meaning Module Removal The SRM no longer sees a module on the backplane. This means that the module either experienced a nonrecoverable fault, was removed from the chassis, or was reset. Double-click the event to see the slot number of the module. Modules Chassis State Rule A check to choose a primary chassis if both chassis power up at the same time.

  • Page 115: Export The Srm Event Log

    Maintain and Troubleshoot the System Event Description Meaning The partner RM screamed The partner SRM lost power, has an unrecoverable fault, or was removed. An SRM has circuits that hold power long enough for it to send a message to its partner over the fiber-optic interconnect cable.

  • Page 116: Actions

    Maintain and Troubleshoot the System When you send event logs to Rockwell Automation: IMPORTANT • send events from both the primary and secondary chassis. • include all events from the latest event to the last event when you knew that the chassis were in a good state. •...
  • Page 117 Maintain and Troubleshoot the System Action Details 3. Select the events that you want to export. A. Click the first event that you want to export from the primary chassis. B. Press and hold the [Shift] key and then click the last event that you want to export from the primary chassis.

  • Page 118: Manually Synchronize The Chassis

    3. Expand the network until you see the 1757-SRM module in the primary chassis. − Workstation Linx Gateways, Ethernet − AB_KTC-x, ControlNet − n, 1756-CNB/D/E − Backplane, 1756-Ax xx, 1756 module, 1757-SRM 4. Right-click the 1757-SRM module and select Module Configuration. 5. Click Synchronization. Publication 1756-UM523F-EN-P - December 2006...

  • Page 119: Optimize Communication

    Maintain and Troubleshoot the System 6. Click Synchronize Secondary and then choose Yes to confirm. 7. Click OK. 8. In the primary chassis, what do the CNB modules display? Front Panel If you see Which means Then • Synchronization is in progress. PwQg Primary with Synchronizing (Qualifying) Secondary...

  • Page 120: Choose A Greater System Overhead Time Slice

    Maintain and Troubleshoot the System Acceleration of Unscheduled Communication If an RSLogix 5000 project contains Then See Page Only a continuous task and no other tasks Choose a Greater System Overhead Time (This is the default task configuration.) Slice More than one task (for example, at least 1 Make All Your Tasks Periodic periodic task) Choose a Greater System Overhead Time Slice...

  • Page 121: Enter A System Overhead Time Slice

    Maintain and Troubleshoot the System If you increase the system overhead time slice to 33 %, unscheduled communication occurs every 2 ms of continuous task time for 1 ms. 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms 1 ms Unscheduled...

  • Page 122: Make All Your Tasks Periodic

    Maintain and Troubleshoot the System Make All Your Tasks Periodic Action Details 1. If you have more than one task, make If the controller contains only a periodic task or tasks, the system overhead time slice value them all periodic tasks. has no effect.

  • Page 123: Check The Allocation Of Unused Memory

    Maintain and Troubleshoot the System Check the Allocation of The controller reserves a specific amount of unused memory for tags and the rest for logic. Depending on how you configure the memory Unused Memory usage, you might not have memory for the required operation. To display this dialog: 1.

  • Page 124: Use Rslinx Software

    3. Right-click the module and choose Module Statistics. 4. Click Connection Manager. Number of Connections Used CPU Usage 42903 Four-Character Display The four-character display on the front of the 1756-CNB/D/E or 1756-CNBR/D/E module, shows this information. 42797 Publication 1756-UM523F-EN-P - December 2006...
  • Page 125 Maintain and Troubleshoot the System Four-Character Display Readings For this information about a Display Where CNB module Address of the module A#xx xx is the node address of the module. Percent of CPU usage %Cxx xx is the percent of CPU usage. The range for the display is 00 - 99%. Number of open connections nCxx xx is the number of open connections that the module is using.

  • Page 126: Send A Message To The Cnb Module

    Maintain and Troubleshoot the System Send a Message to the CNB Module To use a Message (MSG) instruction to learn the CPU usage of a CNB module, configure the MSG instruction. CNB Module Configuration On this tab For this Type or select Configuration Message Type CIP Generic...
  • Page 127 Maintain and Troubleshoot the System In a redundant system, store or load a project only while the secondary chassis is disqualified. To store or load a project, perform these procedures. Storing or Loading Projects Action Details Store a Project Important: If your computer is online with the controller over a ControlNet network, check the CPU usage of the CNB module.

  • Page 128: Store A Project To Nonvolatile Memory While A Process Is Running

    Maintain and Troubleshoot the System Store a Project to To store an updated project and firmware to the nonvolatile memory of a 1756-L61, 1756-L62 or 1756-L63 controller while the process is Nonvolatile Memory While running, perform this procedure. a Process Is Running Use this procedure only with a 1756-L61, 1756-L62 or 1756-L63 IMPORTANT controller.

  • Page 129: Chapter 7 Introduction

    Update the firmware of a redundant chassis without shutting Update an Online Redundant System down the process Change CNB Modules from To replace 1756-CNB/D or 1756-CNBR/D module(s) with series E modules while you are online, perform this procedure. Series D to Series E While Online •...

  • Page 130: Actions

    Action Details 1. Add the latest EDS files. Add the revision 11 EDS files for the 1756-CNB and 1756-CNBR modules, if you have not already done so, 2. Prepare the RSLogix 5000 project. A. Start the RSLogix 5000 software and go online with the primary controller.
  • Page 131 Update Modules and Redundant Systems Action Details 3. Open the SRM configuration tool for the A. Start RSLinx software. primary chassis. B. From the Communications menu, choose RSWho. C. Open the branches of your network until you find the 1757-SRM module in the primary chassis.
  • Page 132 Update Modules and Redundant Systems Action Details Did you already update the firmware of the Did you already update the firmware of the series E modules? series E modules? • Yes — Go to step 6. • No — Continue with step 5. 5.
  • Page 133 Update Modules and Redundant Systems Action Details 7. Update the keeper signatures of the CNB A. Start RSNetWorx for ControlNet and open the network configuration file. modules. B. Go online with the network. You do not have to browse the entire network. C.
  • Page 134 Update Modules and Redundant Systems Action Details 8. Reset the secondary CNB modules. A. Cycle power to the secondary chassis. B. On the Synchronization Status tab of the configuration tool, verify that the modules show full compatibility. 9. Synchronize the secondary chassis. A.
  • Page 135 Update Modules and Redundant Systems Action Details 12. Synchronize the chassis. A. Go to the SRM configuration tool for the primary chassis. B. On the Configuration tab, change the Auto-Synchronization option to Always. C. Choose Apply and Yes. 13. In the RSLogix 5000 project, change the revision of the new local CNB modules to revision 11.

  • Page 136: Update A Redundant Control System Offline

    Update Modules and Redundant Systems Update a Redundant Complete this procedure to upgrade the revision of your redundant modules. This procedure minimizes the time your process is down Control System Offline during an upgrade. Do not connect your computer to the network access port on a IMPORTANT CNB module in the primary chassis.
  • Page 137 Update Modules and Redundant Systems Action Details 3. Disqualify the secondary chassis, A. Click Configuration. B. Set Auto-Synchronization to Never. C. Choose Apply and then Yes to confirm. D. Click Synchronization. E. Choose Disqualify Secondary and then Yes to confirm. 4.

  • Page 138: Update An Online Redundant System

    Update Modules and Redundant Systems Update an Online The redundancy system update feature of ControlLogix lets you update the firmware in a secondary chassis while the primary chassis Redundant System is controlling outputs. However, during a redundancy system update, remember that: •...

  • Page 139: Redundant System Relationships

    Update Modules and Redundant Systems When a secondary communications module is locking for IMPORTANT updating, it displays SLU. When a primary communications module is locked for updating and has firmware revision 15.56 or later, it displays PLU. If the primary communications module’s firmware is an earlier revision, PwQS will be displayed when the system is locked.
  • Page 140 Update Modules and Redundant Systems Action Details 1. Update the software. A. Go to the tool tray of your computer and shutdown RSLinx software. B. Update this software: • 1757-SRM System Redundancy Module Configuration tool • RSLogix 5000 software • RSLinx software •...
  • Page 141 Update Modules and Redundant Systems Action Details 5. Disqualify the secondary chassis, A. Click Configuration. B. Set Auto-Synchronization to Never. C. Choose Apply and then Yes. D. Click Synchronization. E. Click Disqualify Secondary and then Yes. The secondary chassis is disqualified.
  • Page 142 Update Modules and Redundant Systems Action Details 8. Initiate a switchover. A. Click Initiate Switchover and Yes. B. Wait for the system to switchover. The other chassis is now the primary chassis. 9. Update the modules in the new Use the ControlFLASH firmware update tool to update the modules in the new secondary secondary chassis.
  • Page 143 Update Modules and Redundant Systems Action Details 11. Change the project revisions. A. Go offline. B. Click the Controller Properties button. C. Change the controller to the newer revision. Example: Change the controller from revision 13 to revision 15. D. Change the Revision of each local communication module to match what its revision will be after you update its firmware.
  • Page 144 Update Modules and Redundant Systems Action Details 12. Download the project to the secondary Important: If I/O forces are enabled in the offline project, the software asks if you want to controller. enable the forces in the controller. Even if you choose No, I/O forces stay enabled in the primary controller and become enabled in this controller after you switchover.
  • Page 145 Update Modules and Redundant Systems Action Details 14. Initiate a Locked Switchover. A. Click Initiate Locked Switchover and Yes. B. Wait for the system to switchover. A locked switchover takes about as long as a normal switchover. The other chassis is now the primary chassis.
  • Page 146 Update Modules and Redundant Systems Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 147: Appendix A Introduction

    Appendix Set Up EtherNet/IP Communication Across Subnets Introduction This appendix explains how to keep HMIs and messages pointing to the primary chassis when IP swapping is not in use. This appendix provides this information. Topic Page Keep an HMI Communicating with the Primary Chassis Keep a Message Going to the Primary Chassis Use this appendix when: •...

  • Page 148: Keep An Hmi Communicating With The Primary Chassis

    Set Up EtherNet/IP Communication Across Subnets Keep an HMI If you are not using IP swapping, your HMIs must direct their communication to the new primary chassis after a switchover. Communicating with the ControlLogix Redundancy Alias Topic Switcher software can most Primary Chassis easily do this.

  • Page 149: Install The Controllogix Redundancy Alias Topic Switcher Software

    Set Up EtherNet/IP Communication Across Subnets To keep an HMI communicating with the primary chassis: • install the ControlLogix Redundancy Alias Topic Switcher Software. • configure a Driver to Communicate with the Primary and Secondary EtherNet/IP Modules. • create a DDE/OPC topic for each controller. •...

  • Page 150: Configure A Driver To Communicate With The Primary And Secondary Ethernet/Ip Modules

    Set Up EtherNet/IP Communication Across Subnets Configure a Driver to Communicate with the Primary and Secondary EtherNet/IP Modules 1. Start RSLinx software. 2. Click 3. Select Ethernet devices and choose 4. Accept the default name. 5. Type the IP address of each ENBT or EWEB module. To add another IP address, choose 6.

  • Page 151: Create A Dde/Opc Topic For Each Controller

    Set Up EtherNet/IP Communication Across Subnets Create a DDE/OPC Topic for Each Controller 1. Browse to the controller in Chassis A. 2. Right-click the controller and choose Configure New DDE/OPC Topic. 3. Rename the topic to indicate that this is Chassis A. 4.

  • Page 152: Create An Alias Topic

    Set Up EtherNet/IP Communication Across Subnets Create an Alias Topic 1. In RSLinx software, choose DDE/OPC ⇒ Alias Topic Configuration. 2. Type a name for the alias topic that will communicate with this pair of redundant controllers. 3. Add the topic for each redundant controller to the Aliased Topics list.

  • Page 153: Set Up The Alias Topic Switcher

    Set Up EtherNet/IP Communication Across Subnets Set Up the Alias Topic Switcher If you start the Alias Topic Switcher software without access to IMPORTANT an RSLinx activation file (for example, without a version of RSLinx which supports OPC), this error occurs: 0x80040112 (The text for the message depends on your operating system.) 1.

  • Page 154: Address The Alias Topic In The Hmi Project

    Set Up EtherNet/IP Communication Across Subnets Address the Alias Topic in the HMI Project When you create tags for your HMI project, use the alias topic in the address of the tag. Keep a Message Going to If you are not using IP swapping, any controller that sends a message to a redundant chassis has to point to the new primary chassis after a the Primary Chassis switchover.

  • Page 155: Create A Periodic Trigger For The Messages

    Set Up EtherNet/IP Communication Across Subnets Type - CIP Generic Chassis A Type - CIP Generic Chassis B To keep a Message (MSG) instruction going to the new primary chassis after a switchover: • create a periodic trigger for the messages. •...

  • Page 156: Get The Redundancy State Of Chassis A

    Set Up EtherNet/IP Communication Across Subnets Get the Redundancy State of Chassis A If Timer_RedundancyMSGs.DN = 1 (2 seconds are up so execute the MSG instruction again) And ChasA_GetRedundState_FromENBT.EN = 0 (The MSG instruction is not currently enabled.) Then Execute a MSG instruction that gets the redundancy state of Chassis A from the ENBT module in Chassis A. Store the value in ChasA_RedundancyState (data type = DINT).

  • Page 157: Get The Redundancy State Of Chassis B

    Set Up EtherNet/IP Communication Across Subnets MSG Parameter Value Source Length Destination ChasA_RedundancyState Path Specify the 1756-ENBT module in Chassis A. Use either of these (communication tab) methods: • Add the module to the I/O configuration of the controller. Then use the Browse button on the Communication tab to identify the module.
  • Page 158 Set Up EtherNet/IP Communication Across Subnets MSG Parameter Value Message Type CIP Generic Service Type Get Attribute Single Service Code Class Instance Attribute Source Element Source Length Destination ChasB_RedundancyState Path Specify the 1756-ENBT module in Chassis B. Use either of these (communication tab) methods: •...

  • Page 159: Determine Which Chassis Is Primary

    Set Up EtherNet/IP Communication Across Subnets Determine Which Chassis is Primary If ChasA_RedundancyState = 2, 3, or 4 then ChasA_IsPrimary = 1. (Chassis A is the primary chassis.) If ChasB_RedundancyState = 2, 3, or 4 then ChasB_IsPrimary = 1. (Chassis B is the primary chassis.) Tag Name Description Alias For...

  • Page 160: Send The Message To The Appropriate Controller

    Set Up EtherNet/IP Communication Across Subnets Tag Name Description Alias For Data Type ChasA_IsPrimary If set (1), then Chassis A is the primary chassis. IsPrimary.0 BOOL ChasB_IsPrimary If set (1), then Chassis B is the primary chassis. IsPrimary.1 BOOL IsPrimary Each bit represents the primary status for an DINT individual chassis within a redundant chassis pair.
  • Page 161 Set Up EtherNet/IP Communication Across Subnets If Timer_RedundancyMSGs.DN = 1 (2 seconds are up.) And ChasB_IsPrimary = 1. (Chassis B is the primary chassis.) And ChasB_MSG.EN = 0 (The message is not currently enabled.) Then Execute the MSG instruction for the controller in Chassis B. Tag Name Description Alias For...
  • Page 162 Set Up EtherNet/IP Communication Across Subnets Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 163: Appendix B Introduction

    Appendix Convert an Existing System to Redundancy Introduction This appendix explains how to convert an existing system to redundancy. If you are adding redundancy to an existing system, follow these guidelines: • Changing the node number of a CNB module may affect messages, tags, or listen-only connections in other devices.

  • Page 164: Reconfigure The Local I/O Modules

    [x] 1756-xxx name_of_local_module Cut local I/O modules from here. − [x] 1756-CNB/x name_of_local_CNB z [x] 1756-CNB/x name_of_remote_CNB Paste the I/O modules here. 2. In the controller organizer, cut these modules from the local I/O configuration and paste them into the remote CNB module: •...
  • Page 165 Convert an Existing System to Redundancy 3. Type Local. 4. Type the name of the CNB module that is in the remote chassis. 5. Select All Routines. 6. Click Find Within >>. 42805 7. Select Ladder Diagrams. 8. Check Instruction Operands. 9.

  • Page 166: Replace Any Aliases To Local I/O Tags

    Convert an Existing System to Redundancy This example shows the results of replacing Local with chassis_c. Replacing Local with chassis_c... EXAMPLE Searching through MainProgram - MainRoutine... Replaced: Rung 0, XIC, Operand 0: XIC(Local:16:I.Data.0) Replaced: Rung 0, OTE, Operand 0: OTE(Local:2:O.Data.0) Replaced: Rung 1, XIC, Operand 0: XIC(Local:16:I.Data.1) Replaced: Rung 1, OTE, Operand 0: OTE(Local:2:O.Data.1) Replaced: Rung 2, XIC, Operand 0: XIC(Local:16:I.Data.2)
  • Page 167 Convert an Existing System to Redundancy 42815 3. Type Local. 4. Type the name of the CNB module that is in the remote chassis. 5. Select All Tags. 6. Click Find Within >>. 42815 7. Check Alias. 8. Choose Replace All. 9.
  • Page 168 Convert an Existing System to Redundancy Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 169: Appendix C Introduction

    Appendix Attributes of the Redundancy Object Introduction This appendix explains how to use the redundancy object to learn about the status of your redundant system. Attributes of the These are the attributes of the redundancy object. Redundancy Object Redundant System Status and Corresponding Attributes For this information Get this attribute Data...
  • Page 170 Attributes of the Redundancy Object For this information Get this attribute Data GSV/SSV Description Type Results of the compatibility CompatibilityResults INT Then checks with the partner Undetermined controller. No compatible partner Fully compatible partner Status of the Qualification Then synchronization InProgress Synchronization (qualification) is not in progress.
  • Page 171 Attributes of the Redundancy Object For this information Get this attribute Data GSV/SSV Description Type Mode of the partner. PartnerMode DINT Then 16#0 Power up 16#1 Program 16#2 16#3 Test 16#4 Faulted 16#5 Run-to-program 16#6 Test-to-program 16#7 Program-to-run 16#8 Test-to-run 16#9 Run-to-test 16#A...
  • Page 172 Attributes of the Redundancy Object For this information Get this attribute Data GSV/SSV Description Type Slot number of the SRMSlotNumber 1757-SRM module in this chassis. • Size of the last LastDataTransfer DINT This attribute gives the size of data that was or would have crossload.

  • Page 173: Appendix D Introduction

    You can temporarily lose communication with a remote chassis if you use both these modules in the remote chassis: while Bridging Via a Series B ControlNet • 1756-CNB/B or 1756-CNBR/B module Bridge Module • 1756-DHRIO module that is connected to a remote I/O network. Communication Loss While Bridging...

  • Page 174: Communication Stoppage While Using A Series B Controlnet Bridge Module

    Communication Stoppage All communication on a ControlNet network could stop if the lowest node is a 1756-CNB/B or 1756-CNBR/B module. This happens if you While Using a Series B unplug or break the tap of the module while it is turned on.
  • Page 175 • During the communication loss, the I/O modules go to their configured state for a communication fault. • The communication loss is temporary. Communications restore themselves. To prevent this situation, use 1756-CNB/D/E or 1756-CNBR/D/E modules. Publication 1756-UM523F-EN-P - December 2006...
  • Page 176 1756-CNB or -CNBR/D module is breaking a cable could stop all disconnected or breaks and then is replaced while power is still applied to the the 1756-CNB/B or communications over the network.

  • Page 177: Appendix E Introduction

    Appendix Redundant System Restrictions Introduction This appendix explains the known restrictions affecting a redundant system. In a redundant system, use an EtherNet/IP network only for IMPORTANT HMI/workstation communication and messaging. Do not use an EtherNet/IP network for: • communication with I/O modules. •...
  • Page 178 Redundant System Restrictions Notes: Publication 1756-UM523F-EN-P - December 2006...

  • Page 179: Index

    Index Numerics connection requirements 35 consumed tag 1756-ENBT module configure 70 See ENBT module controller 1756-EWEB module configure 68 EWEB module download project 95 1757-SRM module install 46 See SRM module nonvolatile memory 126 periodic task 122 program scan time 74 requirements 22 synchronize 51 redundant components 33...

  • Page 180: Index

    Index configure 50 IP address requirements 23 assign 50 estimate program scan time 74 what happens during a switchover 20 EtherNet/IP network IP swapping configure modules 50 overview 20 design 21 IP swapping 20 module requirements 23 keeper signature plan 38 check 99 proper use 177 update 107...

  • Page 181: Index

    Index revision 13 updating system 138 periodic task 122 RIO network place design 21 I/O 31 operator interface terminals 32 pair of redundant chassis 30 plan scan time ControlNet network 35 See program scan time, task scan time EtherNet/IP network 38 schedule power supplies ControlNet network 97...
  • Page 182 Index system test edits getting information 87 finalize 67 install 43 what happens during a switchover 18 overhead time slice 120 troubleshoot switchover 104 task number of 122 update set watchdog time 100 firmware 51 test keeper signature 107 switchover 59 modules 129 offline redundant system 136 online redundant system 138...
  • Page 183 ___Yes, please call me ___Yes, please email me at __________________________ ___Yes, please contact me via ________________________ Return this form to: Allen-Bradley Marketing Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705 Phone: 440-646-3176 Fax: 440-646-3525 Email: [email protected] Publication ICCG-5.21- January 2001...
  • Page 184 PLEASE FASTEN HERE (DO NOT STAPLE) Other Comments PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE 1 ALLEN-BRADLEY DR MAYFIELD HEIGHTS OH 44124-9705...

  • Page 186: Rockwell Automation Support

    Rockwell Automation Rockwell Automation provides technical information on the web to assist you in using our products. At http://support.rockwellautomation.com, you can Support find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.

This manual is also suitable for:

1756-cnd: 1756-cne1756-enbt1756-eweb1756-l551756-l55m121756-l55m13 ... Show all

Table of Contents