text:
Mehr über die Mitgliedschaft bei Scribd erfahren
Entdecken, was Scribd alles zu bieten hat, inklusive Bücher und Hörbücher von großen Verlagen.
Release Notes
ControlLogix Standard Redundancy Firmware, Revision
Redundancy Module Catalog Numbers 1756-RM2, 1756-RM2XT, 1756-RM, 1757-SRM
Controller Catalog Numbers 1756-L61, 1756-L62, 1756-L63, 1756-L64
Communication Module Catalog Numbers 1756-CNB/D, 1756-CNB/E, 1756-CNBR/D, 1756-CNBR/E, 1756-ENBT, 1756-EWEB
About This Redundancy Firmware Bundle
Compatible Software Versions
About the Redundancy Module Configuration Tool
Before You Begin
Corrected Anomalies
Known Anomalies
Application Notes
Upgrade from Revision 15.xxx, or Later
Migrating from 1757-SRM Modules to 1756-RM Modules
Replace 1756-RM/A or 1756-RM/B Redundancy Modules with 1756-RM2/A Redundancy Modules
Store a Project to Nonvolatile Memory While Your Process Is Running
Additional Resources
ControlLogix Standard Redundancy Firmware, Revision 16.057_kit1
About This Publication
These release notes describe enhancements, corrected anomalies, and known anomalies specific to redundancy system software, firmware bundle revisions 16.057_kit1, 16.057_Aug2012, 16.057, 16.056, 16.053, and 16.050.
Information added to these release notes is indicated by change bars like the one shown to the left of this paragraph.
References to the 1756-RM2 and 1756-RM2XT modules are synonymous with 1756-RM2/A and 1756-RM2XT/A modules in text and graphics throughout this publication.
This firmware bundle is 16.057_kit1. This redundancy firmware bundle revises the previous bundle, revision 16.057_Aug2012. The 16.057_kit1 firmware bundle contains the firmware components listed in Table 1
We strongly recommend that you review the information provided regarding previous firmware revisions. We recommend that you do so because if you are upgrading your firmware through multiple previous revisions, all of the information specific to all of the revisions is applicable.
References to the 1756-RM2/A module also apply to the 1756-RM2XT/A module.
The following features have been added with the revision 16.057_kit1 release:
• Addition of the 1756-RM2/A and 1756-RM2XT/A redundancy modules.
• The 1756-RM2/A module is interference-free with regard to safety functions and can be used in ControlLogix® SIL2 applications.
• Redundant fiber ports for the 1756-RM2/A module for crossloading; no single point of failure of a fiber cable.
• During a switchover of the fiber channels on the 1756-RM2/A module, scan time can encounter a delay of ~10 ms or less; however, the chassis remains synched at all times during the channel switchover process.
Only the modules specified in the table below can be used in the standard redundancy system and these firmware revisions. Modules that are not listed in the table are not compatible with the standard redundancy system and are not supported by these redundancy firmware bundle revisions.
Rockwell Automation Publication 1756-RN628M-EN-E - November 2012
Table 1 - Required Series and Firmware Bundle Revisions for Components Used in a Redundancy System, Revisions 16.057_kit1, 16.057_Aug, 16.057, 16.056, 16.053, and 16.050
Cat. No.
Module Description
Firmware Revision
ControlLogix® ControlNet™ bridge module
ControlLogix redundant ControlNet bridge module
ControlLogix ControlNet bridge module
ControlLogix EtherNet/IP bridge module
ControlLogix EtherNet/IP web server module
ControlLogix5561 controller
ControlLogix5562 controller
ControlLogix5563 controller
ControlLogix5564 controller
ControlLogix redundancy module
ControlLogix system redundancy module
The 1756-ENBT build is 6.006 for firmware revision16.057, but RSLogix™ 5000 software version 16 does not recognize an ENBT major revision greater than 4 in a project. Users upgrading to the 6.006 ENBT build will need to set the Electronic Keying fields of the 1756-ENBT module properties to Compatible Keying; otherwise, an error will occur.
The firmware bundle can be downloaded from http://rockwellautomation.com/support. It is identified as V16.057_kit1.
Use these versions of software with this redundancy firmware bundle.
Table 2 - Required Software Versions for Redundancy System, Firmware Bundle Revisions 16.057_kit1, 16.057_Aug2012, 16.057, 16.056, 16.053, and 16.050
FactoryTalk® Services Platform
FactoryTalk View Site Edition (SE)
Redundancy Module Configuration Tool
RSLinx® Enterprise
RSLinx Classic
RSLogix 5000
RSNetWorx™ for ControlNet
RSNetWorx for DeviceNet
RSNetWorx for EtherNet/IP
Use the most recent FactoryTalk Services Platform Patch Roll-up with this redundancy firmware
revision. For the most recent patch roll-up, see Rockwell Automation Knowledgebase Answer ID 56184, accessible at: http://www.rockwellautomation.com/knowledgebase/. See FactoryTalk View Software Considerations on page 4 for use considerations.
If your redundant system is comprised of ControlLogix-XT modules placed in a 1756-A5XT chassis, RSLinx Classic software, version 2.55 or later, is required.
FactoryTalk View Software Considerations
FactoryTalk View software is required for use only with these human-machine-interfaces (HMIs):
• PanelView™ Plus terminal
• VersaView® industrial computer running a Windows CE operating system
• RSView® Supervisory Edition software
If you are using FactoryTalk View Site Edition software, install the RSLinx Enterprise HOTFIX. The HOTFIX improves the EtherNet/IP switchover time. For more information, see Knowledgebase document R154640079. To access the Rockwell Automation Knowledgebase, go to http://www.rockwellautomation.com/support.
The Redundancy Module Configuration Tool (RMCT) is required for use with both the 1756-RM and 1757-SRM modules. Use the RMCT to do the following:
• Configure redundancy system parameters. For example, to configure the Auto-Synchronization parameter.
• View redundancy system event logs when troubleshooting your system.
RSLinx Classic software includes the RMCT, however, it is not likely to be the version that is compatible with this firmware revision.
This firmware bundle also contains the RMCT. To install the RMCT, open the executable file and complete the steps as directed by the installation wizard.
The RMCT does not appear to be updated to a new revision until the redundancy module firmware has been updated. This is because the RMCT automatically uses the version that is compatible with the redundancy module firmware revision installed.
For information about checking the version of your RMCT, see Upgrade the Redundancy Module Configuration Tool (RMCT) on page 21.
Before upgrading a system to standard redundancy firmware bundle revision 16.xxx, consult this table to determine if another firmware upgrade is required.
If currently using firmware bundle revision
Then upgrade to
15.xxx before upgrading to 16.xxx
These enhancements are provided with enhanced redundancy firmware revision 16.057_kit1.
All previous 1756-RM, 1756-RMXT and RMCT enhancements are included in the 1756-RM2, 756-RM2XT modules and RMCT.
System Component
Redundancy Module
Automatic Export The Export All button on the Event Log tab allows all the event log records and internal diagnostic data from both redundancy modules in the chassis pair to be collected automatically.
Configuration Tool
Major Fault Recovery The redundancy module can now communicate on the backplane for most of its major fault conditions. When the redundancy module is in Major Fault state but communicating on the backplane, the OK status indicator flashes red and the module display shows the 4-character error code. The Clear Fault button on the Event Log tab automatically becomes active as soon as a major fault occurs on the redundancy module. The Module Info tab shows the fault code and associated information. You can click the Clear Fault button to clear the fault without removing and reinserting the module. Once the fault is cleared, the redundancy module automatically reboots and enters a primary or secondary state.
Redundant fiber ports for the 1756-RM2/A module for crossloading; no single point of failure of a fiber cable.
Addition of the 1756-RM2/A and 1756-RM2XT/A redundancy modules.
The 1756-RM2/A module is interference-free with regard to safety functions and can be used in ControlLogix® SIL2 applications.
During a switchover of the fiber channels on the 1756-RM2/A module, the chassis remains synched at all times. (Scan time can encounter a delay of ~10 ms or less during this fiber channel switchover.)
Enhancements with Firmware Bundle Revisions 16.057 and 16.057_Aug2012
These enhancements are provided with standard redundancy firmware bundle revisions 16.057 and 16.057_Aug2012.
The false execution time of Add-On Instructions have been improved. With previous revisions, the false execution time of an Add-On Instruction was dependent on the number of parameters (input, output, and inout) configured for the instruction. The more parameters configured, the longer the false execution time of the Add-On Instruction. With this revision, the false execution time of an Add-On Instruction is now constant if a scan false routine is not created. To determine the false execution time of Add-On Instructions based on your controller, reference the values published in the Logix5000 Controllers Execution Time and Memory Use Reference Manual, publication 1756-RM087.
Enhancements with Firmware Bundle Revision 16.056
These enhancements are provided with standard redundancy firmware bundle revision 16.056.
Table 3 - Enhancements with Firmware Bundle Revision 16.056
With 1756-EWEB firmware revision 4.010, socket services are available for use with the standard redundancy system. To download revision 4.010, go to http://www.rockwellautomation.com/support and download the revision posted with the 1756-EWEB module.
The 1756-RM module supports the use of standard redundancy-system communication modules. With this firmware revision, the 1756-RM module can be used with standard communication modules in redundant chassis. To see a list of standard communication modules that are compatible with the 1756-RM module, see the modules listed in the About This Redundancy Firmware Bundle section on page 2.
Auto-qualification and synchronization processes of the 1756-RM module are stopped after a chassis pair first fails to synchronize. In previous firmware revisions, if the Auto-Qualification parameter is set to Always and the controller in the secondary chassis faulted, or a communication module was removed from the chassis, the 1756-RM module would continuously attempt to qualify the redundant chassis. As a result of the continuous attempts to qualify, the event logs became filled with synchronization failure events, thus making the original fault more difficult to troubleshoot. With this firmware enhancement, the 1756-RM module stops auto-qualification and synchronization attempts after the first fault occurs. This makes troubleshooting the original fault easier.
Recent synchronization attempts executed by the primary redundancy module are logged in the Recent Synchronization Attempt log of the secondary redundancy module. The log can viewed by accessing the Synchronization tab within the RMCT. Previously, the Recent Synchronization Attempt log of the secondary 1757-SRM module would not indicate synchronization attempts executed by the primary redundancy module.
Lgx00066149, Lgx00083168
Synchronization failure reports enhanced by adding 'Partner Module not Found' cause.
In previous revisions, if synchronization failed due to either of the causes described below, then failure was indicated by the same cause statement in the synchronization log of the RMCT. For both types of failures, 'Module Pair Incompatible' was indicated as the cause. Causes include the following:
• Partner modules at incompatible firmware revisions, or have mismatched configurations
• A secondary module is not installed or powered
With this firmware revision, the 1756-RM module is able to differentiate between partner incompatibilities and a missing secondary module. The RMCT indicates a missing secondary module by stating 'Partner Module not Found' in the Cause column of the Recent Synchronization Attempts log.
Module is not installed or powered in chassis.
Modules are at different firmware revisions.
The timestamps of Lock for Update and Initiate Locked Switchover commands are more precise. In previous firmware revisions, when the redundant system was locked for an update or a locked switchover was initiated, the 1756-RM module would indicate the same time for both the initiation and completion of those commands. With this revision, the initiation and completion of each of these commands is timestamped accordingly and the difference in time between initiation and completion can be observed.
Enhancements with Firmware Bundle Revision 16.050
These enhancements were provided with standard redundancy firmware bundle revision 16.050.
Table 4 - Enhancements with Firmware Bundle Revision 16.050
Firmware revision 16.050 provides redundancy support for controller programming with Add-On Instructions.
Synchronization points for programs within the RSLogix 5000 project can be configured. Redundancy firmware revision 16.050 provides the ability to limit which programs are followed by synchronization. In many applications, this can reduce the overall impact to the task scan time by reducing the number of times a data area is synchronized. Removing a synchronization point results in 1 ms of overhead time. However, reducing the number of synchronization points may delay the switchover time because more programs may need to be re-scanned by the new primary controller as it starts at the last synchronization point. Synchronization is performed at the end of the last program in the task's program list, regardless of its Synchronize Data after Execution selection.
Standard redundancy firmware revision 16.050 provides support for the use of 1756-L64 controllers in the redundant system.
System Event History accessible via the Redundancy Module Configuration Tool (RMCT).
system event history tab is available in the RMCT and is visible only when the session is launched against the 1756-RM module. This feature automatically
captures key events occurring in the redundant system that tell why a switchover occurred or why redundancy was lost. Certain events also indicate what caused the chassis pair to become synchronized. The 20 most recent entries are available for viewing. Each entry has a user comment attached to it that can be used to enter system maintenance information.
For more details, see the online help of the RMCT.
Event Log provides additional module information. The 1756-RM module is able to report any changes in the application firmware revision and the backplane serial number via entries posted to the Event Log. This information indicates that a firmware upgrade took place and whether the chassis location of the 1756-RM module was changed.
The Synchronization Status tab provides module type and firmware revision data. Within the RMCT, the Synchronization Status tab displays the product name string and firmware revision of redundancy-compliant modules in the chassis.
User-identity parameter increased to 64 characters. The character length of each of the user identity parameters extends to a maximum of 64 characters.
The RMCT provides configuration features for both the 1757-SRM and 1756-RM modules. The RMCT version specified in this revision (16.050) is compatible with both the 1757-SRM module and the 1756-RM/A module. Lgx00076319 and Lgx00076320
The RMCT packaged with redundancy firmware revision 16.050 contains two versions of the RMCT for increased compatibility with the 1757-SRM modules. Version 5.1.1 of the RMCT is compatible with the 1757-SRM module firmware packaged with revision 16.050, but is not compatible with later 1757-SRM module firmware revisions. Therefore, RMCT version 5.2.3 shipped in this revision also includes a previously shipped version 3.6.4. The RMCT version that is compatible with this firmware revision installs both RMCT versions on the workstation. When you open the 1756-RM Module
Configuration dialog box in RSLinx Classic software, version 3.6.4 of the RMCT launches if the firmware revision of the module is at major revision 5, or earlier.
the major revision of the 1757-SRM module firmware is 5, then version 5.2.3 of the RMCT launches. The restrictions that pertain to the use of RMCT version 3.6.4 remain the same.
WCT Object attribute redefined. The 1757-SRM module's currentTime attribute of the WCT object matches the revision 16 ControlLogix controller specifications. The attribute number has been changed from 1 to 11. The default starting date was changed from January 1, 1972 to January 1, 1970.
1757-SRM module is able to identify standard and enhanced-redundancy system components.
The 1757-SRM module has the ability to synchronize or lock a redundant chassis pair containing only these standard redundancy modules:
If standard communication modules are used with any of these enhanced redundancy communication modules in the redundancy chassis:
or, with a 1756-CNB/A module, then the 1757-SRM module displays a '!Cpt' message on the status display and aborts any qualification or lock attempts.
These sections describe anomalies corrected in standard redundancy firmware bundle revisions 16.057_Aug2012, 16.057, 16.056, 16.053 and 16.050.
Corrected Anomalies with Firmware Bundle Revision 16.057_Aug2012
These anomalies have been corrected with standard redundancy firmware bundle revision 16.057_Aug2012.
CORRECTED: When persistent CRC errors occur on the ControlLogix backplane with a 1757-SRM module, the system cannot perform a successful switchover. This occurs when using standard redundancy systems running the 1756-Lxx Standard Redundancy Bundle revision 16.057 or earlier.
CORRECTED: When used in a standard redundancy system with the 1757-SRM or 1756-RM module, E0300 errors on these modules will not cause a switchover. This occurs when using standard redundancy systems running the 1756-Lxx Standard Redundancy Bundle revision 16.057 or earlier.
Corrected Anomalies with Firmware Bundle Revision 16.057
These anomalies have been corrected with standard redundancy firmware bundle revision 16.057.
Fault handlers can be defined at the controller and program scope levels. These fault handlers are typically used to handle major recoverable faults that can occur during runtime execution of an application due to programming errors. A typical example of this would be handling indirect addressing that has gone out of range; MyTag[ index ], where index is larger than the size of the array. Faults can also be handled by the controller during pre-scan of the controller program on the transition to Run mode. Again, for example, the handling of indirect addressing that has gone out of range. There is an anomaly when these methods attempt to handle a fault. These are the possible ways the anomaly can manifest itself:
• The controller will experience a major non-recoverable fault. I/O goes to their configured safe state, and the user application is cleared from memory. At this point, a Code 1 Type 60 or 61 major recoverable fault will be logged in the controller. This requires you to redownload the application.
• Tag data corruption.
• Online saving or uploading failures.
• Anomalous program execution. For example, if a rung is being scanned false and there is an instruction that has false execution, the fault handler executes so the remainder of the rung will scan true. In the example below, the OTE instruction has an index out of range. After returning from the fault handler, the ADD instruction will execute, even though the rung input conditions are false.
Lgx00106481, Lgx00107423, Lgx00100766, Lgx00106478
Corrected Anomalies with Firmware Bundle Revision 16.056
These anomalies have been corrected with standard redundancy firmware bundle revision 16.056. The descriptions in this table describe the anomalous behavior that you may experience if you do not update to this revision.
Table 5 - Corrected Anomalies in Standard Redundancy Firmware Bundle Revision 16.056
Anomaly Description
Use of connected MSG instructions to read data from the secondary chassis may cause loss of control.
ALL of the following conditions are true, there exists a remote possibility that the redundancy chassis may switch over with a faulted 1756-CNB or 1756-CNBR module in the new primary chassis.
• A controller in a remote chassis uses connected MSG instructions to read data from the secondary through a 1756-CNB or 1756-CNBR module located in the secondary chassis.
• The same controller is also using one or more 'Uncached Connected' MSG instructions to access data in the primary through a 1756-CNB or 1756-CNBR module that resides in the same chassis slot number used for the secondary messages.
• The remote chassis is quickly power cycled while it is in RUN mode. Lgx00084583, Lgx00084583, Lgx00089533, Lgx00074710, Lgx0007765, Lgx00095691
When the lowest node of the ControlNet network cannot be detected, the 1756-CNB module may fault and indicate 'ASSERT: redptnrchk.c' on the module status display. ControlNet network conditions that may cause the fault include:
• missing network terminator.
• defective cable or tap.
• use of redundant cabling and with cables broken at different locations on both channels A and B.
• use of redundant cabling and a network where the number of modules connected to channel A differ from the number of modules connected to channel B by more than two.
Lgx00069688 and Lgx00069034
Some network disruptions may cause the secondary 1756-CNB or 1756-CNBR module to constantly be in a DUP NODE state.
Lgx00079816, Lgx00079862
state change of the 1756-ENBT causes a timeout.
Occasionally, during qualification, a 1756-ENBT module state change time-out, a minor fault, will cause qualification to fail. To recover, re-issue the synchronize command.
Module continuously displays code 'PLU' (Primary Locked for Update). The 1756-ENBT module continues to display 'PLU' after you remove a primary or secondary 1757-SRM cable.
fault indicating duplicate IP addresses does not occur on 1756-ENBT modules in redundant systems where these conditions are present:
– IP address swapping is enabled for each of the 1756-ENBT modules.
– The 1756-ENBT modules with duplicate address are in separate primary chassis.
– The separate primary chassis were previously operating as a redundant chassis pair.
With this firmware revision, the 1756-ENBT modules accurately verify that no duplicate IP addresses are present and accurately report the duplicate IP addresses.
After a switchover, the new primary 1756-ENBT module may continue to use the IP address of the secondary 1756-ENBT module instead of assuming the primary 1756-ENBT module IP address. With this firmware revision, the new primary 1756-ENBT module successfully assumes the primary IP address after a switchover.
When an Add-On Instruction is used in the Power-Up Handler or Controller Fault Handler routines, a major nonrecoverable fault (MNRF) occurs on the new primary after two switchovers.
When redundant controllers are used to produce data communicated on a ControlNet network, after a switchover, produced data reverts to an earlier value until the next requested-packet interval (RPI) after and output scan occurs.
Redundant chassis synchronization fails when ControlLogix controllers are used in a redundant system where the redundant controller is consuming data produced by a GuardLogix controller.
After a switchover, an Add-On Instruction stack overflow error occurs on the new primary controller. This anomaly may occur when:
Add-On Instructions are used in the continuous task.
the 'During unused System Overhead Time Slice' parameter (specified in the Controller Properties dialog box, Advanced tab) is set to 'Reserve for System Tasks, eg Communications'.
block-transfer message error 16#301 occurs for an extended time period after a successful switchover. This anomaly occurs when the 1756-L6x controller
programmed with a block transfer of data to analog I/O via a 1756-DHRIO module.
After a redundant system is synchronized, if the secondary controller is removed or is faulted, the primary 1756-RM module faults with an E054 error code. Removing and reinserting the primary 1756-RM re-initiates qualification and resolves the error.
When a redundancy system has been operating in a synchronized state for an extended period of time, a backplane communication error may occur and trigger a complex sequence of system behaviors that includes:
– error code E054 displayed by the 1757-SRM module.
– a task Watchdog timeout occurs on the controller program.
– a redundant chassis switchover.
– ControlNet modules in the new primary chassis faulting and losing communication with I/O.
With this redundancy firmware revision, the controller firmware has been revised to eliminate the internal condition that triggers the backplane communication fault.
After running in the synchronized state for several days, a 1756-RM module of the pair may fault and indicate error code E8A0. The system-response to the fault depends on the location of the 1756-RM module. If the faulted 1756-RM module is in the:
primary chassis, a switchover occurs.
secondary chassis, disqualification occurs.
restore redundancy, remove and reinsert the faulted 1756-RM module. Then, synchronize the chassis.
addition to corrections made in the controller firmware, with this redundancy module revision, changes have been made to the system redundancy
module firmware as a precaution. If a backplane communication fault were to occur, it is rapidly detected and indicated by error code E2LH displayed on the 1757-SRM module.
The 1757-SRM module may fault during flash upgrade.
the 1757-SRM modules in the redundant chassis pair are flashed simultaneously, then the 1757-SRM module may display E700 OS ERR on the front
panel. To recover, cycle power to the module at the end of the flash upgrade process. To avoid this behavior, flash upgrade each 1757-SRM module separately.
minor fault does not clear automatically.
Occasionally, after the redundant chassis pair disqualifies or a switchover occurs, a minor fault (E2A0 and E2A1) on the 1757-SRM module may not be cleared automatically. The minor fault status may get automatically cleared if a new minor fault is recorded. The minor fault has no adverse effect on the 1757-SRM module's operation.
The primary 1757-SRM module faults with an E054 error when the secondary controller is removed or faults. When a secondary controller is removed or faults while synchronized, the primary 1757-SRM module may display an E054 error on its front panel. To recover, remove the primary 1757-SRM module from the rack and re-insert it. This will cause all modules in the secondary to disqualify, allowing a re-qualification to proceed.
The 1757-SRM module faults indicating error codes E88C and E054 after operating in a synchronized state for an extended period of time.
applications where messaging is heavily used and messaging traffic is extensive, the 1757-SRM module may indicate several minor faults with error
code E88C and then a major fault with error code E054. The major fault may cause an unsuccessful switchover where modules in the new primary chassis stop communicating. In addition, a task watchdog timeout occurs on the controller that was previously the primary. With this firmware revision, fault code E2LH is used to indicate the major communication fault on the backplane that previously resulted in the E88C and E054 fault codes. The implementation of fault code E2LH results in a fully-successful switchover to the primary chassis in response to the backplane error.
The 1757-SRM module faults indicating error code E888 immediately following a switchover.
applications where extensive messaging is used, if a break occurs on a communication module in the primary chassis and a switchover results from the
cable break, then a rare timing issue results and causes the 1757-SRM module to fault immediately after the switchover. The fault is indicated with fault code E888.
Qualification is unsuccessful after upgrading multiple modules in the primary chassis at one time.
multiple modules in the primary chassis are flash upgraded at the same time, the 1757-SRM module cannot determine compatibility status of partnered modules once the upgrade is complete. The result is unsuccessful qualification.
1757-SRM event log is unavailable after a power cycle. Occasionally, after cycling power to the 1757-SRM module, the event log for the module is inaccessible. In addition, the error code indicated in the Module Info tab of the RMCT indicates an EK2C error.
The 1757-SRM module's event log contains random entries that state 'This Event Does Not Exist'. In situations where an event log record could not be successfully written to nonvolatile memory, random entries in the event log may state 'This Event Does Not Exist'.
The secondary 1757-SRM module indicates an E010 error code when online edits are made to the primary controller's program while the system is synchronized. The secondary 1757-SRM module may fault and indicate error code E010 when these system conditions exist:
• Multiple controller programs with these settings are used:
– programs do not synchronize or crossload data at their completion.
– programs are uninhibited on the primary controller.
• Redundant chassis are synchronized.
Disconnecting and reconnecting the fiber-optic cable that connects the 1757-SRM modules while the redundant system is locked for an update results in unexpected communication module states. After reconnecting the fiber-optic cable, the expected states for the communication modules would be:
• Primary communication module state = PwDS.
• Secondary communication module state = DSwP.
However, with this anomaly, the modules in the redundant chassis are in these states:
• Primary communication module state = PwNS.
• Primary controller and redundancy module states = PwDS.
• Secondary communication module state = DSNP or DSwP.
Secondary controller and redundancy module states = DSwP. This anomaly is corrected with revision 16.056.
Lgx00089924, Lgx00090421, Lgx00090422
Corrected Anomalies with Firmware Bundle Revision 16.053
These redundancy system anomalies were corrected in redundancy firmware bundle revision 16.053.
Table 6 - Corrected Anomalies with Standard Redundancy Firmware Bundle Revision 16.053
Secondary 1756-ENBT module sometimes stops communicating after a power cycle.
1756-ENBT module in a secondary chassis sometimes stops communicating after you cycle power to it. To recover, cycle power to the secondary chassis
remove and re-insert the module.
Connected messaging to a redundancy controller can cause the controller to have a major nonrecoverable fault (MNRF) or cause disqualification. Performing large Data Table Writes (>125 DINTs) using connecting messaging to a redundancy controller from certain sources can cause the controller to have a Major Non-Recoverable Fault or cause disqualification. If the latter occurs, the system may not be able to re-synchronize without first cycling power to the primary controller. For the anomaly to occur, the system must be synchronized and the source of the message must be either another controller in the same redundancy chassis or an external controller communicating through 1756-EN2T modules.
Connected message writes, greater that 107 DINTs, to a synchronized controller pair may fail improperly. While the redundant chassis pair is synchronized and when an external controller is writing to a tag with a message size that is greater than 107 DINTs, the message fails with an invalid error code: 16#83. The first 115 DINTs will be transferred regardless of the error.
Corrected Anomalies with Firmware Bundle Revision 16.050
These redundancy system anomalies were corrected in redundancy firmware bundle revision 16.050.
Table 7 - Corrected Anomalies with Standard Redundancy Firmware Bundle Revision 16.050
Loss of resources in new primary 1756-CNB module after a switchover event. One of these conditions may occur on the new primary if a switchover happens just as a new incoming connection is being processed:
• The module may fault with 'ASSERT: cm_utils.c' on the display.
• New connection requests may fail with an error code 16#100 'Connection in Use'.
• CPU utilization on the new primary may be higher than the old primary.
• The 1756-CNB module may stop communicating, eventually scrolling Us20 on the display.
• The number of available connections may be less on the new primary.
• The 1756-CNB module may indicate that a connection is active. The status indicator will be OK solid green, when no connection exists. Lgx00074692, Lgx00076563, Lgx00081224, Lgx00081309, Lgx00076633, Lgx00071999
A 1756-CNB module double-cable break to the synchronized secondary causes permanent disqualification.
some cases, the redundant chassis pair may not automatically requalify if the ControlNet cables for more than one 1756-CNB module in the secondary chassis have been removed and then reattached.
Lgx00076560 and Lgx00076547
Fault after switchover caused by a message timeout. Rarely, the 1756-CNB module may fault with 'ASSERT: icn_ucmm.c' on the module status display if an unconnected message times out just before a switchover.
Lgx00068054, Lgx00076949
Cycling power to the primary chassis may cause the new primary 1756-CNB module to fault.
some cases, the 1756-CNB module may fault with 'ASSERT: qualtask.c' on the display after a switchover that had been triggered by the loss of communication to the primary chassis.
Lgx00077417, Lgx00078071
Connections to secondary controller fail with Out of Connections error. Uncached connected MSG instructions may fail with error code 16#11A 'Out of Connections' when sent through a 1756-CNB or 1756-CNBR module in a secondary chassis.
Lgx00076370 and Lgx00076564
The status indicator flashes a red OK without displaying an error message. After recovering from a power cycle the OK status indicator may continue to flash RED until the first connection has been establish. Lgx00081279 and Lgx00076105
Fault due to connection timeout.
a newly created connection times out before it can be duplicated in the secondary chassis the primary 1756-CNB module may fault with 'ASSERT:
redfwdopen.c' on the display.
Lgx00078094 and Lgx00078314
Conducting an firmware upgrade using ControlFlash tactility results in a ControlNet module fault. Rarely, the 1756-CNB module may fault with 'ASSERT: icpserv.c' on the display during a ControlFlash update if it has any active connections.
System restoration after a double cable break on two 1756-ENBT modules did not automatically synchronize the redundant system.
the two RJ45 cables were connected in quick succession on two 1756-ENBT modules in the same chassis, or a common switch was power-cycled while
the chassis pair was synchronized, the system would not re-synchronize automatically, even if the Auto-Qualification option was 'Always' or 'Conditional'. Lgx00076205 and Lgx00076116
Deleting a task or unscheduling a program while online causes a disqualification. The secondary chassis may disqualify and then synchronize if you:
• delete a task while online with the controller.
• unschedule a program while online with the controller.
Redundancy Module Configuration Tool (RMCT)
The event log of the 1757-SRM module is not accessible. Occasionally, the 1757-SRM Configuration Tool would not display any event records or the 1757-SRM module would fault with EK2C during runtime. The 1757-SRM module now handles this condition by displaying an EB17 minor fault on the Module Info tab in the configuration tool and disables event logging. The module will continue to operate normally. It must be replaced to provide the event logging feature.
new attempt to lock the chassis for firmware upgrade failed due to a previously aborted attempt.
An attempt to lock a redundant chassis may not succeed due to configuration issues. In some of these cases, a new attempt to lock was also unsuccessful due to a module insertion or module removal event.
Lgx00076690 and Lgx00075397
spurious 'System Update Abort' entry is logged at powerup.
An unexpected 'System Update Abort' entry was posted to the event log at powerup even when no lock attempt was made.
locked switchover in redundancy causes message block transfers to fail.
When performing block transfer messages through a 1756-DHRIO module, it is possible for the messages to fail with a configuration error after performing a locked switchover.
This table in this section lists known anomalies for standard redundancy firmware bundle revisions 16.057_Aug2012, 16.057, 16.056, 16.053 and 16.050.
Table 8 - Known Anomalies with Firmware Bundle Revisions 16.057_Aug2012, 16.057, 16.056, 16.053 and 16.050
1756-EWEB module may not be at the correct time zone after upgrading the firmware.
you back up your 1756-EWEB settings, and reload them after upgrading your 1756-EWEB module firmware, the 1756-EWEB module may not load the same time zone as that specified when the backup was made. After upgrading your 1756-EWEB module firmware and reloading you settings, access the time zone setting and change it if needed.
Redundant chassis synchronization fails when a high number of controller connections are used. Chassis synchronization may fail if the controller is near its connection limits. To reduce the likelihood of this anomaly, verify that you use controller
connections within the limits of the controller and that at least eight controller connections are reserved for the redundant system. Try to limit the number
controllers connections used to 243 connections, or less.
Message timeout errors increase in frequency when the 1757-SRM modules are replaced with 1756-RM modules. When a standard redundancy system is upgraded by replacing 1757-SRM modules with 1756-RM modules, increased message timeout errors may result from messages being sent to the secondary controller.
avoid experiencing the message timeout errors, verify that the messages in your program are not being sent to the secondary controller.
On very rare occasions, the 1756-RM module may not detect a module in the chassis when you apply power. An undetected module placed in the secondary chassis may cause qualification to be aborted. The undetected module may be identified by viewing the Synchronization Status tab of the RMCT.
Repeated connection and disconnection of the 1756-RM fiber optic cable results in various fault codes indicated on the module status display.
the 1756-RM fiber-optic cable is disconnected and connected repeatedly within short periods of time, the redundancy module faults and indicates error codes such as: E0XX or EAXX.
avoid experiencing these faults, wait 5…10 seconds between disconnecting and connecting the 1756-RM modules' fiber-optic cable. Lgx000845595, Lgx00091960
Disqualification occurs without any external faults.
The redundant chassis may disqualify after being synchronized for several days. Usually, extensive I/O connection traffic is also a factor. The cause of the disqualification is a communication anomaly between the controller and 1756-RM module that is indicated by code E88m minor faults. The faults are logged in the event log in addition to other event entries that are specific to the disqualification.
To configure your system to automatically recover and re-synchronize, select Always for the Auto-Qualification parameter available in the RMCT.
A secondary 1757-SRM module rejects a command issued by using the RMCT.
Sometimes the secondary 1757-SRM module rejects a synchronization, disqualification, or switchover command from the RMCT. To avoid this, give the command to the primary 1757-SRM module.
The restrictions listed in this table are applicable to standard redundancy firmware bundle revisions 16.057_Aug2012, 16.057, 16.056, 16.053 and 16.050.
Table 9 - Restrictions with Standard Redundancy Firmware Bundle Revisions 16.057_Aug2012, 16.057, 16.056, 16.053 and 16.050
Internet Explorer is not for use as an FTP client with 1756-EWEB modules. Due to errors that occur with security and access to the 1756-EWEB module, do not use Internet Explorer as an FTP client with 1756-EWEB modules.
With firmware revisions 16.050 and 16.053, socket services with the 1756-EWEB module are not available for use. With firmware revision 16.056, socket services with the 1756-EWEB module are available when 1756-EWEB firmware revision 4.010 is used. With firmware revision 16.056, if 1756-EWEB firmware revision 4.009 or earlier is used, socket services are not available. See the section About This Redundancy Firmware Bundle on page 2 for more information about 1756-EWEB firmware revisions that are compatible with redundancy firmware revision 16.056.
As of redundancy firmware revision 16.050, the ControlLogix5555 controller is no longer supported. Therefore, you cannot use a 1756-L55Mxx controller with redundancy firmware revisions 16.050, or later.
If you have a controller at this firmware revision, then you need to update the controller firmware with the controller placed in a nonredundant chassis:
• 1756-L64 controller at firmware revision 1.10 (boot firmware).
• 1756-L61, 1756-L62, 1756-L63 at firmware revision 1.7 (boot firmware).
If you install the controller in a redundant chassis, a major nonrecoverable fault (MNRF) may occur, or it may remain in a faulted state. The controller indicates this fault by the OK status indicator being solid red. The label on the side of the controller indicates the series controller and the boot firmware revision as shown in the example here.
Complete these steps to upgrade from the boot firmware revision.
1. Put the controller in a nonredundant chassis.
2. Update the controller.
3. Put the controller in the redundant chassis.
After you have updated the controller from the boot firmware revision, any further updates can be made while the controller is in the redundant chassis. Exception If your controller is already running in a redundant system and you want to update it to a later revision, you may leave it in the existing redundancy system during the firmware update.
The equipment phase feature provided with RSLogix 5000 software, version 16, is not supported by standard redundancy firmware revisions, that is, redundancy firmware revisions 16.050, 16.053, and 16.056. If you are using firmware revision 16.056, attempts to download a project that uses equipment phases are successful, however, the redundant chassis cannot qualify. If you are using firmware revision 16.053 or 16.050, downloading a project that contains equipment phases to a redundant controller is unsuccessful. If you want to use the equipment phase feature or RSLogix 5000 software, version 16, with your redundant system, upgrade to an enhanced redundancy system and use enhanced redundancy firmware revision 16.80, or later.
Alarm instructions provided with FactoryTalk Alarms and RSLogix 5000 software, version 16, are not supported in standard redundancy firmware revisions, that is, redundancy firmware revisions 16.050, 16.053, and 16.056. If you are using firmware revision 16.056, attempts to download a project that uses alarm instructions are successful, however, the redundant chassis cannot qualify. If you are using firmware revision 16.053 or 16.050, downloading a project that contains alarms to a redundant controller is unsuccessful. If you want to use the alarm instructions provided with FactoryTalk Alarms and RSLogix 5000 software, version 16, with your redundant system, upgrade to an enhanced redundancy system and use enhanced redundancy firmware revision 16.80, or later.
Inhibiting or removing an inhibition from a redundant controller program can cause the secondary chassis to disqualify, then to qualify again. When changing the Inhibit Program setting, plan for secondary chassis disqualification according to potential implications that are specific to your application. Or, unschedule the program rather than inhibiting it.
Do not use Match Project to Controller property with redundant controllers. If you use the Match Project to Controller property available in the Advanced tab of the Controller Properties dialog box, you cannot go online with, download to, or upload from the new primary controller after a switchover. This is because the serial number of the new primary controller is not the same as the serial number of the old primary controller and the project cannot be matched to the newly-switched-to controller.
Deleting I/O modules from a project while online with the controller may cause a major nonrecoverable fault (MNRF) on the secondary controller. If your application requires that you delete I/O modules from the project while online with the controller, disqualify the secondary chassis before deleting the I/O modules.
Using version 2.6, or later, of the RMCT with redundancy system firmware revision 11, or earlier, can cause the 1757-SRM module to fault. The 1757-SRM module fault occurs when viewing the Event Log in the RMCT at version 2.6, or later, when the redundant chassis firmware is at version 11 or earlier. Use only RMCT version 2.6, or later, with redundancy firmware revision, 13, or later. RSLinx Classic software, version 2.43 or later, automatically installs version 2.6 or later of the RMCT. For other versions of the RMCT, see Knowledgebase Answer ID 29511 (available at:
http://www.rockwellautomation.com/knowledgebase/). If you need to connect to a redundant system at revision 11, or earlier, use version 2.5 of the RMCT.
Upgrading from redundancy firmware revisions 11 and 13 directly to revision 16.050, 16.053, or 16.056, or later, is not possible. To upgrade the 1757-SRM module to redundancy firmware revision 16.050, 16.053, or 16.056, you first need to upgrade to a revision 15.60-compatible firmware. Then upgrade to firmware revision 16.050, or later, compatible firmware. See Before You Begin on page 5 for more information.
IMPORTANT: Flashing a 1757-SRM module from revision 2.xx, or earlier, directly to revision 4.3, or later, causes the 1757-SRM module to become permanently inoperable. To avoid inoperability, first flash the 1757-SRM module to any 3.xx revision that is included in the redundancy firmware revisions 13.xx. Once the 1757-SRM module is at revision 3.xx, you can successfully flash to version 4.xx.
After disconnecting a fiber-optic cable between the 1757-SRM modules, check the synchronization status of the secondary 1757-SRM module before you reconnect the cable. Wait until the module's status is secondary with no partner before reconnecting the cable. Otherwise, the secondary 1757-SRM module could fault with an EA91 error.
When upgrading 1757-SRM module firmware, allow for several minutes of update time. It takes several minutes to update a 1757-SRM module and the module resets itself at least four times after the upgrade is initiated in ControlFlash software. Interrupting the firmware upgrade of a a 1757-SRM module at firmware revision 3.37, or earlier, may cause the module to become inoperable. If the upgrade fails, leave the power on and try again. A failed upgrade is indicated by:
• Update Status dialog box in ControlFlash software contains a red box and says 'update failed'.
• OK status indicator on the 1757-SRM module is flashing and the four-character module status display is blank.
Consider these application notes when configuring, programming, and using your redundant system.
EtherNet/IP Networks and Redundant Systems
In a redundant system, use an EtherNet/IP network only for HMI/workstation communication and messaging. Do not use an EtherNet/IP network for:
• Communication with I/O modules
• Communication between devices via produced/consumed tags
Minimum Value for the Watchdog Time
Use this table to determine which equation to use to calculate the watchdog time for each task in your program.
Then use this equation
Switchover time is critical to system performance
(2 * maximum_scan_time ) + 150 ms
Module firmware will be updated in the field
maximum_scan_time) + 245 ms
You need to safeguard against the removal of a intermodule fiber-optic cable
maximum_scan_time) + 390 ms
You need to safeguard against communication faults in synchronized chassis
maximum_scan_time) + 225 ms
The maximum_scan_time is the maximum scan time for the entire task when the secondary controller is synchronized.
Synchronizing After Disqualification
If your secondary chassis becomes disqualified, or you manually disqualify it, take these actions before you try to synchronize the chassis:
• Verify that the synchronization status of the primary module is full compatibility.
• Wait at least 15 seconds after the redundant chassis are disqualified before you try to synchronize them.
Complete the tasks listed in this table to upgrade your redundancy system from standard redundancy firmware bundle revision 15.xxx to revision 16.056, or later, while your process continues to run.
Upgrade Workstation Software
Upgrade the Redundancy Module Configuration Tool (RMCT)
Download and Install Redundancy Firmware Bundle
Update EDS Files
Prepare the Redundant Chassis for the Firmware Upgrade
Update Primary 1756-RM or 1757-SRM Module Firmware
Update the Secondary Chassis Firmware
Prepare the RSLogix 5000 Project for the Upgrade
Lock and Switchover the System for Update
Update the New Secondary Chassis Firmware
Synchronize the Redundant Chassis
You cannot upgrade to redundancy firmware revision 16.050, or later, if your current redundancy system is at revisions 11…13. For more information, see the Before You Begin section on page 5.
During the upgrade procedures, you will not be able to use RSLogix 5000 software to change the mode of the controller. Instead, use the keyswitch on the front of the controller.
Leave RSNetWorx for ControlNet software closed or offline throughout this procedure. Otherwise, you will see errors in the RSNetWorx software during the update process.
While completing these tasks to upgrade your redundancy firmware:
– do not make any changes to the RSLogix 5000 project other than those identified in these tasks.
– verify that no one will be, or is making, changes to the project.
Before you download and upgrade software for use with your redundant system, use one of these methods to fully shut down RSLinx Classic software:
• Right-click the RSLinx Classic icon in the notification area of the screen and choose Shutdown RSLinx Classic.
• With RSLinx Classic software open, from the File menu choose Exit and Shutdown.
Obtain and install the software required for your redundant system configuration and application. See Compatible Software Versions on page 3 for versions required for use with this redundancy firmware revision.
Use the installation instructions or release notes provided with each software version for installation procedures and requirements.
Verify Your RMCT Version
Complete these steps to check or verify the version of the RMCT you have installed.
The RMCT launches at the version that is compatible with the 1756-RM module firmware that is currently installed. If you have not upgraded your 1756-RM module firmware after upgrading your RMCT version, the RMCT version that is indicated may not reflect the version you upgraded to.
1. Launch RSLinx Classic software.
2. Click RSWho.
3. Right-click your redundancy module and choose Module Configuration.
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.
Download and install the redundancy firmware revision bundle from the Rockwell Automation Support website at:
The redundancy firmware bundles are posted in the Downloads section and are classified in the Control Hardware category.
If needed, obtain EDS files for modules in your system from the Rockwell Automation Support website at:
Once you have downloaded the required EDS file, launch the EDS Hardware Configuration Tool by choosing Start > Programs > Rockwell Software > RSLinx Tools > EDS Hardware Installation Tool.
The tool then prompts you to Add or Remove EDS files.
Complete these steps to prepare both the primary and secondary redundant chassis for redundancy firmware upgrades.
1. Set the keyswitch of the primary and secondary controllers to REM.
If the redundant controllers are not in Remote Program (REM) mode, the redundancy firmware upgrade cannot be completed.
2. Open RSLinx Classic software and browse to the redundancy module.
3. Right-click the redundancy module and choose Module Configuration.
4. Click the Configuration tab.
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 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.
Wait 45 seconds before you begin updating the 1756-RM or 1757-SRM firmware. During this time, the redundancy module conducts internal operations to prepare for an upgrade.
Complete these steps to upgrade the firmware of modules in the secondary chassis.
1. Launch ControlFlash software and click Next.
2. Select the redundancy module catalog number and click Next.
3. Browse to the redundancy 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 upgrade is complete, the Update status dialog box indicates completion.
Wait 45 seconds before you begin updating the secondary chassis firmware. During this time, the redundancy module conducts internal operations to prepare for an upgrade.
7. If you are replacing and upgrading your controller hardware, remove the controller from the secondary chassis and replace it with the new controller.
If you are replacing and upgrading your redundant controllers, verify that the planned secondary controller provides the same, or greater, memory as the primary controller.
Use this table to determine if your planned primary and secondary controllers can be used together in the redundant chassis.
Compatible Secondary Controller
8. Complete steps 2…6 for each module in the secondary chassis, including the new controller, if applicable.
Once you have upgraded the firmware for each of the modules in the secondary chassis, continue by preparing the RSLogix 5000 project for the upgrade.
Complete these steps to prepare the RSLogix 5000 program and controllers for the upgrade.
1. Launch RSLogix 5000 programming software and go online with the controller.
2. Verify that the watchdog time is set to a value that corresponds with the requirements of the redundancy firmware revision and your application.
See the Minimum Value for the Watchdog Time section on page 19 for information about calculating the minimum watchdog time.
3. Cancel or assemble any pending test edits.
4. Remove all SFC forces from the project.
5. Verify that no changes need to be made to:
• I/O forces.
• I/O configuration.
After this step, changes to I/O cannot be made until after the redundancy firmware upgrade is complete and both chassis are synchronized.
6. Save the project.
7. Go offline.
Controller Properties
8. Click Controller Properties.
9. Click Change Controller.
10. Specify the controller revision you are updating to.
11. If you installed a new controller while upgrading the primary chassis firmware, specify the new controller catalog number.
12. Click OK.
13. Access the Module Properties for each communication module in the chassis and specify the module firmware revision you are upgrading to.
If you are unable to specify the new revision, you may need to change the Electronic Keying parameter to Compatible Keying.
14. Save the project.
15. Download the project to the secondary controller.
The secondary controller is at the higher network address of the two available for the redundant chassis.
16. After the download is complete, go offline.
You are now ready to lock the system and initiate a locked switchover to update the primary chassis. Continue with Lock and Switchover the System for Update on page 30.
Once you have downloaded the RSLogix 5000 project you prepared, complete these steps to lock your system and initiate a switchover.
Remain offline while completing these steps.
Once you have locked the system, do not abort the system lock. Aborting the system lock during this procedure clears the project from the secondary controller.
Do not disconnect any communication cables while completing these steps.
Completing a locked switchover causes SFC instructions to be reset to their initial state. This may result in SFC instructions executing twice.
1. Open the RMCT for the 1756-RM module in the primary chassis.
2. Click the System Update tab.
3. Click Lock for Update, then click Yes.
4. Wait for the system to lock.
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 chassis status indicated in the bottom of the RMCT updates to reflect the switchover.
Once your locked switchover is complete, continue by updating the firmware of the modules in the new secondary chassis.
Verify that your chassis have been locked for update and that the locked switchover has completed successfully. Then complete these steps to upgrade the firmware of all of the modules in the new secondary chassis, except for the 1756-RM or 1757-SRM module that has already been updated (see the Update Primary 1756-RM or 1757-SRM Module Firmware section on page 25).
2. Select the module catalog number and click Next.
3. Browse to the module and select it.
8. Complete steps 2…6 for each module in the new secondary chassis, including the new controller, if applicable.
Once you have upgraded the firmware for each of the modules in the new secondary chassis, continue by synchronizing the redundant chassis.
Complete these steps to synchronize the redundant chassis after firmware in both chassis has been upgraded to the same revision.
1. Launch the RMCT for the 1756-RM module in the primary chassis.
2. Click the Configuration tab.
3. From the Auto-Synchronization pull-down menu, choose the frequency that suits your application.
4. Click Apply, then click Yes.
5. Set the redundancy module date and time according to your preference.
6. Click OK.
7. Close the RMCT.
Your upgrade of the redundant system is now complete.
These sections describe how to migrate your standard redundancy system from 1757-SRM modules to 1756-RM modules. Tasks specific to migrating include the following:
• Before You Begin on page 34
• Upgrade 1756-RM Module Firmware on page 34
• Replace the 1757-SRM Modules with 1756-RM Modules on page 35
If your standard redundancy system is operating at standard redundancy firmware revision 16.053, or earlier, complete the tasks in Upgrade from Revision 15.xxx, or Later on page 20 before you migrate from 1757-SRM modules to 1756-RM modules.
Also, prepare to replace the fiber-optic cable that connects the redundancy modules. You replace the 1756-SRC1 cable (multi-mode fiber with SC connectors) that connects the 1756-SRM modules with a 1756-RMC1 cable (single-mode fiber with LC connectors) that connects the 1756-RM modules.
Upgrade 1756-RM Module Firmware
1756-RM modules at boot firmware must be upgraded to standard redundancy revision 16.056 in a nonredundant chassis before being placed in a redundant chassis. We strongly suggest that you upgrade the 1756-RM module in a nonredundant chassis that has an empty slot. For example, an empty slot in a remote I/O chassis is ideal.
If no slots are available in a nonredundant chassis, complete these steps to upgrade your 1756-RM module from boot firmware in a redundant chassis.
1. Disqualify the chassis pair.
2. Remove power from the secondary chassis.
3. Disconnect the intermodule fiber-optic cable that connects the 1757-SRM modules.
4. Uninstall the 1757-SRM from the primary chassis.
5. Install the 1756-RM module in a now-empty slot that the 1757-SRM was in.
6. Wait for the 1756-RM module status display to indicate APPLICATION UPDATE REQUIRED.
7. Use ControlFlash software to upgrade the 1756-RM module firmware to revision 16.056.
When the upgrade is complete, uninstall the 1756-RM module.
Install the second 1756-RM module in the slot.
Use ControlFlash software to upgrade the second 1756-RM module firmware to revision 16.056.
Uninstall the second 1756-RM module.
Install the 1757-SRM into the slot and connect the intermodule fiber-optic cable that connects the two redundancy modules.
Replace the 1757-SRM Modules with 1756-RM Modules
After you have upgraded the 1756-RM module firmware to revision 16.056, complete these steps to replace the 1757-SRM modules with the 1756-RM modules.
1. If not yet disqualified, disqualify the redundant chassis.
2. Disconnect the intermodule fiber-optic cable from both of the 1757-SRM modules.
3. Remove the 1757-SRM modules in each chassis.
4. Install an 1756-RM module in one of the empty slots in each chassis.
5. Connect the intermodule fiber-optic cable between the 1756-RM modules.
The 1756-RM modules require a different intermodule fiber-optic cable than used with the 1757-SRM module. Connect the appropriate cable between the 1756-RM modules.
6. Wait for the 1756-RM modules to indicate PRIM and DISQ.
7. Use RSLinx Classic software to access the RMCT to do the following:
specify the date and time. configure redundancy settings according to your application. synchronize the system.
You can replace your current redundancy modules with 1756-RM2/A modules without initiating a switchover.
For the following steps, 'redundancy modules' refers to 1756-RM/A or 1756-RM/B modules.
Before executing these steps, review the most recent redundancy bundle release notes to determine the appropriate 1756-RM2 firmware revision and RMCT version required. You can find this information at the Product Compatibility and Download Center at http://www.rockwellautomation.com/support/downloads.html.
Install the compatible version of the RMCT software.
You must shut down RSLinx Classic software to perform the installation, and then restart RSLinx Classic software after the installation is complete.
On the RMCT Configuration tab, from the Auto-Synchronization pull-down menu, choose Never.
Using the RMCT, disqualify the redundant chassis pair (if not already disqualified.)
Unplug the fiber cable on both of the redundancy modules.
Close any open RMCT sessions connected to the current redundancy modules that are being replaced.
Remove the redundancy module pair (in any order) from the redundant chassis.
Insert the 1756-RM2/A redundancy module pair (in any order) in the redundant chassis into the same slots as the redundancy modules.
If not already installed, use RSLinx Classic software to upload the EDS file for the 1756-RM2/A module.
If needed, obtain the EDS file for the 1756-RM2/A module. Right-click the module in RSWho and choose 'Upload EDS file from device'.
Update the primary and secondary 1756-RM2/A modules to the appropriate firmware revision.
Reconnect the fiber cable on either CH1 or CH2 of the 1756-RM2/A redundancy module.
Optional: Connect a second fiber cable on the remaining channel for fiber redundancy.
Wait for at least 45 seconds after connecting the fiber cables.
Launch the RMCT again for the newly-installed 1756-RM2/A modules.
On the RMCT Configuration tab, from the Auto Synchronization pull-down menu, choose your original value.
Using the RMCT, synchronize the system again (if it is not already qualified).
Use this procedure to store an updated project and firmware to the nonvolatile memory of the controller while your process is running.
1. Verify that the redundant chassis are synchronized.
If the redundant chassis are not synchronized, synchronize them before continuing with the next step.
2. In the RMCT, click the Configuration tab and from the Auto-Synchronization pull-down menu, choose Never.
3. In the Synchronization tab, click Disqualify Secondary.
4. In RSLogix 5000 programming software, go online with the secondary controller.
5. Use the steps described in the Logix5000 Controllers Nonvolatile Memory Programming Manual, publication 1756-PM017 to store the project.
Remain offline after you have stored the project to nonvolatile memory. You must stay offline through the remainder of this procedure.
6. In the RMCT, set the Auto-Synchronization parameter according to your preference.
7. Synchronize the chassis.
These documents contain additional information concerning related products from Rockwell Automation.
ControlLogix Redundancy System User Manual, publication 1756-UM523
Provides design, installation, and troubleshooting information specific to the standard redundancy system.
Rockwell Automation'sTechnical Support Knowledgebase, http://www.rockwellautomation.com/knowledgebase/
Provides details about how to assemble and mount the controller, how to upgrade firmware, and controller technical specifications.
ProcessLogix and ControlLogix System Redundancy Module Installation Instructions, publication 1757-IN092
Contains information on how to install the 1757-SRM, Series B ProcessLogix and ControlLogix System Redundancy Module into the ProcessLogix or ControlLogix redundant chassis pair.
ControlFlash Firmware Upgrade Kit Quick Start, publication 1756-QS105
Contains information on how to upgrade module firmware.
ControlLogix Controllers User Manual, publication
Contains information on how to install, configure, program, and operate a ControlLogix system.
Product Certifications website, http://ab.com
Provides declarations of conformity, certificates, and other certification details.
You can view or download publications at http://literature.rockwellautomation.com. To order paper copies of technical documentation, contact your local Allen-Bradley distributor or Rockwell Automation sales representative.
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.com/knowledgebase for FAQs, technical information, support chat and forums, software updates, and to sign up for product notification updates.
For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect sm support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/support/.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact Customer Support for initial help in getting your product up and running.
United States or Canada
Outside United States or Canada
Use the Worldwide Locator at http://www.rockwellautomation.com/support/americas/phone_en.html, or contact your local Rockwell Automation representative.
New Product Satisfaction Return
Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States
Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to complete the return process.
Outside United States
Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Allen-Bradley, Rockwell Software, Rockwell Automation, VersaView, PanelView, RSView, RSLinx, RSLogix, RSNetWorx, FactoryTalk, Logix 5000, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400
Publication 1756-RN628M-EN-E - November 2012
Supersedes Publication 1756-RN628L-EN-E - July 2012
Copyright © 2012 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.


