1756 rm010 - en P
1756 rm010 - en P
1756 rm010 - en P
Original Instructions
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are
required to be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may
be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from
the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or
liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or
software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation,
Inc., is prohibited
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous
environment, which may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous
voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may
reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to
potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL
Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Migration Services and Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 1
Update Considerations Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
LINT Members must align on 8-byte Boundaries . . . . . . . . . . . . . 8
I/O Modules in Redundancy Systems . . . . . . . . . . . . . . . . . . . . . . . . 9
Verify Your RMCT Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Download and Install ControlFLASH Software Version 14.01.00. 11
Install ControlFLASH Software Version 14.01.00 . . . . . . . . . . . 12
Download the Redundancy Firmware Bundle and RMCT. . . . . . . . 15
Install the Redundancy Firmware Bundle . . . . . . . . . . . . . . . . . . . . . . . 17
Install the revision 24.052 Redundancy Firmware Bundle . . . . . 17
Install the revision 30.051 Redundancy Firmware Bundle . . . . . 18
Install the Redundancy Module Configuration Tool . . . . . . . . . . . . . 20
Install the Logix Designer Application . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Prepare the Controller Project for the Update . . . . . . . . . . . . . . . . . . . 22
Update the Redundancy System Firmware . . . . . . . . . . . . . . . . . . . . . . 24
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Prepare the Redundant Chassis for the Firmware Update . . . . . 25
Update the Redundancy Module Firmware in the
Primary Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Update Redundancy Module Firmware and Other Module
Firmware in the Secondary Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . 29
Lock the System and Initiate a Switchover to Update . . . . . . . . . 31
Update the New Secondary Chassis Firmware . . . . . . . . . . . . . . . 33
Synchronize the Redundant Chassis. . . . . . . . . . . . . . . . . . . . . . . . . 35
EDS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Chapter 2
Replacement Considerations Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Replace a Module in the Secondary Chassis that has the
Same Catalog Number and Firmware Revision . . . . . . . . . . . . . . . . . . 38
Replace an EtherNet/IP Module with a New Series . . . . . . . . . . . . . . 39
Synchronization and Switchover for EtherNet/IP Modules . . . 39
Replace a 1756-CN2 Module with a New Series . . . . . . . . . . . . . . . . . 44
Synchronization and Switchover for the ControlNet Modules 44
Replace a 1756-RM Module with a 1756-RM2 Module . . . . . . . . . . 49
Appendix A
Align LINT Members on 8-byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Boundaries
Summary of Changes This table contains the changes made to this revision.
Topic Page
Added references and special instructions for redundancy firmware revision 30.051 Throughout
Organized the Update Considerations and Replacement Considerations chapters to Throughout
provide a more consistent flow.
Added Appendix A: Align LINT Members on 8-byte Boundaries 51
You can access release notes for each redundancy firmware revision from the
Rockwell Automation Product Compatibility and Download Center
(PCDC). Go to http://www.rockwellautomation.com/global/support/
pcdc.page, and search for your redundancy firmware revision.
Migration Services and Tools Throughout the product lifecycle, as products mature, Rockwell Automation
is there as your partner to help you get the most out of your current equipment.
Rockwell Automation also helps you determine your next steps and lay out a
plan for the transition to newer technology.
Rockwell Automation has the tools and the experience to guide you through
the transition, whether you choose to migrate all at once or use our unique,
phased approach.
For tools that assist with planning and configuring an Integrated Architecture
system, see http://www.rockwellautomation.com/rockwellautomation/
products-technologies/integrated-architecture/tools/overview.page?#/tab1
Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Resource Description
1756 ControlLogix Controllers Specifications Technical Data, publication 1756-TD001 Technical specifications for ControlLogix controllers and accessories, including
redundancy modules.
ControlLogix Redundancy User Manual, publication 1756-UM535 Provides information to install, configure, and use redundancy systems.
Migration Solutions Brochure, publication MIGRAT-BR002 Provides information about migration.
Integrated Architecture Tools and Resources website, Provides Integrated Architecture tools and information.
http://www.rockwellautomation.com/global/products-technologies/integrated-
architecture/tools/overview.page?#/tab1
Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1 General guidelines for installing a Rockwell Automation industrial system.
Product Certifications website, Declarations of conformity, certificates, and other certification details.
http://www.rockwellautomation.com/global/certification/overview.page
Update Considerations
Topic Page
Before You Begin 7
Download and Install ControlFLASH Software Version 14.01.00 11
Download the Redundancy Firmware Bundle and RMCT 15
Install the Redundancy Firmware Bundle 17
Install the Redundancy Module Configuration Tool 20
Install the Logix Designer Application 21
Prepare the Controller Project for the Update 22
Update the Redundancy System Firmware 24
Before You Begin When updating products in a ControlLogix redundancy system, you must:
Download and install the appropriate redundancy firmware bundle, and
the compatible versions of the Studio 5000 Logix Designer application,
RSLinx Classic, ControlFLASH software, and the Redundancy
Module Configuration Tool (RMCT)
Update the firmware on the redundancy modules, controllers, and
communication modules in the redundancy chassis pair.
Update the revision of controller and communication module firmware
in the redundancy application project.
IMPORTANT If you are migrating to redundancy revision 30.051, you must have the
redundancy-enabled project on your computer that was originally
downloaded to the controller before you begin the update.
If your computer does not have the redundancy-enabled project that was
originally downloaded to the controller, any attempt to upload the project
from the controller fails.
IMPORTANT If you have User-defined Data Types (UDT) that contain LINT members, you
may not be able perform the online Redundancy System Update. See the
ControlLogix Redundancy User Manual, publication 1756-UM535, on how to
install and update the modules, firmware, and application software versions
while offline.
This change impacts your Logix Designer application project if any of the
following situations are true:
You migrate a standard project, version 26 or earlier, to a redundancy
project that is version 30.051 or later, and you have LINT tags inside a
UDT.
You migrate a redundancy project, version 24.052 or earlier, to a project
that is version 30.051 or later, and you have LINT tags inside a UDT.
You use a tag with LINT members as a producer, and at least one
consumer (controller) has firmware earlier than version 27.
You use a tag with LINT members as a consumer, and the producer
(controller) has firmware earlier than version 27.
In a redundancy system, you can use only I/O modules in a remote chassis. You
cannot use I/O modules in the redundant chassis pair.
This table describes the I/O modules that redundancy systems support.
IMPORTANT If you have RMCT version 7 or earlier, it does not support the 1756-RM2
modules. You need RMCT version 8 for revision 24.052_kit1 or later.
IMPORTANT You must uninstall any existing version of the Redundancy Module
Configuration Tool (RMCT) before you install the RMCT, version 8.4.1.0. If you
do not uninstall the previous version, you can have difficulty if you try to
uninstall version 8.4.1.0 later.
Complete these steps to check or verify the version of the RMCT you have
installed.
TIP If Module Configuration is not available in the list of options, RMCT version 8
has not been installed.
The About dialog box opens and indicates the RMCT version.
TIP The RMCT launches at the version that is compatible with the 1756-RM2
or 1756-RM2XT redundancy module firmware that is installed.
You must update your RMCT version and the redundancy module
firmware revision so it is compatible with the new RMCT version. If you
do not perform this update, the About dialog box cannot reflect the new
RMCT version.
Download and Install If you are upgrading to redundancy firmware revision 30.051, ControlFLASH
software version 14.01.00 is not included in redundancy firmware revision
ControlFLASH Software 30.051_kit1. You must download it separately.
Version 14.01.00
IMPORTANT If you are only upgrading to redundancy firmware revision 24.052, the
compatible version of ControlFLASH software is included in redundancy
firmware version 24.052_kit1. However, ControlFLASH 14.01.00 is
compatible with redundancy firmware revision 24.052.
3. Click Download.
5. On the Available Downloads dialog, select the firmware and click on the
Downloads cart.
Download the Redundancy To download the appropriate redundancy firmware bundle, follow these steps:
Firmware Bundle and RMCT 1. Go to http://www.rockwellautomation.com/global/support/firmware/
overview.page.
5. Click Downloads.
6. On the Downloads page, click the Show Downloads icon.
7. On the Available Downloads dialog, select the Firmware and click the
Downloads Cart.
8. On the Download Cart dialog, make sure the firmware is selected, and
click Download now.
1. Go to http://www.rockwellautomation.com/global/support/firmware/
overview.page.
Install the Redundancy This section details how to install the Redundancy Firmware Bundle.
Firmware Bundle If you are updating from revision 20.05x to revision 24.052, see Install
the revision 24.052 Redundancy Firmware Bundle on page 17.
If you are updating from revision 24.052 to revision 30.051, see Install
the revision 30.051 Redundancy Firmware Bundle on page 18.
Before you update software for your redundant system, use one of these
methods to 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.
6. Click Close.
If you are updating from revision 24.052 to revision 30.051, follow the steps in
the section.
TIP Create a 30.051 firmware directory on your computer first, so you can unzip
the firmware files to this directory.
Before you update software for your redundant system, use one of these
methods to 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.
Install the Redundancy If needed, install the latest version of the RMCT.
Module Configuration Tool
IMPORTANT If you have RMCT version 7 or earlier, it does not support the 1756-RM2
modules. You need RMCT version 8 for revision 24.052_kit1 or later.
IMPORTANT You must uninstall any existing version of the Redundancy Module
Configuration Tool (RMCT) before you install the RMCT, version 8.4.1.0. If you
do not uninstall the previous version, you can have difficulty if you try to
uninstall version 8.4.1.0 later.
2. Double-click on setup.exe.
Install the Logix Designer This section describes how to install the Logix Designer that is compatible
with your redundancy firmware bundle.
Application
IMPORTANT If you update your programming software from version 20 to version 24, we
strongly recommend that you read Rockwell Automation Knowledgebase
Answer ID 565204 - RSLogix 5000 Software, Version 20.03, accessible at:
http://www.rockwellautomation.com/knowledgebase/.
A login is required to access the article.
IMPORTANT There are multiple methods available to update the programming software
version in your redundancy system. The specific tasks that are required vary
by system configuration and requirements.
This section describes one of the methods available.
Prepare the Controller To prepare the controller project and controllers for the update, complete these
steps.
Project for the Update
1. Start the Logix Designer application, and select your redundancy
project.
2. Go online with the primary controller.
3. To make sure that your off-line project has the latest updates, or in case
you do not have an off-line file, upload the project from the primary
controller.
4. Verify that the watchdog time is set to a value that corresponds with the
requirements of the redundancy system revision and your application.
Controller Properties
12. Specify the controller revision that you are upgrading to.
13. If you will install a new controller while upgrading the secondary chassis
firmware, specify the new controller catalog number.
TIP If you are unable to specify the new revision, you must change the
Electronic Keying parameter to Compatible Module. You must also select
the highest available firmware revision.
Update the Redundancy You can update redundancy firmware to another revision while your process
continues to run. This update is known as Redundancy System Update (RSU).
System Firmware
IMPORTANT Remember the following before using this section:
RSU is available when upgrading only from one redundancy version to
another.
You can update only from firmware revision 20.054 or later.
If you update from revision 20.054 to revision 30.051, you must first
update to revision 24.052 before you update to revision 30.051.
You must use this process if the following conditions exist:
You are upgrading from a redundancy system to revision
24.052_kit1 or later.
Your project does not require EtherNet/IP modules to use Electronic
Keying = Exact Match.
Consider these points before you begin upgrading your redundancy system to a
new revision:
IMPORTANT If your system has 1756-RM or 1756-RMXT modules, you must replace them
with 1756-RM2 or 1756-RM2XT modules. You cannot replace the modules
while the controller is in Run mode. See Replace a 1756-RM Module with a
1756-RM2 Module on page 49 for more information.
Complete the steps in this table to update your redundancy system from one
redundancy system revision to another redundancy revision while your process
continues to run.
Task Page
Prepare the Redundant Chassis for the Firmware Update 25
Update the Redundancy Module Firmware in the Primary Chassis 27
Update Redundancy Module Firmware and Other Module Firmware in the Secondary Chassis 29
Lock the System and Initiate a Switchover to Update 31
Update the New Secondary Chassis Firmware 33
Synchronize the Redundant Chassis 35
Complete these steps to prepare both the primary and secondary redundant
chassis for redundancy firmware updates.
1. Set the mode switch of the primary and secondary controllers to REM.
If the redundant controllers in both chassis of the redundant chassis pair
are not in Remote Program (REM) mode, the redundancy firmware
update cannot be completed.
Status in RMCT
IMPORTANT If your system has 1756-RM or 1756-RMXT modules, you must replace them
with 1756-RM2 or 1756-RM2XT modules. You cannot replace the modules
while the controller is in Run mode. See Replace a 1756-RM Module with a
1756-RM2 Module on page 49 for more information.
Make sure that the primary chassis is powered on. If you need to power on the
chassis, wait at least 45 seconds after powerup before you begin the update.
During this time, the redundancy module conducts internal operations to
prepare for an update.
3. On the Firmware Kit Location dialog, if the location where you store
firmware files is not in the Monitored folders list:
a. Click Add.
b. On the Browse for Folder dialog, select the location of your firmware
files.
c. Click OK.
4. On the ControlFlash dialog, select the redundancy module catalog
number as the target device.
5. Click Next
6. Browse to the module and select it.
Primary Chassis
Secondary Chassis
7. Click OK.
8. Select the firmware revision to update to and click Next.
9. Click Finish. The firmware begins to update. When the update is
complete, the Update status dialog box indicates completion
.
1. If you want to replace your module hardware, remove the module from
the secondary chassis and replace it with the new module.
IMPORTANT When replacing communications modules, make sure that the node
address (for ControlNet modules), rotary switches, and Port
Configuration (for Ethernet modules) match the existing modules.
If you replace EtherNet I/P or ControlNet communication modules as
part of this redundancy update, make sure you have read through
and are familiar with the Replacement Considerations on page 37.
Secondary Chassis
5. Click OK.
6. Select the firmware revision to update to and click Next.
7. Click Finish.
The firmware begins to update. When the update is complete, the
Update status dialog box indicates completion.
You are now ready to lock the system and initiate a locked switchover to update
the primary chassis. Continue with Lock the System and Initiate a Switchover
to Update.
Once you have downloaded the controller project, complete these steps to lock
your system and initiate a switchover.
3. Click Lock For Update, and then click Yes at the Redundancy
Configuration Tool dialog box.
The System Update Lock Attempts log indicates when the system lock is
complete.
5. Click Initiate Locked Switchover, and then click Yes at the Redundancy
Configuration Tool dialog box.
Once your locked switchover is complete, update the firmware revisions for
modules in the new secondary chassis.
IMPORTANT After the locked switchover, the new secondary controllers no longer contain
a user application and their configuration settings are reset to the factory-
default settings.
The new secondary controllers use the default settings and the components
in the secondary chassis are updated and the system is synchronized.
IMPORTANT Update the Gateway address of the primary chassis Ethernet module to
192.168.1.1, if you are upgrading from a system using revision 20.054_kit1,
20.055_kit1, 20.055_kit2, 20.055_kit3, 20.055_kit4, or 20.056_kit1 and
Electronic Keying is set to Exact Match, Compatible Module or Disable Keying
and you are either:
a. Updating 1756-EN2T/C (or earlier) modules with 1756-EN2T/C (or earlier)
modules, and the modules being replaced have rotary switches set to
2254.
b. Replacing 1756-EN2T/C (or earlier) modules with EN2T/D modules, and
the modules being replaced have rotary switches set to 2254.
To update the firmware of all modules in the new secondary chassis, complete
these steps.
1. If you are replacing and upgrading your module hardware, remove the
module from the secondary chassis and replace it with the new module.
2. Launch ControlFLASH software and click Next.
IMPORTANT When replacing communications modules, make sure that the node
address (for ControlNet modules), rotary switches, and Port
Configuration (for Ethernet modules) match the existing modules.
If you replace EtherNet I/P or ControlNet communication modules as
part of this redundancy update, make sure you have read through
and are familiar with the Replacement Considerations on page 37.
Secondary Chassis
5. Click OK.
6. Select the firmware revision to update to and click Next.
7. Click Finish.
The firmware begins to update. When the update is complete, the
Update status dialog box indicates completion.
Once you either replace or update the firmware for each of the modules in the
new secondary chassis, continue with Synchronize the Redundant Chassis on
page 35.
To synchronize the redundant chassis after firmware in both chassis have been
updated to the same revision, complete these steps.
5. In the new secondary, set the rotary switches back to the original
configuration.
6. Repeat this process for all Ethernet modules that need the rotary
switches set back to 2254.
7. From the Auto-Synchronization pull-down menu, choose the frequency
that suits your application.
9. Set the redundancy module date and time according to your preference.
10. Click OK.
11. Close the RMCT.
EDS Files
If you see modules that are displayed in RSLinx Classic with yellow question
marks, the EDS files for the modules are not registered. You can right-click on
the module and proceed with the Upload EDS files from device wizard to
upload the EDS file. If this option is not available or as an alternative, obtain
the EDS files for modules in your system from the Rockwell Automation
website at:
http://www.rockwellautomation.com/resources/eds/.
Replacement Considerations
Topic Page
Before You Begin 37
Replace a Module in the Secondary Chassis that has the Same Catalog Number and 38
Firmware Revision
Replace an EtherNet/IP Module with a New Series 39
Replace a 1756-CN2 Module with a New Series 44
Replace a 1756-RM Module with a 1756-RM2 Module 49
Before You Begin When replacing modules in ControlLogix redundancy systems, there are
considerations for these situations:
Replace a module in the secondary chassis
Replace an EtherNet/IP or ControlNet communication module
Replace a 1756-RM or 1756-RMXT module with a 1756-RM2 or
1756-RM2XT module
Replace a Module in the These steps are used when performing a direct communication module
replacement, for example, when replacing a communication module in the
Secondary Chassis that has the secondary chassis with a module that has the same:
Same Catalog Number and Catalog number
Firmware Revision Series
Firmware (after updating the firmware, if necessary)
When you replace communication modules, make sure that the node address
(for ControlNet modules), rotary switches, and Port Configuration (for
EtherNet/IP modules) match the existing modules.
Replace an EtherNet/IP Module This section describes how to replace EtherNet/IP communication modules in
a redundancy system without the need for a controller update.
with a New Series
You can replace the EtherNet/IP modules by using the following methods:
Synchronization and Switchover for EtherNet/IP Modules
Use this method if Electronic Keying is set to Exact Match. You must
configure the new modules to use Exact Match.
1. Make sure the existing module and replacement module use the same IP,
Network Mask, and Gateway addresses.
2. For the Redundancy Module Configuration Tool (RMCT):
With redundancy firmware revision 24.052, make sure the RMCT is
at version 8.3.1.0 or later.
With redundancy firmware revision 30.051, make sure the RMCT is
at version 8.4.1.0 or later.
3. Make sure that the redundancy module firmware is at the firmware
revision for the specified bundle for only 1756-RM2 and 1756-RM2XT
modules.
4. Go online with the primary controller.
5. For each module, verify that the Electronic Keying is set to Compatible
Module or Disable Keying.
6. In the RSLinx Classic software, start the RMCT for the redundancy
module in either chassis.
8. Click Apply.
9. On the Synchronization tab, click Disqualify Secondary.
11. Disconnect the Ethernet cables from the secondary Ethernet module.
12. Turn off power to the secondary chassis.
13. Remove the EtherNet/IP module from the secondary chassis.
14. Set the switches on the new EtherNet/IP module to 888, insert the
module in the secondary chassis, and apply power to the chassis.
a. After the reset is complete, turn power off to the secondary chassis,
remove the module from the secondary chassis.
b. Set the switches to the same settings as on the module that was
removed.
c. Reinsert the module into the secondary chassis, reattach the cable,
and apply power to the secondary chassis.
d. To support bridging across the backplane (or via the USB port),
configure the Port Configuration of the secondary module to match
the Port Configuration of the primary module.
15. If you have not already done so, update the firmware of the new
EtherNet/IP module.
a. Launch ControlFLASH, and click Next.
d. Click OK.
e. Select the firmware revision to update to and click Next.
f. Click Finish.
The firmware begins to update. When the update is complete, the
Update status dialog box indicates completion.
Replace a 1756-CN2 Module with This section describes how to replace ControlNet communication modules in
a redundancy system. You can replace the 1756-CN2/B modules with
a New Series 1756-CN2/C modules by using the following methods:
Synchronization and Switchover for the ControlNet Modules
IMPORTANT When you update 1756-CN2/B modules to 1756-CN2/C modules, you must do so in
pairs. If not, the system cannot synchronize after a switchover.
Replace 1756-CN2/B with 1756-CN2/C, and 1756-CN2RXT/B modules with
1756-CN2RXT/C modules.
1. Add the EDS files for the modules, if you have not already done so.
2. Make a note of the Node configuration of the ControlNet module.
In this example, the primary ControlNet Node is configured to be Node
11. The Node value of the secondary ControlNet module must be the
same value as the primary module.
7. In the RSLinx Classic software, start the RMCT for the redundancy
module in the primary chassis.
10. On the Synchronization tab, click Disqualify Secondary and then click
Yes.
11. Disconnect the coaxial cables from the secondary ControlNet module.
12. Remove the original ControlNet module from the secondary chassis.
13. Set the switches in the new module to 00 and insert the module into the
secondary chassis.
14. After the reset is complete in the new ControlNet module, remove the
module from the secondary chassis.
15. Set the switches in the new ControlNet module to the correct Node
value and reinsert the module into the secondary chassis.
16. Reconnect the coaxial cable to the new secondary ControlNet module.
17. Update the firmware of the ControlNet module in the secondary
chassis.
a. If necessary, complete the following steps to update module firmware.
b. Launch ControlFLASH, and click Next.
c. Select the ControlNet module catalog number and click Next.
e. Click OK.
f. Select the firmware revision to update to and click Next.
g. Click Finish.
22. Remove the ControlNet modules from the new secondary chassis.
23. Make sure to match the node address of replacing the ControlNet
module with existing module.
24. Insert the ControlNet module into the new secondary chassis,
reconnect the module to the network, and turn on power to the chassis.
25. If you have not already done so, update the firmware of the ControlNet
module in the primary chassis.
Replace a 1756-RM Module with You can replace 1756-RM modules with 1756-RM2 modules without
initiating a switchover.
a 1756-RM2 Module
1. Install the compatible version of the RMCT software.
You must shut down RSLinx Classic software to install the software, and
then restart RSLinx Classic software after the installation is complete.
Notes:
The Studio 5000 Logix Designer application has requirements for data type
use. The requirements differ based on the Logix Designer application version
that you use.
Additional pad bytes are added to the data structure to account for the
misalignment. The pad bytes can cause an increase in the size of the UDT.
The possible effects of data structure changes, and subsequent actions that you
can take as a result, are described in the rest of this section.
IMPORTANT You must also act when your application includes Logix5000 controllers,
version 26 or earlier, that communicate with Logix5000 controllers, version
30.051 or later.
You can adapt your project to accommodate larger structure sizes, if necessary.
You can see the following effects due to the larger size:
Message instruction data lengths can require changes to
complete successfully.
Copy lengths of data structures can change.
Produce/Consume connections to other Logix controller types can have
data type mismatches and require changes to complete successfully.
We recommend that you copy and paste the UDT definition from one project
to the other to cover both of these cases. Use the Data Type editor to check the
Data Type Size in both projects:
If the data type size is different between the two projects, modify the UDT to
produce the same internal data structure.
The following sample UDT illustrates how the 8-byte allocation rule and the
8-byte alignment rule cause a UDT to have another size.
Table 1 illustrates how this data structure maps in a Logix Designer project,
version 24.052 or earlier. MyLint is split across two 64-bit words, and the total
size is only 32 bytes.
Table 1 - Data Structure for Logix Designer Projects, Version 26 or Earlier
Word Elements Byte Mapping Table 64 Bit Boundaries
0 LimitA and LimitB Pad Pad Pad Hidden 0
SINT
1 Profile (Real [3]) Map Map Map Map
2 Map Map Map Map 1
3 Map Map Map Map
4 Interlock (Int) Pad Pad Map Map 2
5 MyLint (LINT) Map Map Map Map
6 Map Map Map Map 3
7 Speed (REAL) Map Map Map Map
Table 2 illustrates the hidden padding bytes that the Logix Designer
application automatically adds to achieve the 8-byte alignment and allocation
rules for a Logix Designer project, version 30.051 or later.
Table 2 - Hidden Padding Added for Logix Designer Projects, Version 27 or Later
Word Elements Byte Mapping Table 64 Bit Boundaries
0 LimitA and LimitB Pad Pad Pad Hidden 0
SINT
1 Profile (Real [3]) Map Map Map Map
2 Map Map Map Map 1
3 Map Map Map Map
4 Interlock (Int) Pad Pad Map Map 2
5 Padding for 8-byte Pad Pad Pad Pad
alignment
6 MyLint (LINT) Map Map Map Map 3
7 Map Map Map Map
8 Speed (REAL) Map Map Map Map 4
9 Padding for 8-byte Pad Pad Pad Pad
allocation
To create a UDT that is the same size in all types of projects, insert additional
data elements so that hidden padding bytes are not necessary.
Table 3 illustrates how this data structure maps in all types of Logix5000
controller projects:
Table 3 - Memory Map in All Project Types
Word Elements Byte Mapping Table 64 Bit Boundaries
0 Bools and 2 Pad Pad Pad Hidden 0
SINT
1 Profile (Real [3]) Map Map Map Map
2 Map Map Map Map 1
3 Map Map Map Map
4 Interlock (Int) Pad Pad Map Map 2
5 UnusedDint1 Map Map Map Map
6 MyLint (LINT) Map Map Map Map 3
7 Map Map Map Map
8 Speed (REAL) Map Map Map Map 4
9 UnusedDint2 Map Map Map Map
The concept is the same for nested UDTs. If the lower-level UDT is an 8-byte
type (that is, it contains at least one 8-byte data element), you must align it to
start at an 8-byte boundary.
When the tasks are completed, the UDTs are the same size in the
Logix Designer project, version 24.052 or earlier and the Logix Designer
project, version 30.051 or later.
A useful technique when creating UDTs is to start with the largest data types
first, and work down through 8-byte, 4-byte, 2-byte, 1-byte, and finally single-
bit data types. The resultant mapping is 64-bit-aligned in all controller types,
so no manual padding is required.
Notes:
Technical Support Center Knowledgebase Articles, How-to Videos, FAQs, Chat, User https://rockwellautomation.custhelp.com/
Forums, and Product Notification Updates.
Local Technical Support Phone Numbers Locate the phone number for your country. http://www.rockwellautomation.com/global/support/get-support-now.page
Find the Direct Dial Code for your product. Use the code to
Direct Dial Codes route your call directly to a technical support engineer. http://www.rockwellautomation.com/global/support/direct-dial.page
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
How Are We Doing? form at http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf.
Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.
Allen-Bradley, ControlFLASH, ControlLogix, Data Highway Plus, FactoryTalk, Integrated Architecture, Logix5000, Rockwell Automation, Rockwell Software, RSLinx, RSLogix 5000, RSNetWorx, and Studio 5000 Logix Designer 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 erenky, stanbul, Tel: +90 (216) 5698400