User Manual Owner's manual

ManualsBrandsRockwell Automation ManualsEquipment1756-RMxx ControlLogix Enhanced Redundancy System

ControlLogix Enhanced Redundancy System

Catalog Numbers 1756-RM, 1756-RMXT, 1756-RM2, 1756-RM2XT

User Manual

Summary of content (296 pages)

PAGE 1
User Manual ControlLogix Enhanced Redundancy System Catalog Numbers 1756-RM, 1756-RMXT, 1756-RM2, 1756-RM2XT
PAGE 2
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.
PAGE 3
Summary of Changes This publication contains new and updated information. Changes throughout this revision are marked by change bars, as shown to the right of this paragraph. New and Updated Information This table contains the changes made to this publication revision. Table 1 - New and Updated Information Topic Page This publication includes the addition of the 1756-RM2/A and 1756-RM2XT modules. 1756-RM2/A or 1756-RM2XT modules can only be used with other 1756-RM2/A or 1756-RM2XT modules.
PAGE 4
Summary of Changes Table 1 - New and Updated Information Topic 4 Page SFP error message. 230 Added missing Module Status Display descriptions for the 1756-RM/A and 1756-RM/B modules. 231 Replace 1756-RM/B redundancy modules with 1756-RM2/A redundancy modules without initiating a switchover.
PAGE 5
Table of Contents Preface Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Chapter 1 About Enhanced Redundancy Systems Features of the ControlLogix Enhanced Redundancy System . . . . . . . . Enhanced Redundancy System Components . . . . . . . . . . . . . . . . . . . . . . . I/O Modules in Enhanced Redundancy Systems . . . . . . . . . . . . . . . . Enhanced Redundancy System Operations . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Table of Contents Install the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add the EDS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2: Install the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the First Chassis and its Components . . . . . . . . . . . . . . . . . . . . Install the Chassis and Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Table of Contents Options for Setting the IP Addresses of EtherNet/IP Communication Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Half/Full Duplex Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Use An Enhanced Redundancy System in a Device-level Ring Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Chapter 5 Configure the ControlNet Network Produce/Consume Connections . . .
PAGE 8
Table of Contents System Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit a User Comment for a System Event . . . . . . . . . . . . . . . . . . . . . . Save System Event History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Dual Fiber Ports with the 1756-RM2/A Redundancy Module Fiber Channel Switchover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . .
PAGE 9
Table of Contents Load a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support for Partial Import Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . Plan for Test Edits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finalize Edits with Caution . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
Table of Contents Appendix A Status Indicators Redundancy Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1756-RM2/A and 1756-RM2XT Status Indicators. . . . . . . . . . . . . 1756-RM/A and 1756-RM/B Status Indicators . . . . . . . . . . . . . . . . Redundancy Module Fault Codes and Display Messages . . . . . . . . Recovery Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Table of Contents Appendix G Enhanced Redundancy Revision History Changes to This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
Table of Contents Notes: 12 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 13
Preface This publication provides this information specific to enhanced redundancy systems: • Design and planning considerations • Installation procedures • Configuration procedures • Maintenance and troubleshooting methods This publication is designed for use by anyone responsible for planning and implementing a ControlLogix® enhanced redundancy system: • Application engineers • Control engineers • Instrumentation technicians The contents of this publication are for those who already have an understanding
PAGE 14
Preface The following publications provide specific information about communication module connections. Table 3 - Additional Documentation Resources Description 1756 Communication Modules Specifications Technical Data, publication 1756-TD003 Describes Ethernet communication module specifications. ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001 Describes ControlNet modules and how to use ControlNet modules with a Logix5000 controller.
PAGE 15
Chapter 1 About Enhanced Redundancy Systems Topic Page Features of the ControlLogix Enhanced Redundancy System 16 Enhanced Redundancy System Components 17 Enhanced Redundancy System Operations 19 Restrictions 22 The ControlLogix Enhanced Redundancy System is a system that provides greater availability because it uses a redundant chassis pair to maintain process operation when events, such as a fault on a controller, occur that stop process operation on nonredundant systems.
PAGE 16
Chapter 1 About Enhanced Redundancy Systems Features of the ControlLogix Enhanced Redundancy System The software and hardware components required to configure and use a ControlLogix enhanced redundancy system provide these features: • Redundancy module speeds of up to 1000 Mbps when using a 1756RM2/A module with another 1756-RM2/A module. Redundancy module speeds up to 100 Mbps when using a 1756-RM/A with another 1756-RM/A module, and a 1756-RM/B module with another 1756-RM/ B module.
PAGE 17
About Enhanced Redundancy Systems Chapter 1 Features Not Supported • • • • • Any motion feature Any SIL3 functional safety feature within the redundancy controllers Firmware Supervisor Event Tasks Firmware revision 19.052 for 1756-L7x controller IMPORTANT For Ethernet modules, signed and unsigned firmware are available. Signed modules provide the assurance that only validated firmware can be upgraded into a module. Signed and unsigned firmware: • Both signed and unsigned firmware are available.
PAGE 18
Chapter 1 About Enhanced Redundancy Systems I/O Modules in Enhanced Redundancy Systems In an enhanced redundancy system, you can use only I/O modules in a remote chassis. You cannot use I/O modules in the redundant chassis pair. This table describes differences in network use for I/O in enhanced redundancy systems. Remote I/O Module Placement Available with Enhanced System, Revision 19.052, 19.053, or 20.054 Available with Enhanced System, Revision 16.
PAGE 19
About Enhanced Redundancy Systems Enhanced Redundancy System Operations Chapter 1 Once the redundancy modules in the redundant chassis pair are connected and powered, they determine which chassis is the primary chassis and which is the secondary chassis. The redundancy modules in both the primary and secondary chassis monitor events that occur in each of the redundant chassis. If certain faults occur in the primary chassis, the redundancy modules execute a switchover to the unfaulted, secondary chassis.
PAGE 20
Chapter 1 About Enhanced Redundancy Systems Switchovers During redundant system operation, if certain conditions occur on the primary chassis, primary control is switched to the secondary chassis.
PAGE 21
About Enhanced Redundancy Systems Chapter 1 HMI Blind Time Reduction on Ethernet During a Switchover HMI Blind Time is the time during a switchover from primary to secondary, when tag data from the controller is unavailable for reading or writing. HMI Blind Time is associated with visualizing process operations from an HMI; however, it is applicable to any software that uses tag data, such as data loggers, alarming systems, or historians. Reducing HMI Blind Time is important to avoid shutdowns.
PAGE 22
Chapter 1 About Enhanced Redundancy Systems Restrictions There are restrictions that you must consider when using an enhanced redundancy system. Most of these restrictions apply to all enhanced redundancy system revisions. Exceptions are noted: • The 1756-RM2/A or 1756-RM2XT modules can be used only with other 1756-RM2/A or 1756-RM2XT modules. You cannot mix 1756-RM2/A and 1756-RM2XT modules with 1756-RM/A, 1756-RM/B, or 1756RMXT modules. • Please note that firmware revision 19.
PAGE 23
Chapter 2 Design an Enhanced Redundancy System Topic Page Components of an Enhanced Redundancy System 24 Redundant Chassis 28 Controllers in Redundant Chassis 29 Redundancy Modules in Redundant Chassis 31 Communication Modules in Redundant Chassis 32 Power Supplies and Redundant Power Supplies in Enhanced Redundancy Systems 34 ControlNet Networks with Redundant Systems 38 Other Communication Networks 42 Other Communication Networks 42 I/O Placement 44 1715 Redundant I/O Systems 44
PAGE 24
Chapter 2 Design an Enhanced Redundancy System Components of an Enhanced Redundancy System The central components of a ControlLogix enhanced redundancy system are those in the redundant chassis pair. You can connect other system components to the redundant chassis pair. However, the redundant chassis pair, and the components within it, provide redundant communication and control features. This table lists the components available with enhanced redundancy systems.
PAGE 25
Design an Enhanced Redundancy System Chapter 2 Table 4 - Components Available for Use in a Redundant Chassis Pair Product Type Cat. No. Description Controllers 1756-L61, 1756L62, 1756-L63, 1756-L64 ControlLogix controllers 1756-L63XT ControlLogix-XT controller 1756-L65 ControlLogix controller This component is available with enhanced redundancy systems, revision 19.052 or later.
PAGE 26
Chapter 2 Design an Enhanced Redundancy System This graphic shows an example ControlLogix enhanced redundancy system, revision 19.053 or later, that uses EtherNet/IP networks. Figure 1 - Example ControlLogix Enhanced Redundancy System, Revision 19.
PAGE 27
Design an Enhanced Redundancy System Chapter 2 This graphic shows an example ControlLogix enhanced redundancy system, revision 19.053 or later, that uses ControlNet networks. Figure 2 - Example ControlLogix Enhanced Redundancy System, Revision 19.
PAGE 28
Chapter 2 Design an Enhanced Redundancy System Redundant Chassis You can use any ControlLogix or ControlLogix-XT chassis in a redundant chassis pair as long as the two chassis used are the same size. For example, if the primary chassis in your redundant chassis pair uses a 1756-A4 chassis, the secondary chassis must use a 1756-A4 chassis. You can use the 1756-A4LXT chassis with the enhanced redundancy system, revision 19.052 or later.
PAGE 29
Design an Enhanced Redundancy System Chapter 2 Controllers in Redundant Chassis Remember these points when placing controllers in the redundant chassis pair: • Controllers are typically included, but not required, in enhanced redundancy systems. • The differences between controller types are described in this table.
PAGE 30
Chapter 2 Design an Enhanced Redundancy System • Each controller must have enough I/O memory to store twice the amount of I/O memory used. To check the I/O memory used and available, access the Memory tab of the Controller Properties dialog box in RSLogix 5000 software. For more information about data and I/O memory, see Knowledgebase Answer ID 28972.
PAGE 31
Design an Enhanced Redundancy System Chapter 2 Plan for Controller Connections Consider these conditions when planning controller connection use: • 1756-L6x controllers provide 250 total connections. • 1756-L7x controllers provide 500 total connections. If you use the redundant controller at, or very near the connection limits, you can experience difficulty synchronizing your chassis.
PAGE 32
Chapter 2 Design an Enhanced Redundancy System Communication Modules in Redundant Chassis Remember these points when placing ControlLogix ControlNet and EtherNet/IP communication modules in the redundant chassis pair: • You must use enhanced communication modules in enhanced redundancy systems. Enhanced communication modules contain a ‘2’ in their catalog number. For example, the 1756-EN2T module. Standard ControlNet and EtherNet/IP communication modules are not supported.
PAGE 33
Design an Enhanced Redundancy System Chapter 2 Plan for Communication Module Connections A CIP connection is a point-to-point communication mechanism used to transfer data between a producer and a consumer. These are examples of CIP connections: • Logix5000 controller message transfer to Logix5000 controller • I/O or produced tag • Program upload • RSLinx DDE/OPC client • PanelView™ polling of a Logix5000 controller ControlLogix ControlNet communication modules provide 131 total CIP connections.
PAGE 34
Chapter 2 Design an Enhanced Redundancy System Power Supplies and Redundant Power Supplies in Enhanced Redundancy Systems You can use any of the standard or redundant power supplies listed in Components Available for Use in a Redundant Chassis Pair on page 24 in an enhanced redundancy system. Redundant Power Supplies Typically, enhanced redundancy systems use standard power supplies.
PAGE 35
Design an Enhanced Redundancy System EtherNet/IP Networks with Redundant Systems Chapter 2 The use of EtherNet/IP networks in an enhanced redundancy system is primarily dependent on your system revision. IMPORTANT A remote chassis can be accessed over an EtherNet/IP network using any EtherNet/IP module that works in a nonredundant chassis with no additional firmware requirement with the following exception.
PAGE 36
Chapter 2 Design an Enhanced Redundancy System IP Address Swapping EtherNet/IP communication modules can use IP address swapping to swap IP addresses during a switchover. You must use this feature to use Ethernet I/O connections. For more information on IP address swapping, see Chapter 5, Configure the ControlNet Network on page 93. Unicast Functionality Enhanced redundancy systems support unicast produced tags. Unicast consumed tags are not supported in enhanced redundancy systems.
PAGE 37
Design an Enhanced Redundancy System Chapter 2 This example graphic shows the recommended method to connect an HMI to a redundant chassis pair if connection drops are a concern in your application. In this graphic, the remote chassis contains I/O modules in addition to the EtherNet/IP and ControlNet communication modules. The I/O modules are not required and included here for example purposes only.
PAGE 38
Chapter 2 Design an Enhanced Redundancy System ControlNet Networks with Redundant Systems ControlNet networks are used to connect redundant control chassis to remote I/O and to other devices in the system. IMPORTANT A remote chassis can be accessed over a ControlNet network using any ControlNet module that works in a nonredundant chassis with no additional firmware requirement.
PAGE 39
Design an Enhanced Redundancy System Chapter 2 Assign Lowest Node Numbers to Remote ControlNet Modules Do not assign the lowest ControlNet node addresses to ControlNet modules in the redundant chassis pair. If you assign the lowest ControlNet node addresses to ControlNet modules in the redundant chassis pair, you can experience these system behaviors: • Upon a switchover, you can lose communication with I/O modules, produced tags, and consumed tags.
PAGE 40
Chapter 2 Design an Enhanced Redundancy System Reserve Consecutive Node Addresses for Partner Modules Where ControlNet modules are used as partners in redundant chassis, plan consecutive node numbers for those partnered modules. Plan for consecutive node addresses because the redundant system automatically assigns the consecutive node address to the secondary ControlNet module.
PAGE 41
Design an Enhanced Redundancy System Chapter 2 Redundant ControlNet Media The use of redundant ControlNet media helps to prevent a loss of communication if a trunkline or tap is severed or disconnected.
PAGE 42
Chapter 2 Design an Enhanced Redundancy System Other Communication Networks You can use only EtherNet/IP and ControlNet networks, and corresponding modules, in enhanced redundancy systems. IMPORTANT Do not use the redundant chassis to bridge between networks. Bridging through the redundant chassis to the same or different networks, or routing messages through redundant chassis is not supported. You can bridge to other communication networks outside of the redundant chassis.
PAGE 43
Design an Enhanced Redundancy System Chapter 2 You can bridge these networks via a remote chassis: • ControlNet • DeviceNet • EtherNet/IP • Universal Remote I/O • Data Highway Plus This table indicates what system components can be used with each network connected to a redundant system.
PAGE 44
Chapter 2 Design an Enhanced Redundancy System I/O Placement In an enhanced redundancy system, you can place I/O modules in these locations: • Same ControlNet network as redundant controllers and communication modules • Same EtherNet/IP network as redundant controllers and communication modules • DeviceNet network connected via a bridge • Universal Remote I/O network connected via a bridge IMPORTANT You cannot install I/O modules in the redundant chassis pair.
PAGE 45
Design an Enhanced Redundancy System Chapter 2 Figure 10 - Example of I/O Placement Options Workstation EtherNet/IP EtherNet/IP Switch Primary Chassis Secondary Chassis CH2 CH1 OK CH2 CH1 OK EtherNet/IP Bridging Chassis 1734 POINT I/O 1715 Redundant I/O ControlNet DeviceNet Device Control Tower 1771 Chassis with 1771-ASB DeviceNet Universal Remote I/O Rockwell Automation Publication 1756-UM535D-EN-P - November 2012 45
PAGE 46
Chapter 2 Design an Enhanced Redundancy System Using HMI Depending on the network used to connect the redundant system to HMIs, plan for certain placement and configuration requirements. You can connect an HMI to a primary chassis over either of these networks: • EtherNet/IP • ControlNet HMI Connected via an EtherNet/IP Network This table describes redundant system considerations specific to the HMI being used on the EtherNet/IP network.
PAGE 47
Design an Enhanced Redundancy System Chapter 2 HMI Connected via a ControlNet Network This table describes redundant system considerations specific to the HMI being used on the ControlNet network. Type of HMI Used Considerations • PanelView Standard terminal • PanelView 1000e or PanelView 1400e terminal • If your HMI communicates via unscheduled communication, use four terminals per controller.
PAGE 48
Chapter 2 Design an Enhanced Redundancy System Connection from HMI Over a ControlNet Network shows an example of connecting an HMI to a primary controller over a ControlNet network.
PAGE 49
Design an Enhanced Redundancy System Firmware Requirements Chapter 2 If you are using an enhanced redundancy system, use only enhanced redundancy system firmware. These are the enhanced redundancy system firmware-revision bundles: • 16.054Enh • 16.080Enh • 16.081Enh • 16.081_kit1 • 19.052Enh • 19.053Enh • 19.053_kit1 • 20.054 • 20.054_kit1 To download the most recent enhanced redundancy system firmware bundle, go to http://www.rockwellautomation/support.com.
PAGE 50
Chapter 2 Design an Enhanced Redundancy System Optional Software Software in addition to that listed as required software can be needed depending on your enhanced redundancy system program, configuration, and components. Optional software you might need is listed in this table.
PAGE 51
Chapter 3 Install the Enhanced Redundancy System Before You Begin Topic Page Before You Begin 51 Install an Enhanced Redundancy System 53 Step 1: Install the Software 53 Step 2: Install the Hardware 54 Step 3: Connect the Redundancy Modules via a Fiber-optic Cable 63 Step 4: Update Redundant Chassis Firmware 67 Step 5: Designate the Primary and Secondary Chassis 71 Complete these tasks before you install the enhanced redundancy system: • Verify that you have the components required to in
PAGE 52
Chapter 3 Install the Enhanced Redundancy System 2. To begin the hardware installation, determine the location of your modules in the system’s chassis. Plug in the communication modules, controller and redundancy modules into the chassis, matching partners slot for slot. See Step 2: Install the Hardware on page 54. Install the following: • The first chassis and power supply, see page 54. • The first chassis communication modules, see page 56. a.
PAGE 53
Install the Enhanced Redundancy System Install an Enhanced Redundancy System Chapter 3 The following steps detail the installation process for an enhanced redundancy system. They also explain how to install the redundant modules. These steps include the following. 1. Installing the software 2. Installing the hardware 3. Connecting the fiber-optic communication cable to the redundancy modules 4. Updating the firmware 5.
PAGE 54
Chapter 3 Install the Enhanced Redundancy System IMPORTANT When using the 1756-RM2/A or 1756-RM2XT module, you must use version 8.01.05 or later of the RMCT. TIP When the redundancy module firmware is upgraded, the RMCT is updated. The RMCT automatically uses the version that is compatible with the redundancy module firmware revision installed. Add the EDS Files Some modules have the EDS files already installed.
PAGE 55
Install the Enhanced Redundancy System Chapter 3 The redundancy module prevents certain redundancy operations, such as Qualification, if incompatible modules reside in the redundant-control chassis pair. IMPORTANT For best performance, place the redundancy module in the chassis as close as possible to the controller.
PAGE 56
Chapter 3 Install the Enhanced Redundancy System Install the Communication Modules Use the installation information provided with the communication modules to install them in an enhanced redundancy system. Table 10 - Communication Module Installation Product Type Cat. No.
PAGE 57
Install the Enhanced Redundancy System Chapter 3 Install the Redundancy Module You must install one redundancy module in each chassis planned for your system. Available modules are as follows: • 1756-RM2/A • 1756-RM2XT • 1756-RM/A • 1756-RM/B • 1756-RMXT IMPORTANT Do not connect the primary redundancy module to the secondary redundancy module until all other components used in the redundant chassis pair are installed. IMPORTANT Keep the redundancy module as close as possible to the controller module.
PAGE 58
Chapter 3 Install the Enhanced Redundancy System Environment and Enclosure ATTENTION: This equipment is intended for use in a Pollution Degree 2 industrial environment, in overvoltage Category II applications (as defined in IEC 60664-1), at altitudes up to 2000 m (6562 ft) without derating. This equipment is not intended for use in residential environments and may not provide adequate protection to radio communication services in such environments. This equipment is supplied as open-type equipment.
PAGE 59
Install the Enhanced Redundancy System Chapter 3 ATTENTION: This equipment is not resistant to sunlight or other sources of UV radiation. WARNING: • This equipment must be installed in an enclosure providing at least IP54 protection when applied in Zone 2 environments. • This equipment shall be used within its specified ratings defined by Rockwell Automation. • This equipment must be used only with ATEX certified Rockwell Automation backplanes.
PAGE 60
Chapter 3 Install the Enhanced Redundancy System North American Hazardous Location Approval The following information applies when operating this equipment in hazardous locations. Products marked "CL I, DIV 2, GP A, B, C, D" are suitable for use in Class I Division 2 Groups A, B, C, D, Hazardous Locations and nonhazardous locations only. Each product is supplied with markings on the rating nameplate indicating the hazardous location temperature code.
PAGE 61
Install the Enhanced Redundancy System Chapter 3 A redundant system is comprised of two ControlLogix redundancy modules working together that supervise the operating states and state transitions that establish the basic framework for redundancy operations. The redundant pairs provide a bridge between chassis pairs that let other modules exchange control data and synchronize their operations. This illustration identifies the external features of the module.
PAGE 62
Chapter 3 Install the Enhanced Redundancy System 1756-RM/A or 1756-RM/B Module Figure 13 - 1756-RM/A or RM/B and 1756-RMXT Modules 1756-RMXT Module Top View Top View Front View Front View Status Indicators Status Indicators Redundancy Module PRI COM OK Side View Side View LC Singlemode Connector Backplane Connector Bottom View 44487 LC Singlemode Connector Backplane Connector Bottom View 31941-M To install the redundancy module, follow these steps. 1.
PAGE 63
Install the Enhanced Redundancy System Chapter 3 Install the Second Chassis Once the first chassis and its components are installed, you can install the second chassis of the redundant chassis pair.
PAGE 64
Chapter 3 Install the Enhanced Redundancy System The cable connection is made at the bottom of the module in a downward orientation. There is enough space between the transmit and receive connectors so you can use the LC connector coupler. Using this coupler keeps the fiber-optic cable from bending so you can connect and disconnect the cable without removing the module from the chassis.
PAGE 65
Install the Enhanced Redundancy System Chapter 3 Connect the Fiber-optic Communication Cable to Redundant Channels Follow this procedure to install the communication cable to redundant channels for the 1756-RM2/A module. IMPORTANT The redundancy module communication cable contains optical fibers. Avoid making sharp bends in the cable. Install the cable in a location where it will not be cut, run over, abraded, or otherwise damaged. 1.
PAGE 66
Chapter 3 Install the Enhanced Redundancy System Connect the Fiber-optic Communication Cable to Single Channels Follow this procedure to install the communication cable. IMPORTANT The redundancy module communication cable contains optical fibers. Avoid making sharp bends in the cable. Install the cable in a location where it will not be cut, run over, abraded, or otherwise damaged. 1. Remove the black protective plug on the first redundancy module in the redundant chassis pair. 2.
PAGE 67
Install the Enhanced Redundancy System Chapter 3 Fiber-optic Cable If you choose to make your own fiber-optic cables, consider the following: • Fiber-optic Communication Cable Specifications Attribute 1756-RM2/A 1756-RM2XT 1756-RM/A or 1756-RM/B 1756-RMXT Temperature, operating 0…60 °C (32…140 °F) -25…70 °C (-13…158 °F) 0…60 °C (32…140 °F) -25…70 °C (-13…158 °F) Connector type LC-type (fiber-optic) Cable type 8.
PAGE 68
Chapter 3 Install the Enhanced Redundancy System IMPORTANT Redundancy module firmware contained in the enhanced redundancy system firmware bundle is designed for use with the 1756-RM, 1756-RM2/A, 1756RMXT, and 1756-RM2XT redundancy modules. Upgrade the Firmware in the First Chassis Complete these steps to upgrade the firmware in the first chassis. 1. Apply power to the chassis. Logix5563 Redundancy Module 44490 2. Set the mode switch on the controller to REM.
PAGE 69
Install the Enhanced Redundancy System Chapter 3 3. Wait for the redundancy module to complete its start-up scroll messages. Check Module and status indicators. Wait 45 seconds before you begin updating the 1756-RM firmware. During this time, the redundancy module conducts internal operations to prepare for an update. Power Supply indicator is green.
PAGE 70
Chapter 3 Install the Enhanced Redundancy System 5. Select the module’s catalog number (upgrade the redundancy module first) and click Next. IMPORTANT The 1756-RM2/A module uses different firmware than the 1756-RM and 1756RMXT modules. 1756-RM/B 1756-RM2/A 6. Expand the network driver to locate the redundancy module or module you are upgrading. 7. Select the module and click OK. 8. Select the firmware revision you want to update to and click Next. 9. Click Finish. A confirmation dialog box appears.
PAGE 71
Install the Enhanced Redundancy System IMPORTANT Chapter 3 This can take a few minutes. The system can look like it is not doing anything, but it is. When the update is complete, the Update Status dialog box appears and indicates that the update has successfully completed. 11. Click OK. 12. Verify that the redundancy module status displays PRIM, indicating a successful upgrade. 13. Complete steps 4…12 for each module in the chassis.
PAGE 72
Chapter 3 Install the Enhanced Redundancy System Complete these steps to designate the primary and secondary chassis of a redundant pair. 1. Verify that power is removed from both chassis. 2. Apply power to the chassis you want to designate as the primary chassis and wait for the module’s status indicators to display PRIM. 3. Apply power to the chassis you want to designate as the secondary chassis. 4.
PAGE 73
Install the Enhanced Redundancy System Chapter 3 After Designation When you first apply power to the designated primary and secondary chassis, compatibility checks are carried-out between the redundant chassis. Then, because the default Auto-Synchronization parameter is set at Always, qualification begins. TIP While the qualification occurs, the module status display transitions from DISQ (disqualified) to QFNG (qualifying) to SYNC (synchronized).
PAGE 74
Chapter 3 Install the Enhanced Redundancy System Qualification Status via the RMCT To view the qualification attempt, access the Synchronization or Synchronization Status tabs of the RMCT. These tabs provide information about qualification attempts and redundant chassis compatibility. For more information about using the RMCT, see Chapter 6, Configure the Redundancy Modules on page 105.
PAGE 75
Install the Enhanced Redundancy System Chapter 3 Reset the Redundancy Module There are two ways to reset the module. • Cycle power to the chassis • Remove the module from the chassis and reinsert the module IMPORTANT Only choose to cycle power to the chassis if you will not lose control of your process. Remove or Replace the Redundancy Module To remove or replace the redundancy module, follow these steps. 1. Push on upper and lower module tabs to disengage them. 2. Slide the module out of the chassis.
PAGE 76
Chapter 3 Install the Enhanced Redundancy System Notes: 76 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 77
Chapter 4 Configure the EtherNet/IP Network Requested Packet Interval Topic Page Requested Packet Interval 77 Use IP Address Swapping 77 Use CIP Sync 81 Use Produce/Consume Connections 84 Configure EtherNet/IP Communication Modules in a Redundant System 85 Use An Enhanced Redundancy System in a Device-level Ring Topology 87 When using revisions earlier than 20.054, the RPI for I/O connections in a redundancy-enabled controller tree must be less than or equal to 375 ms.
PAGE 78
Chapter 4 Configure the EtherNet/IP Network Determine Use of IP Address Swapping Depending on your EtherNet/IP network configuration, you can choose to use IP address swapping between your partnered EtherNet/IP communication modules in the event of a switchover.
PAGE 79
Configure the EtherNet/IP Network Chapter 4 When an enhanced redundancy system begins operating, the primary EtherNet/IP communication module uses the IP address assigned during initial configuration. The secondary EtherNet/IP communication module automatically changes its IP address to thenext highest value. When a switchover occurs, the EtherNet/IP communication modules swap IP addresses. For example, if you assign IP address 192.168.1.
PAGE 80
Chapter 4 Configure the EtherNet/IP Network Static versus Dynamic IP Addresses We recommend that you use static IP addresses on EtherNet/IP communication modules in enhanced redundancy system. ATTENTION: If you use dynamic IP addresses and a power outage, or other network failure occurs, modules using dynamic IP addresses can be assigned new addresses when the failure is resolved.
PAGE 81
Configure the EtherNet/IP Network Use CIP Sync Chapter 4 Beginning with enhanced redundancy system revision 19.052 or later, you can use CIP Sync technology. CIP Sync technology provides a mechanism to synchronize clocks between controllers, I/O devices, and other automation products in your architecture with minimal user intervention. CIP Sync technology uses Precision Time Protocol (PTP) to establish a Master/ Slave relationship among the clocks for each CIP Sync-enabled component in the system.
PAGE 82
Chapter 4 Configure the EtherNet/IP Network • If the primary controller is the Grandmaster, the enhanced redundancy system automatically manages the CIP Sync clock attributes so that the controller in the primary chassis is always set to be the Grandmaster instead of the secondary controller. This clock management ensures a change to a new Grandmaster when the redundancy system switches over.
PAGE 83
Configure the EtherNet/IP Network Chapter 4 This figure shows an example enhanced redundancy system, revision 19.052 or later, using CIP Sync technology. Use of ControlNet is not required when using CIP Sync technology in an enhanced redundancy system. It is included in this figure for example purposes. Figure 20 - Enhanced Redundancy System, Revision 19.
PAGE 84
Chapter 4 Configure the EtherNet/IP Network Use Produce/Consume Connections Beginning with enhanced redundancy system, revision 19.053 or later, you can use produce/consume connections over an EtherNet/IP network. Controllers let you produce (broadcast) and consume (receive) system-shared tags. TIP When using 1756-L7x controllers in your system, you must use revision 19.053 or later.
PAGE 85
Configure the EtherNet/IP Network Configure EtherNet/IP Communication Modules in a Redundant System Chapter 4 IMPORTANT If controllers in the redundant chassis pair produce tags over an EtherNet/IP network that controllers in remote chassis consume, the connection from the remote controller to the redundant controller can briefly drop during a switchover. This anomaly occurs if the EtherNet/IP communication modules in the remote chassis do not use specific firmware revisions.
PAGE 86
Chapter 4 Configure the EtherNet/IP Network Options for Setting the IP Addresses of EtherNet/IP Communication Modules By default, ControlLogix EtherNet/IP communication modules ship with the IP address set to 999 and with Bootstrap Protocol (BOOTP)/Dynamic Host Configuration Protocol (DHCP)-enabled.
PAGE 87
Configure the EtherNet/IP Network Use An Enhanced Redundancy System in a Device-level Ring Topology Chapter 4 A DLR network is a single-fault tolerant ring network intended for the interconnection of automation devices. This topology is implemented at the device level because the use of EtherNet/IP embedded switch technology embeds switches into the end devices themselves. No additional switches are required.
PAGE 88
Chapter 4 Configure the EtherNet/IP Network 2. Back-up Supervisor Node - An optional node that behaves like a ring node unless the active supervisor node cannot execute required tasks. At that point, the back-up node becomes the active supervisor node. • Ring Node - A node that processes data transmitted over the network or passes the data to the next node on the network.
PAGE 89
Configure the EtherNet/IP Network Chapter 4 During normal operation, one of the active supervisor node’s network ports is blocked for DLR protocol frames. However, the active supervisor node continues to send beacon frames out of both network ports to monitor network health. The graphic below shows the use of beacon frames sent from the active ring supervisor.
PAGE 90
Chapter 4 Configure the EtherNet/IP Network This graphic shows an example of an operating DLR network that includes an enhanced redundancy system.
PAGE 91
Configure the EtherNet/IP Network Chapter 4 Complete these steps to construct and configure the example DLR network. 1. Install and connect devices on the DLR network but leave at least one connection open. IMPORTANT When you initially install and connect devices on the DLR network, leave at least one connection open, that is, temporarily omit the physical connection between two nodes on the DLR network.
PAGE 92
Chapter 4 Configure the EtherNet/IP Network 2. Configure and enable one active supervisor and any back-up nodes on the network. Use either of these tools to configure and enable supervisor nodes on a DLR network: • RSLogix 5000 programming software • RSLinx Classic communication software 3. Complete the physical connections on the network to establish a complete and fully functioning DLR network. This figure shows the example DLR network on page 91 with all physical connections complete.
PAGE 93
Chapter 5 Configure the ControlNet Network Produce/Consume Connections Topic Page Produce/Consume Connections 93 Network Update Time 95 Use a Scheduled or Unscheduled Network 97 Schedule a New Network 98 Update an Existing Scheduled Network 100 Check the Network Keeper States 101 You can use produce/consume connections over a ControlNet network. Controllers let you produce (broadcast) and consume (receive) system-shared tags.
PAGE 94
Chapter 5 Configure the ControlNet Network Keep these points in mind when you use produced and consumed connections over a ControlNet network in an enhanced redundancy system: • During a switchover, the connection for tags that are consumed from a redundant controller can drop briefly. – The data does not update. – The logic acts on the last data that it received. After the switchover, the connection is reestablished and the data begins to update again.
PAGE 95
Configure the ControlNet Network Network Update Time Chapter 5 The network update time (NUT) that you specify for your redundant system impacts your system performance and your switchover response time. Typical NUTs used with redundant systems range from 5…10 ms. NUTs with Multiple ControlNet Networks You can choose to use multiple ControlNet networks with your enhanced redundancy system.
PAGE 96
Chapter 5 Configure the ControlNet Network Use this table to determine the compatible NUTs for your system.
PAGE 97
Configure the ControlNet Network Use a Scheduled or Unscheduled Network Chapter 5 It is up to the user to decided between using a scheduled or unscheduled network. Use a Scheduled Network Schedule or reschedule your ControlNet network when you are executing these tasks: • Commissioning a new redundant system. • Adding a new chassis of remote ControlLogix I/O that is set to use the Rack Optimized communication format. • Adding any remote I/O besides ControlLogix I/O.
PAGE 98
Chapter 5 Configure the ControlNet Network Add Remote ControlNet Modules While Online If you are adding a remote I/O chassis comprised of a ControlLogix ControlNet module and ControlLogix I/O while your redundant system is running (online), make these considerations: • Do not use Rack Optimized communication formats. The ControlNet module and I/O must be configured for direct connections. • For each remote I/O module used, plan for one direct connection to be used.
PAGE 99
Configure the ControlNet Network Chapter 5 8. In the Network Parameters tab, enter the parameters that are appropriate for your system. Parameter Specify Network Update Time (ms) The minimum repetitive interval when data is sent over the ControlNet network. Max Scheduled Address The highest node number that uses scheduled communication on the network. Max Unscheduled Address The highest node number that you use on the network. Media Redundancy The ControlNet channels you are using.
PAGE 100
Chapter 5 Configure the ControlNet Network Update an Existing Scheduled Network If you are adding the redundant chassis to an existing ControlLogix system that uses a ControlNet network, complete these steps to update the existing ControlNet network. 1. Turn on the power to each chassis. 2. Start RSNetWorx for ControlNet software. 3. From the File menu, choose Open. 4. Select the file for the network and click Open. 5. From the Network menu, choose Online. 6. Click Edits Enabled. 7.
PAGE 101
Configure the ControlNet Network Check the Network Keeper States Chapter 5 After you schedule your ControlNet network, check the states of keeper-capable nodes. Checking the status of keeper-capable nodes is important because if a major network disruption occurs, the keepers provide network configuration parameters required to recover. For more information about keepers and their function in a ControlNet network, see the ControlNet Modules in Logix5000 Control Systems User Manual, publication CNET-UM001.
PAGE 102
Chapter 5 Configure the ControlNet Network 4. Verify that all of the nodes on the network have the same keeper signature. Keeper signatures are all the same. TIP If the keeper signatures of partnered ControlNet modules are different, your redundant chassis may not synchronize. If the keeper signatures of your partnered ControlNet modules are different, update the keepers of the redundant ControlNet modules.
PAGE 103
Configure the ControlNet Network Chapter 5 To replace a ControlNet module that has been configured and scheduled on the ControlNet network, remove the existing module and insert a 1756-CN2/B, 1756-CN2R/B, or 1756-CN2RXT module. The module you are inserting must be unconfigured or have a keeper signature of all zeros. TIP To clear the keeper signature of a 1756-CN2, 1756-CN2R, or 1756-CN2RXT module, complete these steps. 1.Disconnect the module from the ControlNet network and remove it from the chassis.
PAGE 104
Chapter 5 Configure the ControlNet Network Notes: 104 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 105
Chapter 6 Configure the Redundancy Modules About the Redundancy Module Configuration Tool (RMCT) Topic Page About the Redundancy Module Configuration Tool (RMCT) 105 Determine if Further Configuration is Required 106 Use the RMCT 107 Module Info Tab 111 Configuration Tab 113 Synchronization Tab 116 Synchronization Status Tab 119 Event Log Tab 120 System Update Tab 130 System Event History 136 Using Dual Fiber Ports with the 1756-RM2/A Redundancy Module 138 The Redundancy Module C
PAGE 106
Chapter 6 Configure the Redundancy Modules The chassis platform configuration identifies the common operating platform of the modules in the redundant chassis and applies to all redundancy modules. It may be one of the following values depending on the redundancy release installed in the system and the type of communication modules running in the redundant chassis.
PAGE 107
Configure the Redundancy Modules Use the RMCT Chapter 6 To access and begin using the RMCT, launch RSLinx Classic software and browse to your redundancy module. Right-click the redundancy module and choose Module Configuration.
PAGE 108
Chapter 6 Configure the Redundancy Modules When you access the RMCT, the dialog box always indicates the status of the redundancy chassis in the bottom-left corner.
PAGE 109
Configure the Redundancy Modules Chapter 6 Identify the RMCT Version You must use a version of the RMCT that is compatible with your redundancy module firmware. Beginning with version 20.054, the redundancy module firmware reports back to the Redundancy Module Configuration Tool (RMCT) as to which version of the RMCT is compatible. In the case of an incompatibility, the RMCT will show only the Module Info tab and indicate the version that the firmware is compatible with.
PAGE 110
Chapter 6 Configure the Redundancy Modules The Module Configuration dialog box opens. 4. Right-click the title bar and choose About. The About dialog box opens and indicates the RMCT version. Update the RMCT Version The RMCT version that is compatible with your redundancy module firmware is packaged with the redundancy system firmware bundle.
PAGE 111
Configure the Redundancy Modules Module Info Tab Chapter 6 The Module Info tab of the RMCT provides a general overview of the redundancy module’s identification and status information. This status information is updated approximately once every two seconds. NOTE: Not all indicators are shown for 1756-RM/A and 1756-RM/B modules.
PAGE 112
Chapter 6 Configure the Redundancy Modules These parameters are indicated in the Module Info tab. Table 17 - Module Info Tab - Parameters Indicated Parameter Description Vendor Name of the redundancy module’s vendor. Product Type General product type of the redundancy module. Product Code CIP product code for the redundancy module. Revision Major and minor revision information for the redundancy module. Redundancy Module Serial Number Serial number of the redundancy module.
PAGE 113
Configure the Redundancy Modules Configuration Tab Chapter 6 Use the Configuration tab to set redundancy options and the module’s internal clock. After you modify a parameter, the Apply Workstation Time button becomes active.
PAGE 114
Chapter 6 Configure the Redundancy Modules Auto-Synchronization The first parameter in the Configuration tab is the Auto-Synchronization parameter. The value you set this parameter to determines a significant part of your redundant system behavior. TIP Verify that your Auto-Synchronization parameter is at the proper value before you make any changes to your redundant system. This helps prevent system errors.
PAGE 115
Configure the Redundancy Modules Chapter 6 Chassis ID The chassis ID parameter is used to assign a generic label to the chassis that house the redundancy modules. The available chassis labels are Chassis A and Chassis B. If you change the chassis label in the RMCT of the primary redundancy module, the secondary module and chassis are automatically assigned the other chassis label.
PAGE 116
Chapter 6 Configure the Redundancy Modules Synchronization Tab The Synchronization Tab provides commands for these options: • Changing the synchronization state of the system (synchronize or disqualify) • Initiating a switchover • Forcing the disqualified secondary to become the primary The commands available are described in the Commands in the Synchronization Tab section on page 117.
PAGE 117
Configure the Redundancy Modules Chapter 6 Commands in the Synchronization Tab These sections explain each redundancy command and the system conditions that are required for the command to be available. Command Description Synchronize Secondary This command forces the primary redundancy module to attempt synchronization with its partner.
PAGE 118
Chapter 6 Configure the Redundancy Modules Recent Synchronization Attempts Log This table describes the possible result and causes of synchronization states. Table 18 - Recent Synchronization Attempts Log - Result Interpretations Result Result Interpretation Undefined The result of the synchronization is unknown. No attempt since last powerup Synchronization has not been attempted since power was applied to the module. Success Full synchronization was successfully completed.
PAGE 119
Configure the Redundancy Modules Chapter 6 Table 19 - Synchronization Interpretation Cause Cause Interpretation Module Qual Request Synchronization was aborted because another synchronization request was received. The current synchronization has stopped so that the new synchronization request can be serviced. SYS_FAIL_L Deasserted Synchronization was aborted because one of the modules came out of a faulted or failed state.
PAGE 120
Chapter 6 Configure the Redundancy Modules Event Log Tab The Event Log tab provides a history of events that have occurred on the redundant chassis. These system events are indicated in the event logs: • Qualification stages entered and completed • Module insertion/removal • Firmware errors • Communication events and errors • Configuration changes • Other system events that affect qualification and synchronization IMPORTANT The events logged in this tab are not always indicative of an error.
PAGE 121
Configure the Redundancy Modules Chapter 6 Event Classifications Each event identified and logged is classified. You can use these classifications to identify the severity of the event and determine if additional action is required.
PAGE 122
Chapter 6 Configure the Redundancy Modules Use this table to determine what an event classification indicates and if corrective action is required. Table 21 - Classification Types Classification Type Description Action Required Configuration A redundancy module configuration parameter has been changed. For example, if you change the Auto-Synchronization parameter from Always to Never, an event classified as Configuration is logged. No corrective action is required.
PAGE 123
Configure the Redundancy Modules Chapter 6 Access Extended Information About an Event Events logged in the Event Log tab can have additional information available. To access additional information about an event, double-click an event listed in the log. Double-click to open extended information. Scroll to view details of other events. View the Description and Extended Data Definitions.
PAGE 124
Chapter 6 Configure the Redundancy Modules Interpret an Event’s Extended Information The information listed in this table can be provided (depending on the type of event) after you have accessed the Extended Information Definition dialog box.
PAGE 125
Configure the Redundancy Modules Chapter 6 3. In the Auto-Update area, click Off to keep the log from updating. 4. In the Partner Log area, click Close. This closes the event log of the partner module. 5. Select a single event or multiple events for which you want to export data. To select multiple events, select a start event, press SHIFT, and select an end event. 2 6. Click Export Selection. The Export Event Log dialog box opens. 7. Complete these steps on the Export Event Log dialog box. a.
PAGE 126
Chapter 6 Configure the Redundancy Modules 8. Click Export. The event log is exported. The log can take a few minutes to export. 9. If you want to export the secondary redundancy module log for a complete system view complete step 1…step 8. IMPORTANT 126 If you are exporting event data to provide to Rockwell Automation Technical Support to troubleshoot an anomaly, you must obtain the event logs for both the primary and secondary redundancy modules.
PAGE 127
Configure the Redundancy Modules Chapter 6 Export All Use this feature to automatically export all the available event log data for events in both of the redundancy modules of the redundant chassis pair. We recommend that you use this feature when troubleshooting system related anomalies, where the location of a fault could have occurred a lengthy period of time before the current event. Complete these steps to export event log data for a single event.
PAGE 128
Chapter 6 Configure the Redundancy Modules 7. Click Export. The event log is exported. The log can take a few minutes to export. Wait for this dialog box to appear. A .csv and a .dbg file is in the folder location specified. Make sure to provide both these files to Rockwell Automation Technical Support when troubleshooting an anomaly.
PAGE 129
Configure the Redundancy Modules Chapter 6 Clear a Fault You can use the Clear Fault feature on the Event Log tab to clear major faults that occur on a redundancy module. 2 2 2 2 2 2 2 2 2 2 2 2 2 2 With this feature, you can remotely restart the redundancy module without physically removing and reinserting it from the chassis. The module restart clears the fault. IMPORTANT Export all event and diagnostic data from the module before you clear major faults from the module.
PAGE 130
Chapter 6 Configure the Redundancy Modules System Update Tab Use of the commands in the System Update tab lets you perform firmware updates in the secondary chassis while the primary chassis remains in control. Reference the lock and switchover logs in this tab for update information when completing a firmware update. ATTENTION: When performing firmware updates by using commands in the System Update tab, redundancy is lost.
PAGE 131
Configure the Redundancy Modules Chapter 6 System Update Commands The three system update commands are available only when accessing a primary redundancy module. These commands are not available when accessing the secondary redundancy module.
PAGE 132
Chapter 6 Configure the Redundancy Modules Clicking the Lock for Update command initiates the locking process. The lock can take several minutes to finish. Monitor the System Update Lock Attempts log to determine when the lock is complete. In addition, the chassis status shown at the bottom-left of the dialog box changes from Primary with Disqualified Secondary to Primary Locked for Update. Figure 31 - Lock for Update Status Updates Lock initiated. Lock complete. Lock complete.
PAGE 133
Configure the Redundancy Modules Chapter 6 Initiate Locked Switchover The Initiate Locked Switchover command is available only when the chassis redundancy state is Primary with Locked Secondary. That is, the Initiate Locked Switchover is available only after the lock for update is complete. Clicking Initiate Locked Switchover results in your secondary chassis assuming control and becoming the new primary.
PAGE 134
Chapter 6 Configure the Redundancy Modules System Update Lock Attempts The System Update Lock Attempts is where attempts to lock the system are logged. This log displays the last four lock attempts and provides this information specific to each attempt: • Time and date • Status (for example, Locked or Abort) • Result (for example, System Locked or Invalid Response Received) The status indicated in the System Update Lock Attempts log can be any one of the states listed in this table.
PAGE 135
Configure the Redundancy Modules Chapter 6 Locked Switchover Attempts The Locked Switchover Attempts log provides information about the status of the last four locked switchover attempts. This log includes this information about each attempt: • Time and date • Status • Result The status indicated in the Locked Switchover Attempts log can be any one of the states listed in this table.
PAGE 136
Chapter 6 Configure the Redundancy Modules System Event History The System Event History tab provides a log of the last 10 major system events. The events logged here provide information specific to qualification, disqualification, switchovers, and redundancy module faults.
PAGE 137
Configure the Redundancy Modules Chapter 6 Edit a User Comment for a System Event To edit the User Comment associated with a system event, select the event and then click Edit. Then type your event description and click Accept Edit. Save System Event History If you want to save the system event log to the nonvolatile memory of the redundancy module, click Save System History at the bottom of the System Event tab. Saving this history can assist with troubleshooting the system at a later time.
PAGE 138
Chapter 6 Configure the Redundancy Modules Using Dual Fiber Ports with the 1756-RM2/A Redundancy Module The dual fiber ports of the 1756-RM2/A module constitute a redundant pair of communication channels between the partner 1756-RM2s in a redundant chassis pair. One of the channels is termed as 'ACTIVE', while the other channel is termed as 'REDUNDANT'. All data communication between the partner redundancy modules is conducted exclusively over the ACTIVE channel.
PAGE 139
Configure the Redundancy Modules Chapter 6 Monitoring and Repair Synchronization is preserved if the REDUNDANT channel has failed or is being repaired. The repair of the REDUNDANT channel can be performed online while the redundant chassis pair is running synchronized. To aid online repairs, the fiber cable connections and SFP transceiver can be removed and inserted under power. It is not mandatory to have the REDUNDANT channel connected between the two redundancy modules.
PAGE 140
Chapter 6 Configure the Redundancy Modules Notes: 140 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 141
Chapter 7 Program the Redundant Controller Configure the Redundant Controller Topic Page Configure the Redundant Controller 141 Crossloads, Synchronization, and Switchovers 144 Crossloads and Scan Time 149 Program to Minimize Scan Times 152 Program to Maintain Data Integrity 159 Program to Optimize Task Execution 163 Program to Obtain System Status 168 Program Logic to Run After a Switchover 170 Use Messages for Redundancy Commands 171 Set the Task Watchdog 175 Download the Project
PAGE 142
Chapter 7 Program the Redundant Controller 3. Click the redundancy tab and check Redundancy Enabled. 4. If you are going to complete edits to your redundant controller while online, see these sections for information about the parameters available in the Advanced settings: • Plan for Test Edits on page 183 • Reserve Memory for Tags and Logic on page 187 5. Click the Advanced tab. 6. Verify that Match Project to Controller is unchecked.
PAGE 143
Program the Redundant Controller Chapter 7 Verify this is not checked. You have completed the minimum configuration required for your redundant controllers.
PAGE 144
Chapter 7 Program the Redundant Controller Crossloads, Synchronization, and Switchovers Crossloading and synchronization points are points where the primary controller transfers data to the secondary controller. Crossload and synchronization points keep the secondary controller ready to assume control in the event of a fault on the primary. Before you begin programming your redundant controller, be aware of the impact of crossloads and synchronization on the execution of a program after a switchover.
PAGE 145
Program the Redundant Controller Chapter 7 Default Crossload and Synchronization Settings The default setting for a program in a redundant project is for a crossload to occur at the end of each program execution. However, for an equipment phase, the default is that the crossload not execute at the end of the phase. Before you change the default crossload and synchronization settings, read the sections that follow so you have a complete understanding of the implications.
PAGE 146
Chapter 7 Program the Redundant Controller Continuous Task with Crossloads at Each Program End This diagram demonstrates how programs set to crossload and synchronize at each program-end are executed after a switchover. As is shown, the new primary controller begins executing at the beginning of the program that was interrupted by the switchover. This is the switchover execution that occurs if you use the default crossload and synchronization setting for a program.
PAGE 147
Program the Redundant Controller Chapter 7 Multiple Periodic Tasks ATTENTION: If you use multiple periodic tasks, program all crucial outputs within the highest-priority task. Failure to program outputs in the highest-priority task can result in outputs changing state if a switchover occurs.
PAGE 148
Chapter 7 Program the Redundant Controller The diagram below shows a lower priority task that has not been completed and a switchover occurs. The lower priority task and programs are executed from the beginning of the program where the switchover occurred. This is because the program uses the default configuration and crossloads and synchronization points occur at the end of each program.
PAGE 149
Program the Redundant Controller Crossloads and Scan Time Chapter 7 It is important to plan for controller crossloads because the length of the crossloads affects the scan time of your program. A crossload is a transfer of data from the primary controller to the secondary controller and may occur at the end of each program or at the end of the last program in a task. The scan time of your program or phase is a total of the program execution time and the crossload time.
PAGE 150
Chapter 7 Program the Redundant Controller Redundancy Object Attributes for Crossload Times Before you complete calculations to estimate the crossload time, you need to use a Get System Value (GSV) instruction to read certain attributes of the redundancy object. These attributes are data transfer sizes measured in DINTs (4-byte words) and are used to calculate the estimated crossload time. TIP To get these attributes, you do not need to have the secondary chassis installed or operating.
PAGE 151
Program the Redundant Controller Chapter 7 Equation for Estimating Crossload Times After you have either the size of the last data transfer or the maximum size of data transferred, use this equation to estimate your controllers’ crossload time for each program. 1756-L6x Controllers Crossload time per sync point (ms) = (DINTs  0.00091) + 0.6 ms 1756-L7x Controllers The following equations apply when a 1756-L7x controller is paired with a redundancy module in both chassis in a redundancy system.
PAGE 152
Chapter 7 Program the Redundant Controller Program to Minimize Scan Times Because your system switchover time is impacted by your total program scan time, there are several aspects of your program that must be as efficient as possible to facilitate the fastest possible switchover. The sections that follow indicate methods of making your program more efficient to minimize your program scan time.
PAGE 153
Program the Redundant Controller Chapter 7 Minimize the Number of Programs When programming a redundant controller, use the fewest programs possible. Using the fewest programs possible is especially important if you plan to crossload data and synchronize the controllers after the execution of each program. If you need to crossload data at the end of each program, make these programming considerations to minimize the crossload impact on the program scan time: • Use only one or a few programs.
PAGE 154
Chapter 7 Program the Redundant Controller Manage Tags for Efficient Crossloads To program for more efficient crossloads of data and to reduce the amount of time required for a crossload to execute, manage your data tags as recommended in these sections. Delete Unused Tags Deleting unused tags reduces the size of the tag database. A smaller database takes less time to crossload.
PAGE 155
Program the Redundant Controller Chapter 7 Group Data Types Together in User-Defined Data Types When you create a User-Defined Data Type for use in your redundancy program, group like data types together. Grouping like data types compresses the data size and helps reduce the amount of data transferred during a crossload.
PAGE 156
Chapter 7 Program the Redundant Controller For example, if your application uses DINTs that you use only as constants to initialize your logic, BOOLs that you update every scan, and REALs that you update every second, you can create a separate User-Defined Data Type for each type of tag that is used at different points in the application.
PAGE 157
Program the Redundant Controller Chapter 7 Use Concise Programming Use these recommendations to create concise programming. Using concise programming makes your program execute faster and reduces your program scan time. Execute an Instruction Only when Needed We recommend that you execute instructions only when needed because each time an instruction writes a value to a tag, the tag is crossloaded to the secondary controller.
PAGE 158
Chapter 7 Program the Redundant Controller In addition to using preconditions, try to group instructions that can be preconditioned by the same instructions together. In this example, the four preconditions used in the two branches can be combined to precede the two branches. Doing so reduces the number of precondition instructions from four to two.
PAGE 159
Program the Redundant Controller Program to Maintain Data Integrity Chapter 7 When programming your redundant controllers, there are some instructions and techniques that may cause data loss or corruption when used.
PAGE 160
Chapter 7 Program the Redundant Controller Buffering Critical Data If you cannot place Array (File)/Shift instructions in the highest-priority task, consider using a buffer with Copy File (COP) and Synchronous Copy File (CPS) instructions to maintain the integrity of the array of data. The programming example shown here shows the use of a COP instruction to move data into a buffer array. The BSL instruction uses the data in that buffer array.
PAGE 161
Program the Redundant Controller Chapter 7 For example, if a higher priority task interrupts the logic shown in this example, the value of scan_count.ACC is sent to the secondary controller at the end of the program in the higher priority task. If a switchover occurs before the primary controller completes the EQU instruction, the new primary controller starts its execution at the beginning of the program and the EQU instruction misses the last value of scan_count.ACC.
PAGE 162
Chapter 7 Program the Redundant Controller Bind Dependent Instructions with UID and UIE Instructions If you cannot place scan-dependent instructions in the highest priority task, consider using the User Interrupt Disable (UID) and User Interrupt Enable (UIE) to prevent a higher priority task from interrupting the scan-dependent logic.
PAGE 163
Chapter 7 Program the Redundant Controller Program to Optimize Task Execution To make synchronization, crossloads, and HMI updates as fast as possible, make adjustments to the System Overhead Time Slice and the type of tasks used. These adjustments affect service communication tasks that take place during the time when the continuous task is not executing. This table lists some of the communication that takes place during an continuous task and service communication periods.
PAGE 164
Chapter 7 Program the Redundant Controller Specify a Larger System Overhead Time Slice The system overhead time slice specifies the percentage of time the controller devotes to servicing communication, excluding the time for periodic tasks. The controller interrupts the continuous task to service communication, and then resumes the continuous task. This table shows the ratio between executing the continuous task and servicing communication at various overhead time slices.
PAGE 165
Program the Redundant Controller Chapter 7 System Overhead Time Slice Examples This diagram illustrates a system where the System Overhead Time Slice is set to 20% (default). With this percentage, communication is serviced after every 4 ms of continuous task execution. Communication is serviced for up to 1 ms before the continuous task is restarted. Figure 48 - System Overhead Time Slice Set to 20% Legend: Task executes. Task is interrupted (suspended).
PAGE 166
Chapter 7 Program the Redundant Controller Change the System Overhead Time Slice To change the System Overhead Time Slice, access the Controller Properties dialog box and click the Advanced tab. You can enter your System Overhead Time Slice value. Options for During the Unused System Overhead Time Slice Enable the Run Continuous Task option (default setting) if you want the controller to revert to running the continuous task as soon as the communication servicing task has no pending activity.
PAGE 167
Program the Redundant Controller Chapter 7 Use Periodic Tasks If you have multiple tasks in your project, changing the System Overhead Time Slice does not affect how communication is serviced. To increase the time to service communication when multiple tasks are used, configure the periodic tasks such that more time might be available to service communication. TIP While you can use multiple periodic tasks in your redundant controller program, use the fewest number of tasks possible.
PAGE 168
Chapter 7 Program the Redundant Controller Example of Periodic Task Configurations Task Priority Execution Time Period Specified 1 Higher 20 ms 80 ms 2 Lower 30 ms 100 ms Total execution time: 50 ms In this example, the execution time of the highest priority task (Task 1) is significantly smaller than its period, that is, 20 ms is less than 80 ms, and the total execution time of all the tasks is significantly smaller than the specified period of the lowest priority task, that is, 50 ms is le
PAGE 169
Program the Redundant Controller Chapter 7 In the example below, the GSV instruction is used to obtain the chassis ID (that is, the chassis A or B designation) of the chassis that is functioning as the primary. The PhysicalChassisID value is stored in the PRIM_Chassis_ID_Now tag. The PhysicalChassisID value retrieved matches the Chassis ID indicated in the Controller Properties dialog box.
PAGE 170
Chapter 7 Program the Redundant Controller Program Logic to Run After a Switchover If your application requires certain logic or instructions to be executed after a switchover, then use programming and tags similar to that shown in this example. Figure 52 - Precondition Used to Run Logic After Switchover - Ladder Logic Add your switchover-dependent instructions here.
PAGE 171
Program the Redundant Controller Use Messages for Redundancy Commands Chapter 7 For some applications, you may want to program the controller to issue redundancy system commands via the redundancy modules. The sections that follow explain how to configure a MSG instruction to issue a redundancy command. Verify User Program Control For a MSG instruction to issue a command via the redundancy modules, the redundancy modules must be configured for user program control.
PAGE 172
Chapter 7 Program the Redundant Controller Configure the MSG Instruction Use the MSG configuration settings that correspond to the command you intend to issue to the redundancy modules. If you need to See page Initiate a Switchover 172 Disqualify the Secondary Chassis 174 Synchronize the Secondary Chassis 174 Set the Redundancy Module Date and Time 175 Initiate a Switchover To initiate a switchover, use the MSG instruction parameters listed in this table.
PAGE 173
Program the Redundant Controller Chapter 7 Use this table to when using MSG instructions during a switchover. Table 30 - MSG Instruction Behavior During a Switchover If the MSG instruction is Then From a redundant controller In a redundant controller, any MSG instruction that is in progress during a switchover experiences an error. (The ER bit of the instruction turns on.) After the switchover, normal communication resumes.
PAGE 174
Chapter 7 Program the Redundant Controller Disqualify the Secondary Chassis To disqualify the secondary chassis, use the MSG instruction parameters listed in this table.
PAGE 175
Program the Redundant Controller Chapter 7 Set the Redundancy Module Date and Time To set the wallclock time of the 1756-RM module, use the MSG instruction parameters listed in this table.
PAGE 176
Chapter 7 Program the Redundant Controller We recommend that you reevaluate the watchdog times in your application if either of these events occur: • A second controller is added to a redundancy chassis. • The application in a second controller that is already in the system is modified. Figure 54 - Watchdog Configured for Redundancy Switchover In the event of a watchdog timeout, a major fault (type 6, code 1) results.
PAGE 177
Program the Redundant Controller Chapter 7 Minimum Value for the Watchdog Time To set Watchdog time for your 1756-L6x controllers, use this table to determine which equation to use to calculate the time for each task. If Then use this equation Using ControlNet I/O ms (2 * maximum_scan_time) + 150 Using Ethernet I/O ms (2 * maximum _scan_time) + 100 The maximum_scan_time is the maximum scan time for the entire task when the secondary controller is synchronized.
PAGE 178
Chapter 7 Program the Redundant Controller Store a Redundancy Project to Nonvolatile Memory Use this procedure to store an updated project and firmware to the nonvolatile memory card of the controller. IMPORTANT The controllers use these nonvolatile memory cards. Cat. No.
PAGE 179
Program the Redundant Controller Chapter 7 Store a Project While the Controller is in Program or Remote Program Mode If you want to store your controller project in nonvolatile memory while your redundant system is not running, complete these steps. Before you begin, verify that a controller communication path has been specified and that you are able to go online with the primary controller. 1. Verify that the redundant chassis are synchronized. If they are not synchronized, synchronize them. 2.
PAGE 180
Chapter 7 Program the Redundant Controller 5. On the Synchronization tab, click Disqualify Secondary. 6. In RSLogix 5000 software, access the Controller Properties dialog box and click the Nonvolatile Memory tab. 7. Click Load/Store. 8. Click <-- Store and then click Yes. When the store is complete, we go online with the secondary controller. 9. Complete steps 6…8 to store the project in nonvolatile memory of the secondary controller. 10.
PAGE 181
Program the Redundant Controller Chapter 7 Store a Project While a System is Running If you want to store your controller project in nonvolatile memory while your redundant system is running, complete these steps. 1. Verify that the redundant chassis are synchronized. 2. In the RMCT, access the Configuration tab and set the AutoConfiguration parameter to Never. 3. In the Synchronization tab, click Disqualify Secondary. 4. Go online with the secondary controller.
PAGE 182
Chapter 7 Program the Redundant Controller Load a Project If you need to load a project from nonvolatile memory, you must first disqualify your redundancy system. You then load the project from the primary controller and resynchronize the redundant chassis once the load is complete. For details about loading a project from nonvolatile memory, see the Logix5000 Controllers Memory Card Programming Manual, publication 1756-PM017.
PAGE 183
Program the Redundant Controller Chapter 7 • A PIO to a primary controller may fail if a switchover occurs while the PIO is still in process. When the anomaly occurs and the PIO fails, you may see any of these errors: – Failed to import file 'c\...\xxx.L5x Object already exists – Failed to import file 'c\...\xxx.
PAGE 184
Chapter 7 Program the Redundant Controller Use this table to determine the Retain Test Edits on Switchover setting that suits your application.
PAGE 185
Program the Redundant Controller IMPORTANT Chapter 7 When using a 1756-L7x redundancy controller using version 19 software, and the Memory Usage slider is set all the way to Tags, the first synchronization attempt will be successful, but after switchover or disqualification, the next qualification attempt will fail, and one or more entries will appear in the secondary redundancy module event log with the following description: ‘(14) Error Setting Up Data Tracking.
PAGE 186
Chapter 7 Program the Redundant Controller Finalize Edits with Caution When you finalize edits to your program while online, the original program that existed before the changes were made is deleted. As a result, if the edits you finalize cause a fault on the primary controller, the new primary controller will also fault after the switchover. Before you finalize any edits to your program, test the edits to verify that faults do not occur.
PAGE 187
Program the Redundant Controller Chapter 7 Reserve Memory for Tags and Logic Depending on your redundant application, you may need to change the memory usage property for your redundant controller. The setting you specify impacts how the controller divides memory for tags and logic to be stored to the buffer during a crossload to the secondary controller. IMPORTANT For most applications, we recommend that the Memory Usage slider remain at its default position (center).
PAGE 188
Chapter 7 Program the Redundant Controller Notes: 188 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 189
Chapter 8 Monitor and Maintain an Enhanced Redundancy System Topic Page Tasks to Monitor the System 189 Controller Logging 189 Use Programming to Monitor System Status 190 Verify Date and Time Settings 191 Verify System Qualification 192 Check the ControlNet Module Status 197 Tasks to Monitor the System This chapter describes some of the key tasks to complete to monitor and maintain your enhanced redundancy system. Controller Logging Beginning with enhanced redundancy system revision 19.
PAGE 190
Chapter 8 Monitor and Maintain an Enhanced Redundancy System Controller Log A controller log is the record of changes. The log is stored on the controller’s NVS memory automatically. You can store the log to a CF card or SD card on an as needed basis or automatically at predefined times. The controller’s NVS memory and each external memory card type have a maximum number entries they can store. Specific events are stored in the controller’s log.
PAGE 191
Monitor and Maintain an Enhanced Redundancy System Verify Date and Time Settings Chapter 8 After you have completed programming your redundant system and have downloaded your program to the primary controller, check the Redundancy Module Date and Time information and verify it matches the date and time of your system. TIP 2 Consider checking the Redundancy Module Date and Time as a part of your regular maintenance procedures.
PAGE 192
Chapter 8 Monitor and Maintain an Enhanced Redundancy System Verify System Qualification After you have completed programming your redundant system and have downloaded your program to the primary controller, check the system status to verify that the system is qualified and synchronized. TIP The system qualification process can take several minutes. After a qualification command or a switchover, allow time for qualification to complete before taking action based on the qualification status.
PAGE 193
Monitor and Maintain an Enhanced Redundancy System Chapter 8 Example of Qualified and Disqualified Status Indicators This example shows status display messages and status indicators that may appear differently depending on the qualification status of the redundant chassis. Note that these are only two examples of many possible status display message and indicator combinations for both the qualified and disqualified states.
PAGE 194
Chapter 8 Monitor and Maintain an Enhanced Redundancy System Check Qualification Status via the RMCT To determine the qualification status of your system by using the RMCT, open the RMCT and view the qualification status in the bottom-left corner of the tool.
PAGE 195
Monitor and Maintain an Enhanced Redundancy System Conduct a Test Switchover Chapter 8 Complete these steps to verify that your redundant system switches over as expected. Your system must be fully-qualified before you begin. 1. In RSLinx Classic software, access the RMCT for the primary redundancy module. 2. Click the Synchronization tab. 3. Click Initiate Switchover. The Redundancy Configuration Tool dialog box opens. 4. Click Yes. The switchover begins. 5.
PAGE 196
Chapter 8 Monitor and Maintain an Enhanced Redundancy System Synchronization After a Switchover TIP If your Auto-Synchronization parameter is set to Always, your system begins synchronizing immediately after the switchover. To monitor the synchronization of your system after you initiate the test switchover, you can monitor the synchronization process by using these methods: • Click the Synchronization Status tab and monitor the Secondary Readiness column.
PAGE 197
Monitor and Maintain an Enhanced Redundancy System Check the ControlNet Module Status Chapter 8 After you have programmed your redundant system and configured your ControlNet network, check two statistics specific to your ControlNet modules. These statistics include the CPU usage and the connections used. To view the CPU usage and the number of connections used, complete these steps. 1. In RSLinx Classic software, open the Module Statistics for the ControlNet module. 2. Click the Connection Manager tab.
PAGE 198
Chapter 8 Monitor and Maintain an Enhanced Redundancy System CPU Usage The CPU usage of the ControlNet modules must be at 80%, or less. Keeping the CPU usage below 80% reserves enough CPU functionality for the ControlNet module to properly facilitate a switchover. If the CPU usage is above 80%, the secondary chassis may not be able to synchronize with the primary chassis after a switchover occurs. In addition, unscheduled communication may be slowed.
PAGE 199
Chapter 9 Troubleshoot a Redundant System General Troubleshooting Tasks Topic Page General Troubleshooting Tasks 199 Check the Module Status Indicators 200 Use RSLogix 5000 Software to View Errors 201 Use the RMCT for Synchronization Attempts and Status 204 Use the RMCT Event Log 206 Keeper Status Causing Synchronize Failure 216 Partner Network Connection Lost 220 Redundancy Module Connection Lost 222 Redundancy Module Missing 223 Qualification Aborted Due to a Nonredundant Controlle
PAGE 200
Chapter 9 Troubleshoot a Redundant System Check the Module Status Indicators If an error or event occurs in the enhanced redundancy system, check the module status indicators to determine which module is causing the error or event. If any of the modules have status indicators that are steady or blinking red, then examine that module status display and the RMCT or other software to determine the cause.
PAGE 201
Troubleshoot a Redundant System Use RSLogix 5000 Software to View Errors Chapter 9 To view redundancy status by using RSLogix 5000 software, complete these steps. 1. Go online with the redundant controller. 2. Either click Primary or Secondary, depending on the controller you are online with. Primary Controller Secondary Controller The redundant controller ID and status are displayed.
PAGE 202
Chapter 9 Troubleshoot a Redundant System 3. If further information is required, click Controller Properties. 4. Click the Redundancy tab. 5. If controller fault details are needed, click the Major Faults and Minor Faults tabs to view fault types and codes.
PAGE 203
Troubleshoot a Redundant System Chapter 9 6. If necessary, reference these resources: • Redundant Controller Major Fault Codes • Logix5000 Controllers Major and Minor Faults programming manual, publication 1756-PM014 (describes all major and minor fault codes) Redundant Controller Major Fault Codes The fault codes listed and described in this table are specific to redundant controllers.
PAGE 204
Chapter 9 Troubleshoot a Redundant System Use the RMCT for Synchronization Attempts and Status When troubleshooting your redundant system for anomalies with qualification and synchronization, check the Synchronization and Synchronization Status tabs of the RMCT. Recent Synchronization Attempts The Synchronization tab provides a log of the last four synchronization attempts. If a synchronization command was unsuccessful, the Recent Synchronization Attempts log indicates a cause.
PAGE 205
Troubleshoot a Redundant System Chapter 9 Module-level Synchronization Status The Synchronization Status tab provides a module-level view of redundant chassis and can be used to identify what module pair may be causing a synchronization failure. Depending on the type of synchronization failure, you may need to open the Synchronization Status tabs for the primary and secondary redundancy modules.
PAGE 206
Chapter 9 Troubleshoot a Redundant System Use the RMCT Event Log When troubleshooting your redundant system, access the Event Log to determine the cause of an event, error, switchover, or major fault. Interpret Event Log Information Use this procedure to view and interpret Event Log information. 1. Open the RMCT and click the Event Log tab.
PAGE 207
Troubleshoot a Redundant System Chapter 9 2. If an event occurred, open the Event Log for both chassis (A and B). 3. Locate the Event line that shows the qualification code, start date and time of the event, in the A chassis event log. This is the last time the redundancy module was working properly. Please note, multiple codes could be displayed if multiple errors occurred. Additionally, if a secondary redundancy module is not present, then a code may not be seen at all.
PAGE 208
Chapter 9 Troubleshoot a Redundant System 5. Work back in time (up the lines of preceding events), to locate the point that a switchover or disqualifying event occurred. This is the end date and time of the event, and will be indicated on the Event line in the A chassis event log, with a disqualification code that the secondary has been disqualified, and a corresponding disqualification code in the B chassis event log.
PAGE 209
Troubleshoot a Redundant System Chapter 9 6. Examine the range of time in between the start of the event and the end of the event to find the error that caused the disqualification. IMPORTANT Be aware that this range of time can be very large depending on how much time has passed since the last disqualifying event.
PAGE 210
Chapter 9 Troubleshoot a Redundant System You can also use the Log Time column to identify a significant event. Scan within a time range that corresponds to the time an event was reported or annunciated. In addition, you can also attempt to identify events by finding differences between times logged. Such gaps in time often identify events that require troubleshooting.
PAGE 211
Troubleshoot a Redundant System Chapter 9 Table 39 - Possible Qualification Status Indicators Status Code Description PwQS Primary with qualified (synchronized) secondary partner QSwP Qualified (synchronized) secondary with primary partner DSwP Disqualified secondary with primary partner DSwNP Disqualified secondary with no partner PwDS Primary with disqualified secondary partner PwNS Primary with no secondary partner Export All Event Logs To export event logs with the RMCT version 8.01.
PAGE 212
Chapter 9 Troubleshoot a Redundant System The Export Event Log configuration screen appears. 4. To change the file name or save location to something other than the default, select the Browse button. 5. Click Export. 6. Select the 1756-RM in the secondary chassis. In the following example, chassis A is the secondary chassis. The primary chassis exports first. The status displays during export.
PAGE 213
Troubleshoot a Redundant System Chapter 9 In the following example, chassis B is the primary chassis. The secondary chassis then exports. In the following example, chassis A is the secondary chassis. A confirmation dialog box displays when the export completes. 7. Click OK.
PAGE 214
Chapter 9 Troubleshoot a Redundant System Export Diagnostics IMPORTANT Only Export Diagnostics when requested to do so by Rockwell Automation Technical Support. You can also click Export Diagnostics in the event of a module fault in the 1756 redundancy module. Click Export Diagnostics to collect and save diagnostic data from the redundancy module and its partner, if an unrecoverable firmware fault occurs.
PAGE 215
Troubleshoot a Redundant System Chapter 9 The Export Diagnostics dialog box appears, asking you to continue specifying a communication path. 3. Click OK to specify the communication path via RSWho software. The RSWho window appears. 4. Select the communication path to the partner or secondary module and click OK. The Export Diagnostics dialog box will appear and prompt you to specify a location to save the export file.
PAGE 216
Chapter 9 Troubleshoot a Redundant System 5. Name and save the export file. 6. Click Export. It may take several minutes to export all of the data. The Export Diagnostic Complete dialog box appears once the export has completed. 7. Click OK. Forward this diagnostics file to Rockwell Automation Technical Support only if requested to do so.
PAGE 217
Troubleshoot a Redundant System Chapter 9 Check the Module Status Display If the module status display of the ControlNet modules in the redundant chassis indicate these errors, you need to take corrective action: • Keeper: Unconfigured • Keeper: Unconfigured (data format changed) • Keeper: Unconfigured (slot changed) • Keeper: Unconfigured (net address changed) • Keeper: Signature Mismatch • Keeper: None Valid on Network Check Keeper Status in RSNetWorx for ControlNet Software To check the status of keep
PAGE 218
Chapter 9 Troubleshoot a Redundant System Valid Keepers and Signatures This example shows a Keeper Status dialog box where the ControlNet network that is comprised of valid keepers and signatures. Valid Keeper Status and Signatures Unconfigured Keeper The example below shows the Keeper Status dialog box where a module has an unconfigured status. Besides the status shown, the module status display indicates Keeper: Unconfigured (node address changed).
PAGE 219
Troubleshoot a Redundant System Chapter 9 Keeper Signature Mismatch This example shows ControlNet modules in the redundant chassis that do not have the same keeper signatures. With this anomaly, the ControlNet module display indicates Keeper: Signature Mismatch. This anomaly may result if a ControlNet module configured for the same node of another network is used to replace a ControlNet module with the same node address in the redundant chassis.
PAGE 220
Chapter 9 Troubleshoot a Redundant System Partner Network Connection Lost If a partner network connection between a redundant chassis pair is lost, a state change or switchover may occur. These state changes may result: • Primary with qualified secondary changes to primary with disqualified secondary • Qualified secondary with primary to disqualified secondary with primary To use the Event Log to determine if a lost partner network connection caused a state change, complete these steps.
PAGE 221
Troubleshoot a Redundant System Chapter 9 4. Use the time of the switchover event found in the primary chassis to identify the corresponding event in the secondary chassis. The switchover indicated in the primary chassis log occurred at 10:27:08. Secondary Chassis Event Log 2 2 2 2 The corresponding events in the secondary chassis log indicate that the network is not attached and that the SYS_FAIL_LActive backplane signal is active.
PAGE 222
Chapter 9 Troubleshoot a Redundant System To recover from a ControlNet network disconnection, take these actions: • Check all ControlNet tap and trunkline connections. Correct any disconnections or other connection anomalies. • If the Auto-Synchronization parameter is not set to Always, use the commands in the Synchronization tab of the RMCT to synchronize your chassis.
PAGE 223
Troubleshoot a Redundant System Chapter 9 To resolve this anomaly, check the intermodule cable that connects the redundancy modules. Verify that it is properly connect and is not severed. Also, if the Auto-Synchronization parameter of this system is not set to always, use the commands in the Synchronization tab to synchronize that chassis once the anomaly is resolved.
PAGE 224
Chapter 9 Troubleshoot a Redundant System You can also browse to the redundancy module in RSLinx Classic software to determine if it is connected to the network. A red X over the redundancy module indicates the module is not in the chassis. Figure 66 - Missing Redundancy Module in RSLinx Classic Software 73 2 73 2 To correct the missing module anomaly, first verify that the redundancy module is correctly installed in the chassis and it is properly powered.
PAGE 225
Troubleshoot a Redundant System Qualification Aborted Due to a Nonredundant Controller Chapter 9 If you place a controller that is not enabled for redundancy into the redundant chassis, the qualification and synchronization fail. To determine if your synchronization failure is due to a nonredundant controller, complete these steps. 1. If not already open, open the RMCT of the primary module. 2. Click the Synchronization tab and view the Recent Synchronization Status Attempts log.
PAGE 226
Chapter 9 Troubleshoot a Redundant System 5. Open RSLogix 5000 and go online with the primary controller in your system. 6. Open the controller properties and verify that Redundancy Enabled is checked. This controller is not enabled for use in a redundant system. If Redundancy Enabled is not selected, then take these actions: • Do one of the following: –Remove the controllers that are not Redundancy Enabled. –Enable the controller for redundancy and make other program changes to accommodate redundancy.
PAGE 227
Appendix A Status Indicators Redundancy Module Status Indicators Topic Page Redundancy Module Status Indicators 227 The redundancy modules have these diagnostic status indicators. 1756-RM2/A and 1756-RM2XT Status Indicators Figure 67 - Redundancy Module Status Indicators for 1756-RM2/A and 1756-RM2XT Modules PR I M CH2 CH1 OK CH2 CH1 OK Module Status Display The module status display provides diagnostic information.
PAGE 228
Appendix A Status Indicators Table 40 - Module Status Display 228 Module Status Display Description PRIM Primary redundancy module. The module is operating as the primary module. No action required. DISQ Disqualified secondary redundancy module. Check the secondary partner module’s type and revision. QFNG Qualifying secondary redundancy module. Redundant system status. No action is required. SYNC Qualified secondary redundancy module. Redundant system status. No action is required.
PAGE 229
Status Indicators Appendix A OK Status Indicators The OK status indicator reveals the current redundancy module state. Table 41 - OK Status Indicator Indicator State Description Off No power is applied to the redundancy module. If necessary, apply power. Solid red One of these conditions exists: • The redundancy module is conducting a self-test during powerup. No action necessary. • The redundancy module has experienced a major shutdown fault. Cycle power to clear the fault.
PAGE 230
Appendix A Status Indicators Indicator State Description Redundant Channel is operating normally as the redundant channel. Link Down Channel is disconnected. Several causes could be: – The cable is disconnected, broken, or damaged – The signal is attenuated – The connector is loose – The partner 1756-RM2 module is powered down or in a major fault state No SFP No transceiver was detected.
PAGE 231
Status Indicators Appendix A Table 43 - Module Status Display Module Status Display Description PROG Boot mode - Updating redundancy module firmware. Wait for firmware update to finish. No action is required. ???? Resolving initial redundancy module state. Wait for state resolution to finish. No action is required. PRIM Primary redundancy module. The module is operating as the primary module. No action required. DISQ Disqualified secondary redundancy module.
PAGE 232
Appendix A Status Indicators OK Status Indicators The OK status indicator reveals the current redundancy module state. Table 44 - OK Status Indicator Indicator State Description Off No power is applied to the redundancy module. If necessary, apply power. Solid red One of these conditions exists: • The redundancy module is conducting a self-test during powerup. No action necessary. • The redundancy module has experienced a major fault. Cycle power to clear the fault.
PAGE 233
Status Indicators Appendix A Chassis State Status Indicator The Chassis State (PRI) status indicator identifies whether the chassis is primary. The PRI status indicator on the primary redundancy module remains solid green, and the PRI status indicator on the secondary redundancy module remains off. Redundancy Module Fault Codes and Display Messages Redundancy modules may experience any of these faults.
PAGE 234
Appendix A Status Indicators Module Status Display A character string scrolls across the Module Status Display to indicate the fault type. The character string displays the fault type in either of these ways: • Two to four-character word abbreviations • Alpha numeric codes This table describes the two to four-character word abbreviations. Table 47 - Major Fault Code Messages 234 1st Word 2nd Word 3rd Word CFG LOG ERR Configuration log error. No action is required.
PAGE 235
Status Indicators Appendix A Table 48 describes the alphanumeric codes. The fault code is a four-character alphanumeric string. Valid characters are 0…9 and A through Z, except S and O. The first character is always E. Each firmware subsystem within the redundancy module is assigned a range of fault codes. Each subsystem assigns fault codes within its range. Table 48 - Alphanumeric Error Codes Valid Character String Indication E Error. x1 x2 x3 The subsystem in which the error was detected.
PAGE 236
Appendix A Status Indicators Notes: 236 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 237
Appendix B Event Log Descriptions This table lists and explains some of the most-commonly experienced event descriptions found in the Event Log of the RMCT. Use this table as a reference when determining if an event on your system requires additional troubleshooting. Event Description Description Autoqualification trigger Something happened that caused the system to try and synchronize again. Double-click the event to see what happened.
PAGE 238
Appendix B Event Log Descriptions Event Description Description Modules chassis state rule A check to choose a primary chassis if both chassis power up at the same time. Suppose that the modules in one chassis are already in a primary state. In that case, that chassis becomes primary. NRC modules rule A check to choose a primary chassis if both chassis power up at the same time. NRC stands for nonredundancy compliant.
PAGE 239
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Upgrade from a Standard Redundancy System Topic Page Upgrade from a Standard Redundancy System 239 Upgrade System Components 240 Upgrade Ethernet Modules When Rotary Switches Are Set between 2…254 244 Upgrade the System Software 241 Upgrade by Using Redundancy System Update 250 Replace 1756-RM/A or 1756-RM/B Redundancy Modules with 1756-RM2/A Redundancy Modules 264 If you need to upgrade your stan
PAGE 240
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Upgrade System Components IMPORTANT Safely shut down system and controlled equipment. Be sure to place the system and controlled equipment in a state where they can be safely shut down prior to beginning this upgrade. The available components to which you can upgrade when converting a standard redundancy system to an enhanced redundancy system depends on the enhanced redundancy system revision level.
PAGE 241
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C Upgrade the System Software Upgrading your system software requires you to make many considerations and decisions. Make sure you are fully aware of how your specific application will be affected when you upgrade system software: • If you are upgrading to enhanced redundancy system, revision 16.081 or earlier, you are not required to upgrade any software.
PAGE 242
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Replace Communication Modules You must replace all communication modules when upgrading to any enhanced redundancy system revision. You must use enhanced communication modules in an enhanced redundancy system. This table describes which controllers are available for system upgrades.
PAGE 243
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C Steps After System Components Upgrade Complete these remaining steps after upgrading the necessary components to an enhanced redundancy system 1. Apply power to the primary chassis. 2. Update and load the controller program. IMPORTANT If you have an existing RSLogix 5000 program for the controller, update the program to reflect the new modules and firmware revisions.
PAGE 244
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Upgrade Ethernet Modules When Rotary Switches Are Set between 2…254 This section includes the procedure to upgrade your Ethernet communication modules when the modules rotary switches are set to 2…254 and you are unable to interrupt the primary. IMPORTANT This procedure must be executed before steps 6…12 of Upgrade by Using Redundancy System Update on page 250.
PAGE 245
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C 5. From the Auto-Synchronization pull-down menu, choose Never. 6. Click Apply, then click Yes. 7. Click the Synchronization tab. 8. Click Disqualify Secondary, then click Yes. The secondary chassis is disqualified as indicated by the RMCT at the bottom-left of the RMCT and on the redundancy module’s status display. Status in RMCT 9. Click OK.
PAGE 246
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System 10. Make a note of the primary Ethernet module’s Port Configuration including the following: • IP Address • Network Mask • Gateway Address 11. Disconnect the Ethernet cable or cables from the secondary Ethernet module. 12. Remove the secondary Ethernet module from the secondary chassis. Record the original rotary switch settings, as you need to set them back later. Set the rotary switches to 999. 13.
PAGE 247
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C b. Select the Ethernet module catalog number and click Next. c. Browse to the module and select it. Secondary Chassis 2 2 d. Click OK. e. Select the firmware revision to upgrade to and click Next. f. Click Finish. The firmware begins to update. When the update is complete, the Update status dialog box indicates completion. Wait for the update to complete. 16.
PAGE 248
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System 18. In RSLinx Classic software, browse in this chassis to the primary 1756-RM module. 19. Right-click to select Module Configuration to open the RMCT. 20. Click the Synchronization tab in the RMCT. 21. Click Synchronize Secondary, then click Yes. 22. After the redundant chassis pair synchronizes, click Initiate Switchover from the Synchronization tab in the RMCT, then click Yes. 23.
PAGE 249
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C 28. After the update completes, reconnect the Ethernet cable or cables to the secondary Ethernet module and wait for communication to resume on the network. 29. Repeat steps 23…28 for all Ethernet modules that have their rotary switches set between 2…254. 30. In RSLinx Classic software, browse to the primary 1756-RM module. 31. Right-click to select Module Configuration to open the RMCT. 32.
PAGE 250
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Upgrade by Using Redundancy System Update You can upgrade an enhanced redundancy system revision to another while your process continues to run. This is known as Redundancy System Update (RSU). IMPORTANT RSU is available only when upgrading from an enhanced redundancy system revision to another. You cannot use this process to upgrade from a standard redundancy system to an enhanced redundancy system.
PAGE 251
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C Step 1: Before You Begin Consider these points before you begin upgrading your enhanced redundancy system to a new revision. • During the upgrade procedures, you cannot use RSLogix 5000 software to change the mode of the controller. Instead, use the mode switch on the front of the controller. • Leave RSNetWorx™ for ControlNet software closed or offline throughout this procedure.
PAGE 252
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Step 3: Download and Install the Redundancy Firmware Bundle Download and install the redundancy firmware revision bundle from the Rockwell Automation Support website at: www.rockwellautomation.com/ support/ Follow these steps. 1. 2. 3. 4. Click the Downloads link on the Get Support Now menu. Click Firmware Updates under Additional Resources. Click Control Hardware.
PAGE 253
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C The Module Configuration dialog box opens. 4. Right-click the title bar and select About. The About dialog box opens and indicates the RMCT version. TIP The RMCT launches at the version that is compatible with the redundancy module firmware that is currently installed.
PAGE 254
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Step 6: Prepare the Redundant Chassis for the Firmware Upgrade Complete these steps to prepare both the primary and secondary redundant chassis for redundancy firmware upgrades. 1. Set the mode switch of the primary and secondary controllers to REM. If the redundant controllers in both chassis of the redundant chassis pair are not in Remote Program (REM) mode, the redundancy firmware upgrade cannot be completed.
PAGE 255
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C 7. Click the Synchronization tab. 8. Click Disqualify Secondary, then click Yes. The secondary chassis is disqualified as indicated by the RMCT at the bottom-left of the RMCT and on the redundancy module’s status display. Status in RMCT 9. Click OK and close the RMCT. Closing the RMCT helps prevent a timeout from occurring when the redundancy module’s firmware is upgraded.
PAGE 256
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System 3. Browse to the module and select it. Primary Chassis Secondary Chassis 4. Click OK. 5. Select the firmware revision to upgrade to and click Next. 6. Click Finish. The firmware begins to update. When the update is complete, the Update status dialog box indicates completion.
PAGE 257
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C 3. Browse to the module and select it. Primary Chassis Secondary Chassis 4. Click OK. 5. Select the firmware revision to upgrade to and click Next. 6. Click Finish. The firmware begins to update. When the update is complete, the Update status dialog box indicates completion. 7.
PAGE 258
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System 8. Complete steps 2…7 for each module in the secondary chassis, including a new controller, if applicable. IMPORTANT Ethernet communication modules that have rotary switches set must have been previously updated using Upgrade Ethernet Modules When Rotary Switches Are Set between 2…254 on page 244.
PAGE 259
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C 11. Click Change Controller. 12. Specify the controller revision to which you are upgrading. 13. If you installed a new controller while upgrading the primary chassis firmware, specify the new controller catalog number. 14. Click OK. 15. Access the Module Properties for each communication module in the chassis and specify the module firmware revision to which you are upgrading.
PAGE 260
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System You are now ready to lock the system and initiate a locked switchover to update the primary chassis. Continue with Step 10: Lock the System and Initiate a Switchover to Upgrade. Step 10: Lock the System and Initiate a Switchover to Upgrade Once you have downloaded the RSLogix 5000 project you prepared, complete these steps to lock your system and initiate a switchover.
PAGE 261
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C The System Update Lock Attempts log indicates when the system lock is complete. 5. Click Initiate Locked Switchover, then click Yes. This step results in your secondary chassis assuming control and becoming the primary chassis. When the switchover is complete, the Locked Switchover Attempts log indicates success. In addition to the log, the text in chassis status row indicates the switchover state.
PAGE 262
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System 1. If you are replacing and upgrading your controller hardware, remove the controller from the secondary chassis and replace it with the new controller. 2. Launch ControlFLASH software and click Next. 3. Select the module catalog number and click Next. 4. Browse to the module and select it. Primary Chassis Secondary Chassis 5. Click OK. 6. Select the firmware revision to upgrade to and click Next. 7.
PAGE 263
Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Appendix C Step 12: Synchronize the Redundant Chassis Complete these steps to synchronize the redundant chassis after firmware in both chassis have been upgraded to the same revision. 1. Launch the RMCT for the redundancy module in the primary chassis by right-clicking on the module in RSLinx Classic software and selecting Module Configuration. 2.
PAGE 264
Appendix C Upgrade from a Standard Redundancy System or to Another Enhanced Redundancy System Replace 1756-RM/A or 1756RM/B Redundancy Modules with 1756-RM2/A Redundancy Modules If you need to replace your current redundancy modules with 1756-RM2/A modules, you can do so without initiating a switchover. TIP For the following steps, ‘redundancy’ module is used when referring to the 1756-RM/A or 1756-RM/B modules.
PAGE 265
Appendix D Convert from a Nonredundant System Topic Page Update the Configuration in RSLogix 5000 Software 266 Replace Local I/O Tags 268 Replace Aliases to Local I/O Tags 269 Remove Other Modules from the Controller Chassis 270 Add an Identical Chassis 271 Upgrade to Enhanced Redundancy Firmware 271 Update the Controller Revision and Download the Project 271 When converting from a nonredundant to a redundant system, first consider the following: • You can use only RSLogix 5000 software v
PAGE 266
Appendix D Convert from a Nonredundant System Update the Configuration in RSLogix 5000 Software These steps provide an overview of the process required to update the I/O Configuration tree in RSLogix 5000 software. 1. If you have I/O in the chassis with the controller, add a ControlLogix communication module to the appropriate network because I/O modules are not permitted in a redundant chassis. You can now move the I/O modules to the new chassis in the I/O Configuration tree.
PAGE 267
Convert from a Nonredundant System Appendix D 2. Copy the I/O modules and paste them into the chassis of the newly-added communication module. Paste I/O into the new ControlNet chassis. 3. Delete the I/O modules from the controller chassis configuration. 4. Continue by completing the procedures to Replace Local I/O Tags and to Replace Aliases to Local I/O Tags.
PAGE 268
Appendix D Convert from a Nonredundant System Replace Local I/O Tags If you have moved I/O modules out of the local controller chassis and into the remote I/O chassis, complete these steps to find and replace the local I/O tags in your program. 1. Open the routine where the local I/O tags need to be updated. 2. Press CTRL+H to open the Replace in Routines dialog box. 3. From the Find What pull-down menu, choose Local:. 4.
PAGE 269
Convert from a Nonredundant System Appendix D 9. Click Replace All. The find/replace is completed and the results are indicated in the Search Results tab. Replace Aliases to Local I/O Tags If your program uses alias tags for the I/O modules that you are moving, complete these steps to replace alias tags. 1. In RSLogix 5000 software, open the Controller Tags. 2. Press CTRL+H to open the Replace Tags dialog box. 3. From the Find What pull-down menu, choose Local:. 4.
PAGE 270
Appendix D Convert from a Nonredundant System Remove Other Modules from the Controller Chassis If modules other than those listed below are in the controller chassis, you must remove them. You can use these modules in ControlLogix enhanced redundancy systems. Table 51 - Components Available for Use in a Redundant Chassis Pair Module type Cat. No.
PAGE 271
Convert from a Nonredundant System Add an Identical Chassis Appendix D After you have configured your primary chassis with the modules listed above, add an identical chassis that contains the same modules with the same moduleplacement. For more information about chassis configuration, see the section titled Redundant Chassis on page 28.
PAGE 272
Appendix D Convert from a Nonredundant System Notes: 272 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 273
Appendix E Redundancy Object Attributes Use this table of redundancy object attributes as a reference when programming to obtain the status of your redundancy system. For this information Get this attribute Data Type GSV/SSV Description Redundancy status of the entire chassis.
PAGE 274
Appendix E Redundancy Object Attributes For this information Get this attribute Data Type GSV/SSV Description Status of the synchronization (qualification) process. Qualification InProgress INT GSV If Then -1 Synchronization (qualification) is not in progress. 0 Unsupported 1 - 99 For modules that can measure their completion percentage, the percent of synchronization (qualification) that is complete.
PAGE 275
Redundancy Object Attributes For this information Get this attribute Data Type GSV/SSV Description In a pair of redundant chassis, identification of a specific chassis without regard to the state of the chassis. PhysicalChassisID INT GSV If Then 0 Unknown 1 Chassis A 2 Chassis B Appendix E Slot number of the 1756-RM module in this chassis. 1756-RM SlotNumber INT GSV • Size of the last crossload. • Size of the last crossload if you had a secondary chassis.
PAGE 276
Appendix E Redundancy Object Attributes Notes: 276 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 277
Appendix F Enhanced Redundancy System Checklists Topic Page Chassis Configuration Checklist 277 Remote I/O Checklist 278 Redundancy Module Checklist 278 ControlLogix Controller Checklist 279 ControlNet Checklist 279 EtherNet/IP Module Checklist 280 Project and Programming Checklist 281 Chassis Configuration Checklist  Requirement Chassis used for the redundant pair are the same size, for example, both are 1756-A7, 7-slot chassis.
PAGE 278
Appendix F Enhanced Redundancy System Checklists Remote I/O Checklist  Requirement I/O is not placed in redundant chassis. I/O is connected to the redundant chassis by using one of these networking options: • ControlNet connections to the same ControlNet network as the redundant controller chassis, without bridging. • EtherNet/IP connections to the same EtherNet/IP network as the redundant controller chassis, without bridging.
PAGE 279
Enhanced Redundancy System Checklists Appendix F ControlLogix Controller Checklist  Requirement Identical ControlLogix controllers are placed in the same slot of both chassis of the redundant pair. Partnered controllers are identical in redundancy firmware revision, and memory size.
PAGE 280
Appendix F  Enhanced Redundancy System Checklists Requirement ControlNet HMI A ControlNet network or a ControlNet-to-EtherNet/IP gateway is used to connect to HMI because your system requires that HMI be updated immediately after a switchover. • PanelView Standard terminal, PanelView 1000e or 1400e terminal For an unscheduled network, 4 HMI terminals per controller are used. For a scheduled network, any amount of terminals within the limits of the ControlNet network are used.
PAGE 281
Enhanced Redundancy System Checklists  Appendix F Requirement EtherNet/IP HMI HMI Blind Time is the time during a switchover from primary to secondary, when tag data from the controller is unavailable for reading or writing. See HMI Blind Time Reduction on Ethernet During a Switchover on page 21. IMPORTANT: This feature requires RSLinx Enterprise software, version 5.50.04 or later.
PAGE 282
Appendix F  Enhanced Redundancy System Checklists Requirement Scan time is minimized by using these techniques when possible: • • • • • • • Unused tags are eliminated. Arrays and user-defined data types are used instead of individual tags. Redundancy data is synchronized at strategic points by using the Synchronize Data after Execution setting in the Program Properties dialog box. Programming is written as compactly and efficiently as possible. Programs are executed only when necessary.
PAGE 283
Appendix G Enhanced Redundancy Revision History Changes to This Manual With the availability of new controllers, modules, applications, and RSLogix 5000 software features, this manual has been revised to include updated information. This appendix briefly summarizes changes that have been made with each revision of this manual. Reference this appendix if you need information to determine what changes have been made across multiple revisions.
PAGE 284
Appendix G Enhanced Redundancy Revision History Publication Revision and Date Topic Added firmware requirements for revisions 20.054 and 19.
PAGE 285
Enhanced Redundancy Revision History Publication Revision and Date Topic 1756-UM535B-EN-P, December 2010 Updates to EtherNet/IP network use in enhanced redundancy systems Appendix G Support for 1756-A4LXT to chassis Support for 1756-L65 controller Support for 1756-L7x controllers(1) Improved scan time with 1756-L7x controllers when compared to the scan time with 1756-L6x controllers Corrected MSG attribute value to set the date and time for a 1756-RM redundancy module Support for Partial Import online
PAGE 286
Appendix G Enhanced Redundancy Revision History Notes: 286 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 287
Index Numerics 1715 Redundant I/O systems 16, 18, 35, 44 1756-A7XT 24 1756-CN2/B 56 1756-CN2R/B 56 1756-CN2RXT 56 1756-CN2x modules 32 1756-EN2F 24, 242 1756-EN2T 56 sockets 85 1756-EN2TR 56 sockets 85 1756-EN2Tx modules 32 1756-EN2TXT 56 1756-L6x 279 1756-L6x controller 29 1756-L7x 30, 185, 279 1756-RM2/A 152 1756-L7x controller 29 1756-L7xXT 25 1756-RM status indicators 200 1756-RM and 1756-RMXT modules 31 1756-RM2/A 24, 57, 61 1756-L7x 152 compatible revisions 24 crossload 151 dual fiber ports 138 restr
PAGE 288
Index ControlNet CPU usage 198 keeper crossload 102 keeper status 101 module check status 197 monitor CPU usage 198 network update time 95 node requirements 38-40 overview 38-?? produce/consume connections 93 redundant media 41 remote I/O 18 requirements 38-?? sample programs 198 schedule existing network 100 new network 98 troubleshoot keeper status 216 lost connection 220 unscheduled 97 ControlNet communication modules 56 conversion nonredundant to redundant 73 convert nonredundant to redundant 265-271 C
PAGE 289
Index export data for all events 127-128 export diagnostics button 214 export event log 124-128 extended event information 123 F FactoryTalk software 16 features available in system revision 19.
PAGE 290
Index overview 35-37 keeper 101 keeper crossload 102 Remote I/O 42 schedule existing 100 new 98 Universal Remote I/O 43 update time 95 network update time 95 nonredundant controller 225 nonredundant to redundant conversion 73 nonredundant, convert from 265-271 O online edits 182-188 finalize 186 reserve memory 187 retain edits 184 test edits 183 operations chassis designation 19 crossload 19 enhanced redundancy system 19 qualification 19 switchover 19 synchronization 19 optical ports 59 scan time 149 en
PAGE 291
Index redundancy firmware bundles bundles redundancy firmware 252 redundancy module 31, 52 connect via fiber-optic cable 63 date and time 115 info 111-112 install 57 lost connection between modules 222 status indicators 227 troubleshoot missing 223 Redundancy Module Configuration Tab qualification status 74 Redundancy Module Configuration Tool 49, 105 additional configuration 106 check qualification 194 Configuration tab 113-115 Event Log tab 120-129 identify version 109 install 54 Module Info tab 111-112
PAGE 292
Index shutdown RSLinx Classic 53 signed and unsigned firmware 17 SIL3 unsupported feature 17 single point of failure redundant fiber ports 16 small form pluggable SFP 67 sockets 1756-EN2T 85 1756-EN2TR 85 software 49 FactoryTalk Alarms and Events 50 FactoryTalk Batch 50 FactoryTalk View Site Edition 50 install 53 optional 50 Redundancy Module Configuration Tool 49 required 49 RSLinx communication software 49, 53, 86 RSLogix 5000 software 86 RSNetWorx for ControlNet 50 RSNetWorx for EtherNet/IP 50 RSView32
PAGE 293
Index upgrade components 240 firmware 67-71 Redundancy Module Configuration Tool 252 software 251 user comment 137 user program control 115 utilities BOOTP/DHCP 86 V version RMCT 109 W watchdog time 177, 281 workstation software 51 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012 293
PAGE 294
Index Notes: 294 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
PAGE 295
PAGE 296
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, 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. You can also visit our Knowledgebase at http://www.rockwellautomation.