1756-RN608 - Rockwell Automation
Contents
1. Erroneously Reported a Duplicate IP Address Anomaly RSLinx Enterprise Software and Local Ethernet Modules Product Service Advisory ACIG 2004 11 002 It was possible for a 1756 EWEB module to erroneously report a duplicate IP address under these conditions e high HMI traffic e secondary chassis was powering up depended on your configuration If this happened the chassis wouldn t synchronize ControlLogix5555 5561 5562 5563 Rev 13 53 Description If you use Then RSLinx Enterprise Put your 1756 ENBT or 1756 EWEB modules in the redundant software revision 3 0 chassis pair RSLinx Enterprise Put your 1756 ENBT or 1756 EWEB modules in a non redundant software revision 2 0 chassis and bridge the communication over a ControlNet network to the redundant chassis Revision 5 45 of the 1756 CNB and 1756 CNBR module corrects the following issue Continuous operation prevented additional unconnected communications After 497 days of uninterrupted continuous operation the unconnected buffer resources soon became unavailable The result of the ControlNet module s unconnected buffers being unavailable was that you could no longer communicate with the module via unconnected messaging Some examples of how module services were affected included e Unconnected message connections that were passed to or through the ControlNet module failed e Any attempt to go online with a controller through the ControlNet module failed i e progra2. modules are already at 5 45 or later ControlLogix5555 5561 5562 5563 Rev 13 70 Enhancement Description Series B of these controllers What s new about series B controllers e ControlLogix5561 With Series B controllers you e ControlLogix5562 e get to the CompactFlash card from the front of the controller e ControlLogix5563 e have longer battery life See Maintain the Battery of a ControlLogix Series B Controller publication 1756 AP014 for details Important Use only a 1756 BA2 battery in a series B controller Are there any new precautions Take these precautions with CompactFlash cards 1 Put the keyswitch in the PROG position before you insert a card Do this for any card except one that you know is blank Suppose you insert a card that already has a project that is configured to load on power up If a power cycle happens before you store another project the card loads the earlier project and firmware into the controller It s also possible that the controller starts running the project 2 Make sure that you hold the CompactFlash latch to the left before you remove the card If you push the eject button without moving the latch out of the way it s possible to damage the CompactFlash socket Do use the same firmware for both series A and series B controllers Yes You use the same firmware for series A and series B of ControlLogix5561 ControlLogix5562 ControlLogix5563 controllers CNB module gives a better The C
3. redundant system is less than in a non redundant system e Even though the ControlLogix5561 5562 and 5563 controllers execute logic faster they must still crossload data e Given the same project and redundant system a ControlLogix5561 5562 or 5563 controller is up to 30 faster than a ControlLogix5555 controller Up to 2 ControlLogix5555 Controllers in the Same Redundant Chassis This revision lets you place up to 2 ControlLogix5555 controllers in a redundant chassis e Use identical controllers in the same slots in the partner chassis e Do not mix ControlLogix5555 controllers in the same chassis with ControlLogix5561 5562 or 5563 controllers 1756 EWEB module in a local redundant chassis Place 1756 EWEB modules in a redundant chassis pair Important If you use RSLinx Enterprise software revision 2 0 put your 1756 ENBT or 1756 EWEB modules in a non redundant chassis and bridge the communication over a ControlNet network to the redundant chassis e Place an EWEB module in the same slot in each redundant chassis The modules in each redundant chassis must match each other slot by slot e Place up to 2 EtherNet IP modules in each redundant chassis e Use any mix of ENBT or EWEB modules e The remaining communication modules must be either 1756 CNB or CNBR modules for a total of 5 communication modules per redundant chassis e In a redundant system use an EtherNet IP network only for HMI workstation communication an
4. the firmware of the SRMs It takes several minutes to update a 1757 SRM module and the module resets itself at least 4 times Don t interrupt the process Wait until the Update Status window turns green and says Update complete Update Status Catalog Number 1757 SRM 4 amp SerialNumber 80001276 Current Revision 3 39 16 View Log New Revision 3 39 16 Wait until you see this box Status Help turn green and say Update complete Repeat If you interrupt the process the module may become inoperative If the update fails do not cycle the power to the module Leave the power on and update the firmware of the module again The update failed if you see e Update Status window turn red and say the update failed e OK LED on the SRM module is red flashing and the 4 character display is blank After you update a module to revision 3 39 or later it doesn t become inoperative if you interrupt an update 2 Update the firmware of the CNB ENBT and EWEB modules 3 Update the firmware of the controllers Publication 1756 RN608F EN E July 2005 6 ControlLogix Redundancy System Revision 13 Mattie Pont update a series B controller that has 1 7 firmware while it s in a secondary chassis If you have And the controller is And its firmware is Then updated the firmware of this SS gt 5335 It s OK to update its firmware while it s in a controller before secondary chassis notupdated the firmware of this se
5. 00 Mbps EtherNet IP 1756 ENBT E01 e g E01 E02 F01 etc 3 7 Bridge Twisted Pair Media 1756 10 100 Mbps EtherNet IP 1756 EWEB any 2 4 Bridge w Enhanced Web Services redundancy module 1757 SRM A or SRM B any 3 39 Publication 1756 RN608F EN E July 2005 2 ControlLogix Redundancy System Revision 13 What s In These Release These release notes provide the following information about the components of the redundancy system Notes For information about See this section On this page which software revisions to use Compatible Software Revisions 2 order in which to update your system How to Update Your Firmware 5 new features Enhancements 7 changes to existing features Changes 11 restrictions that no longer apply Corrected Anomalies 11 restrictions to your redundancy system Restrictions 15 other ControlLogix redundancy publications For More Information 15 Compatible Software To use this revision update your system as follows Revisions Mg Revision 2 6 or later of the 1757 SRM System Redundancy Module Configuration tool doesn t work with revision 11 or earlier redundancy systems Use revision 2 6 or later of the configuration tool only with revision 13 or later ControlLogix redundancy systems You can cause the 1757 SRM module to fault if you use those revisions with an earlier revision of a ControlLogix redundancy system For this software Use this Notes revision RSLinx See Which revision
6. 5 544 5 1756 CNBR 1 Transition to Not Lonely State Changes 1623162 8 5 2004 15 26 04 845 5 1756 CNBR 1 Transition to Not Lonely _ State Changes 1576984 8 24 2004 10 00 18 562 8 1757 SRM 28 Chassis Modules Rule Starts Stops See extended information 83 8 4 2004 10 00 18 558 8 1757 SRM 27 Powerdown Time Rule Starts Staps in text format 1576982 0 00 18 556 8 1757 SRM 26 NRC Modules Rule Starts Stops 1576981 8 4 2004 10 00 8 175 SRM 25 Standby Secondaries Rule Starts Stops 1576980 8 4 2004 10 00 18 551 8 _ 24 Blank Memories Rule Starts Stops Publication 1756 RN608F EN E July 2005 ControlLogix Redundancy System Revision 13 11 Changes This revision corrects these anomalies Rev 13 71 Change Description Support future component The controller firmware was updated to accommodate anticipated component change of the change to ControlLogix5561 ControlLogix5561 5562 and 5563 controller hardware 5562 and 5563 controllers Lgx00057340 Corrected Anomalies This revision corrects these anomalies Rev 13 71 I Change Description Excessive electrical disturbance Excessive electrical disturbance on the backplane caused a 1756 CNB or 1756 CNBR module to stop on the backplane caused a CNB communicating When this happened the CNB module showed one of these messages module to stop e FAULT ping c line 448 e FAULT ping c line 467 Revision 5 46 of the CNB module increased the chance of this fault Redund
7. NB module shows the following message when its backplane hardware fails indication when its backplane hardware fails FAILED BACKPLANE INTERFACE ASIC Publication 1756 RN608F EN E July 2005 8 ControlLogix Redundancy System Revision 13 Enhancement SRM module logs when modules open or close connections Enhancement Sequential Function Charts Description The SRM module now logs when a CNB module or controller opens or closes a connection to the SRM module Lgx00051525 ControlLogix5555 5561 5562 5563 Rev 13 53 Description This revision lets you use the sequential function chart SFC programming language to program your redundancy system More Stable Scan Times This revision reduces the jumps in program scan time that may have occurred in previous revisions The jumps were caused by programs with fast scan times or large crossloads that flooded the 1757 SRM module with data which increased the crossload time One ControlLogix5561 5562 5563 Controller in a Redundant Chassis This revision lets you place a ControlLogix5561 5562 or 5563 controller in a redundant chassis e Use only 1 ControlLogix5561 5562 or 5563 controller in a redundant chassis e Use an identical controller in the same slot in the partner chassis e Do not mix ControlLogix5561 5562 or 5563 controllers in the same chassis with ControlLogix5555 controllers The program scan time improvement when using one of these controllers in a
8. Open DeviceNet Vendor Association www rockwellautomation com Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1756 RN608F EN E July 2005 PN 957974 17 Supersedes Publication 1756 RN608E EN E May 2005 Copyright 2005 Rockwell Automation Inc All rights reserved Printed in the U S A
9. Release Notes ControlLogix Redundancy System Revision 13 Cat No 1756 CNB D 1756 CNBR D 1756 ENBT 1756 EWEB 1756 L55 1756 L55M12 1756 L55M13 1756 L55M14 1756 L55M16 1756 L55M22 1756 L55M23 1756 L55M24 1756 L61 1756 L62 1756 L63 1757 SRM If you have a 1756 L55 controller you must install a memory board IMPORTANT For more information see the ControlLogix Controller and Memory Board Installation Instructions publication 1756 IN101 When to Use These Release These release notes are for the following modules when you use them Notes in a ControlLogix redundancy system For a module in a redundant controller chassis make sure the catalog revision of the IMPORTANT module is greater than or equal to the catalog revision shown in the following table Otherwise the secondary chassis will not synchronize with the primary chassis ControlLogix COMMUNICATIONS BRIDGE label on the side of the module or box CAT NO SERIES CAT REV 1756 ENBT A E01 catalog revision EES Ethernet IP 10 100 Mb s To determine the catalog revision of a module look at the Module Catalog number Catalog revision or greater Firmware revision ControlLogix5555 controller 1756 L55Mxx any 13 70 ControlLogix5561 controller 1756 L61 any 13 71 ControlLogix5562 controller 1756 L62 any 13 71 ControlLogix5563 controller 1756 L63 any 13 71 ControlNet bridge module 1756 CNB D or CNBR D any 5 51 1756 10 1
10. ant chassis were more susceptible than non redundant chassis Lgx00057099 ControlLogix5555 5561 5562 5563 Rev 13 70 Anomaly Description ENBT module still showed PwDS Sometimes an ENBT module still showed PwDS even after you removed its partner from the after its partner was removed secondary chassis Lgx00045467 Communication Module Occasionally After a switchover or simultaneous power cycle both chassis cycled power at the same time a Used a Duplicate Address 1756 CNB 1756 ENBT or 1756 EWEB module sometimes tried to use a duplicate address e When this happened the module showed DUPL NODE or DUPLICATE IP ADDRESS e This condition stopped you from communicating with the module and left the secondary chassis disqualified unsynchronized e Sometimes an ENBT or EWEB module showed a duplicate IP address due to this condition but the chassis still synchronized Lgx00047327 Publication 1756 RN608F EN E July 2005 12 ControlLogix Redundancy System Revision 13 Anomaly RSLogix 5000 software couldn t go online after you inhibit a remote CNB module Description RSLogix 5000 software went offline when 1 Your system used universal remote 1 0 RIO 2 You cycled power to all I O on both the RIO and ControlNet networks 3 You inhibited a remote CNB module while the I O was reconnecting RSLogix 5000 software couldn t go back online and the 1 0 stopped reconnecting when this happened To recover you had to cause a swi
11. cy Module Configuration tool showed that the primary controller didn t have a partner e The chassis synchronized after you either cycled power to the secondary chassis or removed and reinstalled the secondary controller Lgx00053474 Chassis synchronized with mis configured ENBT modules The redundancy chassis pair synchronized even though one of the ENBT modules showed DUPLICATE IP ADDRESS This happened when the ENBT modules couldn t use IP swapping because their configurations didn t match Lgx00053868 Load from nonvolatile memory caused SRM module to fault Publication 1756 RN608F EN E July 2005 If you loaded a project from nonvolatile memory the 1757 SRM module sometimes faulted The fault was E2h1 FRMW Reset MOD Lgx00054558 Anomaly CNB module blocked a 1407 CGCM module from joining the network ControlLogix Redundancy System Revision 13 13 Description A CNB module sometimes blocked a 1407 CGCM module from joining the ControlNet network This happened if you cycled power to both modules at the same time Lgx00054692 Chassis wouldn t synchronize if an SRM reset itself during a switchover Sometimes an SRM resets itself during a switchover When that happened the chassis wouldn t synchronize Lgx00054716 Couldn t open an 1 0 connection Sometimes the CNB module wouldn t let you open an I O connection It gave you this error instead 16 0111 RPI out of range Lgx00055359 EWEB Module
12. d messaging Do not use an EtherNet IP network for e communication with 1 0 modules e communication between devices via produced consumed tags Publication 1756 RN608F EN E July 2005 Enhancement Duplicate IP Address Detection ControlLogix Redundancy System Revision 13 9 Description 1756 ENBT and 1756 EWEB modules now detect if their IP address conflicts with another device on the EtherNet IP network How the modules respond to the conflict depends on the following conditions If And The Both devices have One of the devices is in a e The device in the redundant chassis uses duplicate IP address redundant chassis the IP address detection e The other device stops communicating on the network Both devices are outside of The second device to access the network a redundant chassis uses the IP address e The other device stops communicating on the network One of the devices does The other device is ina Both devices try to communicate at that not have duplicate IP redundant chassis IP address address detection Both devices are outside of The device without duplicate IP address a redundant chassis detection uses the IP address e The other device stops communicating on the network In a redundant chassis an ENBT or EWEB module uses duplicate IP address detection to swap its IP address with its partner during a switchover See Automatic IP Address Swapping on page 9 Automatic IP A
13. ddress Swapping During a switchover 1756 ENBT and 1756 EWEB modules now swap their IP addresses with their partner modules in the other redundant chassis This lets you use the same IP address to communicate with a primary module regardless of which chassis is primary e Typically you no ongerneed to use ControlLogix Redundancy Alias Topic Switcher software to manage the IP addresses If your application still requires alias topics to manage IP addresses see ControlLogix Redundancy System User Manual publication 1756 UM523 e During a switchover communication over an EtherNet IP network with other controllers or HMI may freeze for up to a minute depending on network topology If you need bumpless communication with controllers HMls use a separate ControlNet network that is dedicated to communication with those devices Important Make sure to connect the 1757 SRCx cable to both 1757 SRM modules of the redundant chassis pair Otherwise the ENBT and EWB modules will show a duplicate IP address To let the modules swap IP addresses during a switchover 1 Allocate 2 consecutive IP addresses for each set of ENBT or EWEB modules one in each chassis For example 10 10 10 10 and 10 10 10 11 Give the same IP address gateway address and subnet mask to both modules in the redundant pair E g Set both IP address 10 10 10 10 The module in the primary chassis uses the IP address to which it is configured e g 10 10 10 10 The module in t
14. dundancy Module Configuration Tool revision 2 6 or later e RSLinx software revision 2 43 or later It automatically installs revision 2 6 or later of the configuration tool If you stay at revision 2 5 of the configuration tool Details If you use revision 2 5 of the configuration tool in a revision 13 redundancy system the event log lists these devices as Unknown Device Code 5 e 1756 L61 controller e 1756 L62 controller e 1756 L63 controller e 1756 EWEB module This doesn t affect the operation of the redundant system Some enhancements aren t available Keep in mind that the following enhancements aren t in revision 2 5 e Set the Clock of a 1757 SRM Module to the Workstation Clock listed on page 10 e Event Log Provides More Information listed on page 10 Publication 1756 RN608F EN E July 2005 4 ControlLogix Redundancy System Revision 13 How do I tell which revision I have of the configuration tool To see which revision of the 1757 SRM System Redundancy Module Configuration tool that you have 1 In RSLinx software browse to a SRM 2 Right click the SRM and choose Module Configuration 1757 SRM REDUNDANCY MODULE HEStGTE aze HaximzE 3 Right click the title bar of the configuration tool and choose About Publication 1756 RN608F EN E July 2005 ControlLogix Redundancy System Revision 13 5 How to Update Your Update your firmware in the following order Firmware ATTENTION 1 Update
15. er On subsequent executions the timer became active again Lgx00046229 Restrictions IMPORTANT Restriction Online Editing During a Switchover ControlLogix Redundancy System Revision 13 15 This revision contains the following restrictions In a redundant system use an EtherNet IP network only for HMI workstation communication and messaging Do not use an EtherNet IP network for e communication with I O modules e communication between devices via produced consumed tags Description In some instances RSLogix 5000 software may not let you perform additional online edits of a function block SFC or structured text routine This may occur if you edit the routine while online and the system is switching over and synchronizing If this occurs 1 Close and then open RSLogix 5000 software 2 Upload the RSLogix 5000 project from the primary controller Deleting a Task or Unscheduling a Program Online The secondary chassis may disqualify and then synchronize if you e delete a task while online with the controller e unschedule a program while online with the controller ASCII Instructions May Prevent the Secondary Controller From Synchronizing Controller May Momentarily Drop Its Connection to a Digital 1 0 Module After you download a project that contains ASCII instructions e g ABL ACB to a pair of redundant controllers the secondary controller may disqualify and fail to synchronize If this occu
16. he secondary chassis uses the IP address of the primary 1 in the last address segment e g 10 10 10 11 N Publication 1756 RN608F EN E July 2005 10 ControlLogix Redundancy System Revision 13 Enhancement Description Set the Clock of a 1757 SRM Requires 1757 SRM System Redundancy Module configuration tool revision 2 6 or later See Which Module to the Workstation revision of RSLinx software do need on page 3 Clock 1757 SRM REDUNDANCY MODULE Conditional ChassisA H vrm usm To send the currently running workstation PC time to the SRM module click this button Event Log Provides More Requires 1757 SRM System Redundancy Module configuration tool revision 2 6 or later See Which Information revision of RSLinx software do need on page 3 Export file includes extended information in text format RM REDUNDA OD o C oF See events in both SRM modules at the same time 1623168 8 5 2004 15 27 17 952 8 175 SRM 1A Chassis Redundancy State changed State Changes 1623167 825 2004 15 27 17 910 8 1757 SAM___ 2E Qualification Complete Qualification 1623166 8 5 2004 15 26 48 437 8 1757 SAM_ 2D Qualification Attempted Qualification 1623165 8 5 2004 15 26 48 436 8 1757 SAM__ 2C Autoqualification Trigger Qualification 1623164 8 5 2004 15 26 17 874 8 1757 SAM_ 19 Chassis Redundancy State changed State Changes 1623163 8 5 2004 15 26 0
17. mming terminal connection failed e Establishing or re establishing I O connections failed e Browsing to or through the module via RSLinx failed e CPU utilization reading quickly went to 100 and stayed there Lgx00052277 Publication 1756 RN608F EN E July 2005 14 ControlLogix Redundancy System Revision 13 Anomaly Secondary Chassis Synchronized with ENBT Module NOT Connected Description Revision 3 4 of the 1756 ENBT module corrects the following issue A secondary chassis synchronized even if a 1756 ENBT module wasn t connected to the EtherNet IP network For example the chassis synchronized when you unplugged or broke the ethernet cable of the ENBT module Lgx00035956 ENBT Module Erroneously Reported a Duplicate IP Address Revision 3 4 of the 1756 ENBT module corrects the following issue It was possible for an ENBT module to erroneously report a duplicate IP address under these conditions e high HMI traffic e secondary chassis was powering up depended on your configuration This resulted in a failure to synchronize Online Memory Information Was Incorrect fa Controller Properties MyRedundantController_R11 While online RSLogix 5000 software showed incorrect values for the memory usage of the controller General Serial Port System Protocol User Protocol Time Advanced SFC Execution File Rec Used Unused Total Memory Lgx00042913 Modules Incorrectly Indica
18. of RSLinx software do need on page 3 RSLinx Enterprise 3 0 You need this only for these HMls e PanelView Plus terminal e RSView Supervisory Edition software e VersaView industrial computer running a Windows CE operating system RSLogix 5000 13 0 RSNetWorx for ControlNet 4 21 RSNetWorx for DeviceNet 4 21 Publication 1756 RN608F EN E July 2005 If you don t connect your computer to revision 11 or earlier ControlLogix redundancy systems ControlLogix Redundancy System Revision 13 Which revision of RSLinx software do need And Then RSLinx software revision Install RSLinx software revision 2 50 2 50 is available This revision of RSLinx software automatically installs 1757 SRM System Redundancy Module Configuration tool revision 2 6 4 RSLinx software revision 1 Install RSLinx software revision 2 43 2 50 isn t available 2 Get Knowledgebase document G92234770 To access Rockwell Automation s Knowledgebase go to http support rockwellautomation com 3 Use the Knowledgebase document to install 1757 SRM System Redundancy Module Configuration tool revision 2 6 4 also connect your computer to revision 11 or earlier ControlLogix redundancy systems Consideration Revision 2 5 of the configuration tool doesn t recognize some devices gt gt gt Install RSLinx software revision 2 42 Do not install any of these software revisions e 1757 SRM System Re
19. ries A gt gt gt It s OK to update its firmware while it s in a controller before secondary chassis series B 1 7 To update its firmware the first time put the controller in a primary chassis or a non redundant chassis The controller will have a non recoverable fault if you update it while it is in a secondary chassis LOGIX 5563 PROCESSOR UNIT CATALOG REV PART NO Allen Bradle CATALOG SERIGS 1756 L63 B After you update the controller the first time it s OK to update it in a secondary chassis from then on 1 8 or more It s OK to update its firmware while it s in a secondary chassis Publication 1756 RN608F EN E July 2005 ControlLogix Redundancy System Revision 13 7 Enhancements This revision has these enhancements for a redundant system For the list of enhancements for both redundant and non redundant systems see the following release notes e ControlLogix Controller Revision 12 Release Notes publication 1756 RN601 e ControlLogix Controller Revision 13 Release Notes publication 1756 RN603 Rev 13 71 Enhancement Description Update your CNB modules while Revision 5 51 of a 1756 CNB or 1756 CNBR module synchronizes with revision 5 45 5 51 This lets keeping control of your system you update the CNB modules in a secondary chassis and then synchronize the chassis Once synchronized you can switchover and update the modules in the old primary chassis This works only if your CNB
20. rs turn off both controllers primary and secondary and then turn the controllers back on In rare instances if a tap to a 1756 CNB module is disconnected or breaks the primary controller may momentarily drop its connection to a digital 1 0 module in local or remote chassis The connection automatically re establishes To minimize this use redundant ControlNet media Redundant ControlNet media prevents a loss of communication if a trunkline or tap is severed or disconnected The File Search Compare FSC Instruction Causes a Non Recoverable Fault For More Information The FSC instruction causes a non recoverable fault if both these conditions occur e a major fault is declared from within the expression of an FSC instruction e the user fault routine clears the fault When the user fault routine attempts to recover information previously saved isn t properly restored which results in corrupted system registers and a non recoverable fault Lgx00055522 For more information on the ControlLogix redundancy system see the ControlLogix Redundancy System User Manual publication 1756 UM523 Publication 1756 RN608F EN E July 2005 Rockwell Automation Support Rockwell Automation provides technical information on the web to assist you in using our products At http support rockwellautomation com you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service pack
21. s and a MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit http support rockwellautomation com Installation Assistance If you experience a problem with a hardware module within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running United States 1 440 646 3223 Monday Friday 8am 5pm EST Outside United States Please contact your local Rockwell Automation representative for any technical support issues New Product Satisfaction Return Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning and needs to be returned United States Contact your distributor You must provide a Customer Support case number see phone number above to obtain one to your distributor in order to complete the return process Outside United States Please contact your local Rockwell Automation representative for return procedure ControlNet is a trademark of ControlNet International Ltd DeviceNet is a trademark of the
22. tchover Lgx00052900 Each ControlLogix5555 Controller Needed a Separate ControlNet Bridge Module You had to use a separate 1756 CNB or 1756 CNBR module for each ControlLogix5555 controller in a redundant chassis If you have 2 controllers in a chassis e You needed at least 2 CNB modules in the chassis e You couldn t share a CNB module between controllers Communication sometimes stopped through the CNB module if you shared it between controllers Lgx00052928 ENBT module wouldn t recover from a short time between power cycles OK light of an ENBT module didn t show that a firmware update failed Download caused a CNB module to stop An ENBT module wouldn t go back to OK if you cycled power too soon after turning on the power That happened if you cycled power within 7 seconds after you first turned on the power Lgx00052938 The OK light of an ENBT module wouldn t go red if a firmware update failed Lgx00053083 A CNB module stopped when you downloaded a project that had a scheduled connection that was too big When this happened the CNB module showed this message ASSERT txlist c line 907 The CNB module now rejects the connection Lgx00053132 Chassis wouldn t synchronize after simultaneous power cycle Sometimes the redundant chassis wouldn t synchronize if you cycled power to both chassis at the same time When this happened e You couldn t manually synchronize the chassis e The 1757 SRM System Redundan
23. ted Primary with Disqualified Secondary After the Secondary Module Was Removed A module in a primary chassis incorrectly indicated Primary with Disqualified Secondary under the following conditions 1 The secondary module was present but disqualified 2 While the secondary module was disqualified you removed it from the chassis Both the software and hardware showed the incorrect redundancy state of the module Lgx00045469 Connections Prematurely Timed Out A connection prematurely timed out under the following combination of circumstances e RPI of the connection was approximately 15 to 25 ms e CPU usage of the CNB module was close to 98 100 Lgx00045470 Switchover Extended Task Period If the period of a periodic task expired during a switchover the task might have delayed its execution 2 times the specified period After this extended period it returned to its specified period Lgx00045661 After a Switchover the Maximum Interval Time for a Periodic Task Might Have Been Incorrect After a switchover a periodic task might have shown a maximum interval time that was approximately 1 second longer than the actual value Lgx00046215 After a Switchover Watchdog Timer May Have Been Temporarily Inactive Publication 1756 RN608F EN E July 2005 If the period of a periodic task expired during a switchover the watchdog timer for the task might not have been active during the first execution after the switchov
Download Pdf Manuals
Related Search