text:
Using recursion to create a one line number pattern
Write a recursive method that prints out a numeric sequence. printSequence(4) prints 1 2 3 4 3 2 1
public class Practice {
public static void main(String[] args){
public static void printSequence(int n){
My code is there, and the output is pretty obvious, but it's 43211234. My desired output is 1234321, and I'm not sure how to get there. Unless I can use two methods, but only call one in main, I don't think I can use two methods.
Does anyone know how I can get my desired output:
1 2 3 4 3 2 1 recursively, and only using one method?
See also questions close to this topic
Java: final string comparison does not work
I have created final strings for certain commands but when I try to check if the command given by the user matches, it does not work.
These are examples of my final strings:
public static final String END = "quit"; public static final String SHOW = "print";
But if I were to use it e.g. like this:
String command = scanner.nextLine(); if (command == SHOW) { System.out.println("Print this line."); }
It sees that they do not match even if they do. I tried printing the finalized variables:
and it prints its value, but for some reason when I compare them to identical strings provided by the user, it does not recognize them.
I have tried to search similar examples and read about finalizing variables, but I think I am missing something important. I know that the problem is with the final variables and not elsewhere, because the program works if I compare these same strings with equal. E.g:
String command = scanner.nextLine(); if (command.equals("print") { System.out.println("Print this line."); }
I am assuming that there is something very simple that I am doing wrong, but I could not find any answer anywhere that I would understand. I am still a beginner and all the other examples regarding similar questions include some features that I don't understand, so they don't help me to see what I am doing wrong.
Stack class in java.util a violation of Liskov substitution principle?
From the documentation of https://docs.oracle.com/javase/7/docs/api/java/util/Stack.html
public class Stack<E> extends Vector<E>
Isn't this a violation of the Liskov substitution principle? The LSP in simple terms states that objects of the same superclass should be able to be swapped with each other without breaking anything.
For example: Let us say that I have a function that takes a Vector as an input. If while calling a function I start passing it a Stack then it might break because Stack prevents random access of elements.
import java.util.*; class Book {} class TextBook extends Book {} public class Sample { public static void process(Vector<Book> books) { # This should not be allowed for Stack, Stack is FILO System.out.println(books.get(1)); } public static void main(String[] args) { Vector<Book> books = new Vector<>(); books.add(new Book()); books.add(new Book()); books.add(new Book()); process(books); System.out.println("ok"); Stack<Book> bookz = new Stack(); bookz.add(new Book()); bookz.add(new Book()); bookz.add(new Book()); process(bookz); System.out.println("ok"); } }
Can i combine unicode categories in Regex?
I want to get such set of symbols:
\P{L}unicode category use as base
- add
хХxXтТTоОoO0symbols to
\P{L}unicode category
- do not use symbols
By that i get such regex in Java:
But this not working, what's wrong?
Time Limit Exceeded - Recondtructing Binary Tree
Trying to practice using inorder and postorder arrays to reconstruct a binary tree. My code works with small inputs and some different edge cases but when I have a super large postorder and inorder array, it times out and not sure why. Any way that I can refactor this to make it faster? I'm thinking using a dictionary to store the indices, but not sure where I should place the mapped array indices in this code.
def buildTree(inorder, postorder): # base case: if inorder == null: return null (L and R trees do not exist) # Determine root from postorder # Determine L and R subtrees from inorder # create node from root # assign node.left to left tree and node.right to right tree # return root if not inorder: return None else: rootVal = postorder[-1] rootNode = TreeNode(rootVal) for i in range(len(inorder)): if inorder[i] == rootVal: rootIndex = i break # default if no L or no R subtree rightInST, leftInST = [], [] if rootIndex + 1 < len(inorder): # right tree found rightInST = inorder[rootIndex + 1:] if rootIndex > 0: # left tree found leftInST = inorder[:rootIndex] rightPostST = [x for x in postorder if x in rightInST] leftPostST = [x for x in postorder if x in leftInST] rootNode.right = buildTree(rightInST, rightPostST) rootNode.left = buildTree(leftInST, leftPostST) return rootNode
Get all combinations for arbitrary number of elements
How can I make a method in Java which obtains input integer
n, and an array of double
x, and returns all combinations of n elements out of values in x.
x={1,2,3}and n=2,
the expected returns/combinations are
{1,1},{1,2},{1,3},{2,2},{2,1},{2,3},{3,1},{3,2},{3,3}(the order is not ignored.) The number should be
(int) Math.pow(x.length, n)
static List<Double[]> getAll(int n, double[] x){ List<Double[]> combinations = new ArrayList<>(); //number of combinations should be x.length ^ n // when n = 1; for (int i=0;i<x.length;i++) combinations.add({x[i]}); return combinations; } // return patterns[i] is the i th pattern //which contains num-elements from the input depths, // patterns[i][j] is the j th double in patterns[i] private double[][] void makePatterns(int num, double[] depths) { int patternN = (int) Math.pow(depths.length, num); double[][] patterns = new double[patternN][num]; System.out.println(patterns.length); int i = 0; int k = 0; while (i < patternN) { for (int j = 0; j < num; j++) { // System.out.println(i+" "+j+" "+(i / (int)Math.pow(depths.length, j))%depths.length); patterns[i][j] = x[(i / (int)Math.pow(depths.length, j))%depths.length]; } i++; } return patterns; }
makePatternsis where I started...
How to translate this from template?
def build_repr(operations, templates): """ Build the representation of the series of operations with the given templates. The operations are prioritized from right to left. Restrictions: You should use recursion. You should do input validation. Parameters: operations (list(str)): List of numbers and operations to be executed on them Returns: (str): String representation of the operations >>> build_repr([0, '+', 1, '-', 3], {'+': '({0}, +, {1})', '-':\ '({0}, -, {1})'}) '(0, +, (1, -, 3))' >>> build_repr([0, '+', 1, '-', 3], \ {'+': '({0}, add, {1})', '-':'({0}, minus, {1})'}) '(0, add, (1, minus, 3))' >>> build_repr([0, '+', 1, '-', 3], \ {'+': '({0}, add, {1})', '-': '({0}, minus, {1})'}) '(0, add, (1, minus, 3))' """

subset: commoncrawl


text:
New Post
Related topics
Hey guys! It's almost spring time. And that has my in a very reflective mindset. It also makes me want to travel. (Who doesn't get FOMO from th...
Read more ›
by @LoveandDream33
Hey guys! Before we get started I have three things to say ~1) How cute is the smile of the guy in my cover photo??? (I think very!)2) This...
Read more ›
by @honeysugarxx
it snowed last nightWhat made this snow significant is that it hasn't snowed at all in my town this winter. Even though it only snowed a little...
Read more ›
by @ambyion
Hello!SO, recently I have discovered the album of SZA and it is giving me some vibe so chill and something that seems to be emptiness.SZA -...
Read more ›
by @youarebored
Sign in with Facebook or Twitter to start your gallery.
Sign in with Facebook
Sign in with Twitter
Have a We Heart It account?
Follow user
Unfollow user
Unfollow collections
You have now unfollowed
Unfollow all
Unfollow collection
Are you sure you want to unfollow the collection "" by (@)?
Are you sure you want to unfollow all collections for this entry by (@)?
Are you sure you want to unfollow all hearts and collections from (@)?


text:
Local Blogs
By Cheryl Bac
E-mail Cheryl Bac | Follow this Blog
Sort by: Most Recent | Most Popular
Feb 24, 2020 10:10 am
Comments: 0 | Views: 579
When I see a little one throwing a tantrum in a public place, like a restaurant or a grocery store, I usually just try to give the parents space. I know they want... More
Feb 19, 2020 11:47 am
Comments: 12 | Views: 1,748
Over the weekend we were planning to take our kids to Talbots Toyland. Sadly we discovered that the store recently closed. We... More
Feb 13, 2020 9:21 am
Comments: 0 | Views: 1,049
Unlike Christmas, our family doesn't have many Valentine's Day traditions.
We usually make and decorate heart-shaped cookies. We make valentines for friends... More
Jan 30, 2020 11:20 am
Comments: 4 | Views: 1,115
When our kids were babies, I expected to be sleep deprived. As our kids grew up and learned to sleep for longer stretches of time, I expected to get more and more... More
Jan 22, 2020 2:38 pm
Comments: 0 | Views: 1,371
Our daughters have a wide array of jackets and sweaters. However, most of the time they choose to leave these pieces of clothing at home, in the minivan, or in... More
Stay informed
Get daily headlines sent straight to your inbox.
Portland's Thai food darling Pok Pok will be popping up on the Peninsula this spring
By Elena Kadvany | 2 comments | 3,437 views
Flying: How to lower your impact
By Sherry Listgarten | 16 comments | 2,835 views
Premarital and Couples: Here Be Dragons!
By Chandrama Anderson | 1 comment | 2,285 views
Pseudo-Primary for CA Senate District 13: some thoughts
By Douglas Moran | 3 comments | 1,429 views
Overachieving in High School: Is It Worth It?
By Jessica Zang | 6 comments | 1,369 views
Short story writers wanted!
The 34th Annual Palo Alto Weekly Short Story Contest is now accepting entries for Adult, Young Adult and Teen categories. Send us your short story (2,500 words or less) and entry form by March 27, 2020. First, Second and Third Place prizes awarded in each category. Sponsored by Kepler's Books, Linden Tree Books and Bell's Books.


text:
dash door photo of door dash ca united states gonna take up.
angle custom door panels with pockets and, officially a door dash driver,v interior full dash trim kit w door panels , universal under dash courtesy light and door jam switch harness, how to unlock secret door in vault geometry dash world, new car body dash door trim panel wedge clip remover removal pry, auto car fastener bumper clips tool plastic dash trim removal door, carbon fiber door panel and dash trim decal kit, delivery now available from via door dash, painted door dash panel inserts.
Related Post
Double Vessel Sink Recessed Lighting Ideas For Living Room Fun Office Chairs Shower Head Plumbing Covered Patio Design Table Liner Flush Mount Outdoor Ceiling Fans Window Film And More Adjustable Stool With Back Free Standing Electric Fireplace Outswing Door Security Bar Navy Sectional Couch Table Top Christmas Tree Decorated House For Sale Louisville Ky Vessel Sink Vanity Bases


text:
Re-Issue Rock N Roll Band
Formed in 2017, we are a five or six-piece vintage rock and roll band specialising in covers from the 1950s and 1960s. Alan, Ed and Mandy have been playing together for many years. Graham is ex of the punk band Void.
We are based in the south of England with members living in the New Forest, Southampton and Somerset. We play pubs, clubs, festivals, parties and other functions and events.
Alan House, drums and vocals; Graham Cowling, lead guitar and vocals; Mandy Alderson, vocals and drums; Ed Niziolek, bass; Scott Sinclair, keyboards.
- 21 March – 8.30pm
Everton & Lymore Social Club, SO41 0JJ
- 28 March – 9pm
Lymington RBL, SO41 9AD
- 18 April – 8.30pm
Fawley RBL, SO45 1XD
- 25 April – 8.30pm
Ashley Wood Golf Club, Blandford, DT11 9HN
- 15 May – 9pm
Wyke Regis Working Men's Club, Weymouth, DT4 9AB
- 4 July – 9pm
The Academy, Basingstoke, RG22 5EE
- 11 July – 8.15pm
Chandler's Ford Central Club, SO53 2FS
- 22 August – 8.30pm
Liphook & Bramshott Social Club, GU30 7HP
- 26 September – 9pm
Lymington RBL, SO41 9AD
- 3 October – 9pm
Wyke Regis Working Men's Club, Weymouth, DT4 9AB
- 21 November – 8.30pm
Everton & Lymore Social Club, SO41 0JJ
- 31 December – 8.30pm
Fawley RBL, SO45 1XD


text:
Home > Members Area > Protected: Leaders Links
This content is password protected for security reasons. Please enter your password below. If you don't have one, please speak to our team.
Aged 6+? Join Scouting today in just a few clicks. Start here.
Jersey Scout Association Annual General Meeting 5th September 2019
12th Mar
7:00 pm - 9:00 pm
24th Mar
7:00 pm - 10:00 pm
25th Mar - 26th Mar
6:30 pm - 9:30 pm


text:
Brawny Latino takes a enormous tilt inside his meet interfere
Big Cock,Amateur,Latin,Gay Muscular Latino takes a huge cock in his butt
Glasses - 16-04-2019 - 42.9K views
Charming Porn FuckBook Video Three in jail
Glasses - 04-06-2019 - 40.2K views
Awesome Video 18+ more daddy wanking
Glasses - 19-03-2017 - 15.3K views
Breathtaking Hot xxx Video Oriental twink team nailed hard passing the time
Glasses - 04-03-2019 - 37.4K views
Bomb Porn clips Ejiki kumapoo 002 end
Glasses - 16-03-2017 - 75.5K views
Delicious Naked Porn tube Jay and max hammer
Glasses - 13-05-2016 - 87.7K views
Seductive Naked FuckBook Video bar donnys gay lesbian pittsburgh Im getting drilled by my Bf, this chab pushes his weenie in in natures garb und drilled until a good creampie comes out my lewd aperture.
Kevin At Tonton Dick !
Male Self Spank and Soap
Ace Hanson Bottoms
Brock Jacobs Performs Live In Front Of Webcam With Very Sexual Moans
Doggystyle fucked stud gets anally pounded
All Amateur Bears 3
PACK ATTACK 6 MARC DYLAN - Scene 2
Black fucking twink bareback
Sucking a young black dick!
Exotic male in horny amature, blond boys homosexual adult video
Rocker boy gets fucked
Twink Threeway
Vintage thong wrestl
Skater Bareback Orgy
Fabulous male in hottest blowjob, twinks homosexual xxx scene
Gay Cross-dresser Emerson Beddome 27
Brothers Kiss Gay Short Film
Twinks Good Hard Fuck
Young Bearded Latino Jacking Off


text:
How much does a Chief Ultrasound Technologist make in Loveland, CO? The average Chief Ultrasound Technologist salary in Loveland, CO is $92,888 as of January 20, 2020, but the range typically falls between $83,524 and $102,745. Salary ranges can vary widely depending on many important factors, including education, certifications, additional skills, the number of years you have spent in your profession. With more online, real-time compensation data than any other website, Salary.com helps you determine your exact pay target.
Chief Ultrasound Technologist oversees Ultrasound Technologists and maintains the technical aspects of ultrasound services. Acts as a liaison between technologists, physicians and area support staff. Being a Chief Ultrasound Technologist suggests equipment modification and evaluates accuracy and quality of ultrasound images. May perform duties of Ultrasound Technologist as needed. Additionally, Chief Ultrasound Technologist requires an associate degree. May require completion from an approved one-year program in Ultrasound Technology. Requires registration with the American Registry of Diagnostic Medical Sonographers (ARDMS). Typically reports to a manager or director. The Chief Ultrasound Technologist typically manages through subordinate managers and professionals in larger groups of moderate complexity. Provides input to strategic decisions that affect the functional area of responsibility. May give input into developing the budget. Capable of resolving escalated issues arising from operations and requiring coordination with other departments. To be a Chief Ultrasound Technologist typically requires 3+ years of managerial experience. (Copyright 2020 Salary.com)
See user submitted job responsibilities for Chief Ultrasound Technologist.
Salary.com's CompAnalyst platform offers:
|City, State
|Compared to national average
|City, State San Francisco, CA
Compared to national average
+ 25.3%
|City, State Washington, DC
Compared to national average
+ 10.7%
|City, State Miami, FL
Compared to national average
|City, State Chicago, IL
Compared to national average
+ 6.0%
|City, State Boston, MA
Compared to national average
+ 12.9%
|City, State New York, NY
Compared to national average
+ 21.0%
|City, State Dallas, TX
Compared to national average
|Job Title
|Salary Compared to This Job
|Job Title Chief CAT Scan Technologist
|Experience 5 +
Salary Compared to This Job
- 9.0%
|Job Title Chief Diagnostic Imaging Operations Technologist
Salary Compared to This Job
+ 3.3%
|Job Title Chief Financial Officer
Salary Compared to This Job
+ 100.0%
|Job Title Chief Medical Technologist
|Experience 5 +
Salary Compared to This Job
- 12.7%
|Job Title Chief MRI Technologist
|Experience 5 +
Salary Compared to This Job
- 5.4%
Take just three simple steps below to generate your own personalized salary report
Core compensation
Includes base and annual incentives
About Loveland, Colorado Loveland is the Home Rule Municipality that is the second most populous municipality in Larimer County, Colorado, United States. Loveland is situated....More
Loveland, Colorado area prices were up 2.3% from a year ago View the Cost of Living in Loveland, Colorado
Chief Ultrasound Technologist Salary in popular cities: Denver, Colorado Springs, Aurora
Skills associated with Chief Ultrasound Technologist: Diagnostic Imaging, Electronic health records (EHR) Software, Physician Support, Perform Diagnostic Tests ...More
Salary estimation for Chief Ultrasound Technologist at companies like : BRIGHT HORIZONS FAMILY SOLUTIONS INC., FONAR CORP, PRECIPIO, INC.


text:
technologies for intelligent mines
infomine provides comprehensive information on mining, the mining industry, mining technology and mineral exploration. infomine categories include mining news, miningGet Price
global mining market intelligence
global mining market intelligence - keep up-to-date with new developments in the global mining market. cost-effective and in-depth mining market data at your fingertips.Get Price
improving safety and productivity
mst global - mine site technologies mine agency alert system is installed in many mines, our technology provides intelligent applications and managementGet Price
robotics, automation & design
robotics, automation & design research area develop computational technologies that embed intelligence for fault detection and robots and intelligentGet Price
intelligent information technologies: concepts, methodologies
intelligent information technologies: concepts, methodologies, tools and applications: 9781599049410: computer science books @Get Price
intelligent technology archives
institut mines-télécom. news. social wall; press release; agenda; schools agenda; presentation. the institut in brief; key figures; organisation chart; statuses andGet Price
innovative technologies and concepts for the intelligent deep
innovative technologies and concepts for innovative technologies and concepts for the intelligent deep only these eco-efficient mines will contributeGet Price
pdf intelligent integration of mineral processing technologies
intelligent integration of mineral processing technologies for sustainable mining waste treatment dr. eugene lakay november 2014Get Price
mining technology | technology solutions for mining | technomine
mine technology, technology in mining, technomine is the expanding source of news, views, opinions, and information on mining technology.Get Price
pdf mine of the future brochure
02 the mine of the future™ programme is creating next-generation systems and technologies to drive rio tinto to become a global leader in fullyGet Price
technologies for intelligent mines
cdc - mining project - intelligent safety technologies for mining... this project will investigate the implementation and integration of existing and emergingGet Price
about remrsec
remrsec | about renewable changes in pv and other optoelectronic technologies through significant improvements in for the intelligent design of novelGet Price
intelligent mining, sensing and automation
intelligent mining, sensing and automation technologies and smarter processes that drive down costs and environmental impacts designing safer open pit mines.Get Price
abb process control and automation solutions for mines
process control and automation solutions for mining and mines tend to have a large number of and operational technologies (ot): intelligentGet Price
an exciting era of automation
an exciting era of automation. technologies is expected to play a key role in helping mining companies tackle "smart mines are more competitive from theGet Price
what is the applications of intelligent helmet in coal mines
intelligent helmet for coal mines using zigbee the atmost mine site technologies . coal a distance grid other applications of gis in mining intelligent minesGet Price
intelligent and low impact mines
new mining technologies and regulations have significantly improved mining efficiency we understand that intelligent and low impact mines costs a lot more moneyGet Price
welcome to the mine intelligence research group (mirg
technologies & partners; products therefore research at the mine intelligence research group (mirg) researchers develop and implement products into mines andGet Price
google buys uk artificial intelligence startup deepmind for £
google has made one its largest european acquisitions to date with a deal to buy deepmind technologies, a london-based artificial intelligence firm which specialisesGet Price
sustainable intelligent mining systems
in order to realize the vision of a sustainable intelligent mine with safe working conditions, high efficiency and low environmental impact, several new technologiesGet Price
to investigate the implementation and integration of existing and emerging technologies in surface and underground mines to provide automatic, intelligent protectionsGet Price
smart grid
a smart grid is an electrical grid which includes a variety of operational and energy measures including smart meters, smart appliances, renewable energy resourcesGet Price
project overview | i2mine
i2mine. innovative (innovative technologies and concepts for the intelligent deep mine of methods and rock mechanics that will be demanded by deeper mines andGet Price
pdf fiber optic sensors-based intelligent coal mines
fiber optic sensors-based intelligent coal mines t major effort has been made in recent years in china on research and development of advanced technologies toGet Price
- saudi arabia jaw crusher kemco
- el midhya oil mills
- development of mining policy in zimbabwe
- hydraulic cone crusher pdf
- crusher plant maintenace in uae
- ff14 leves of quarry mill
- limestone mining term of reference
- vibrating ball mill introduction
- gravel rings and aggregated stones suppliers in dubai
- application of coal in industry
- magotteaux grinding media sorting machine
- sepatu safety crusher yang ada di medan


text:
Hi There! Is this Your First Time?
Did you know if you Register you have access to free search tools including the ability to save listings and property searches? Did you know that you can bypass the search altogether and have listings sent directly to your email address? Check out our how-to page for more info.
- Price$599,000
- Beds5
- Baths5
- SQ. Feet3,105
- Acres15.95
- Built1820
350 Cushman Road, Patterson
With 14 rooms and 6 fireplaces, this antique colonial on 15.95 acres, located on sought after Cushman Road, has 5 bedrooms, and 4.5 baths. Beautiful sun-lit living room with fireplace, built-ins, and french doors to a large patio. Large formal dining room with fireplace leads to the butler's pantry and eat-in-kitchen. Bedroom, den/office, full bath, paneled study with fireplace and powder room, laundry room. The second floor offers a Master Suite with FPL, bath and walk-in-closet, hall bath, bedroom, study, bedroom/FPL, hall Bath, bedroom/FPL. Front and rear staircases, wide board floors and many built-ins. Charming finished space over two car garage offers a great room, two additional rooms, and full bath perfect for home office, yoga studio, artist studio, etc. A barn, majestic old trees, stone walls and beautiful land complete this enchanting property. Make your new memories here. Addl. land available. Horse property. Perfect full-time or weekend residence. Taxes w/o Star of $1273
Essential Information
- Price$599,000
- Bedrooms5
- Bathrooms5.00
- Full Baths4
- Half Baths1
- Square Footage3,105
- Acres15.95
- Taxes$22,508
- Year Built1820
- TypeSingle Family
- StyleColonial
- StatusActive
- HeatingForced Air
- CoolingNone
- Has BasementYes
- BasementPartial
- FireplaceYes
- # of Fireplaces6
- # of Stories2
Community Information
- Address350 Cushman Road
- AreaPatterson
- CityPatterson
- CountyPutnam
- StateNY
- Zip Code12563
- ConstructionClap Board
- Lot DescriptionLevel, Possible Sub Division, Partly Wooded, Stone/Brick Wall
- ExteriorFrame
Additional Information
- Levels2
- Amenities1st Floor Bedrm, Close to Shops, Hardwood Floors As Seen, Barn, Close to Railroad, Eat in Kitchen, Formal Dining Room, Foyer, Guest Quarters, Horse Property, Laundry Room/Private, Master Bath, Out Building, Patio, Pantry, Privacy, Powder Room, Storage, Walk In Closet
- IncludedB/I Shelves, Chandelier(s), Garage Remote, Garage Door Opener, Light Fixtures, Oven/Range, Refrigerator
- Parking2 Car Detached
School Information
- DistrictCarmel
- ElementaryMatthew Paterson
- MiddleGeorge Fischer
- HighCarmel
Listings Similar to 350 Cushman Road, Patterson
- 5 Beds
- 5.0 Baths
- 3,105 SqFt
Single Family
Patterson, NY
- 5 Beds
- 3.0 Baths
- 5,344 SqFt
Single Family
Patterson, NY
- 4 Beds
- 3.0 Baths
- 3,200 SqFt
Single Family
Patterson, NY
- 2 Beds
- 4.0 Baths
- 3,414 SqFt
Single Family
Patterson, NY
- 3 Beds
- 3.0 Baths
- 2,240 SqFt
Single Family
Patterson, NY
- 3 Beds
- 3.0 Baths
- 1,968 SqFt
Single Family
Patterson, NY
- 3 Beds
- 3.0 Baths
- 2,705 SqFt
Single Family
Patterson, NY
- 3 Beds
- 3.0 Baths
- 2,924 SqFt
Single Family
Patterson, NY
The data relating to real estate for sale or lease on this web site comes in part from HGMLS. Real estate listings held by brokerage firms other than RE/Max Classic Realty are marked with the HGMLS logo or an abbreviated logo and detailed information about them includes the name of the listing broker.
Information deemed reliable but not guaranteed.
© 2020 Hudson Gateway Multiple Listing Service, Inc. All rights reserved.
Listing information last updated on February 19th, 2020 at 9:43am EST.
Listing Courtesy of: Houlihan Lawrence Inc..


text:
This erotic video opens with a mature blond and torrid mistress who is changing her mind with vibrators with the help of her friend. Here is a nice whore who seems to want to fuck, so the guy caresses her tits, takes off her shoes and shoves her tail into the nympho's mouth. They caress her face and don't forget to touch her breasts ; they stick their finger in the chick's buttocks to excite her more and smash the mold and butt like an authentic nymphomaniac. As a result of the fact that they met in a guest room, our fat whore prepared herself accordingly to welcome the guy. Afterwards, the guy lifts her up and puts her on with hunting comings and goings so that she can be hunted.
Pornstars : Alison Star
Channels : Hoodamateurs, Pengav, Bigboobsfilm, Camsoda