Home › Technical articles

Đọc bằng tiếng Việt

ControlLogix and CompactLogix firmware updates with ControlFLASH Plus: revisions, order, interruptions

TDL Industrial Automation · Last updated:

From the ControlFLASH Plus 6.02 help and manuals 1756-UM543, 1756-UM001Q and 1756-UM015O: ControlFLASH Plus, ControlFLASH and AutoFlash, the PCDC and DMKs, the major revision rule, Remote Program mode, SD card, CIP Security, flash order, interrupted updates and running redundant pairs.

Firmware on a ControlLogix or CompactLogix controller is changed with ControlFLASH Plus, with AutoFlash from inside Studio 5000 Logix Designer, or, for devices that do not support CIP, with the older ControlFLASH. The revision comes from Rockwell Automation's Product Compatibility and Download Center (PCDC) and must share its major revision with the Logix Designer version that opens the project. This article follows the ControlFLASH Plus 6.02 help and Rockwell's controller and redundancy manuals. Which software version goes with which controller: RSLogix 5000 and Studio 5000 Logix Designer versions.

Logix firmware update: the steps in Rockwell's documentsFour steps from top to bottom: choose the revision on the PCDC, prepare the controller and the computer, flash with ControlFLASH Plus, watch the Status column and keep the flash report. At the bottom, the order for a running redundant ControlLogix pair: secondary chassis, project download to the secondary, locked switchover, then update the new secondary and synchronise. Based on the ControlFLASH Plus 6.02 help, 1756-UM543, 1756-UM001Q and 1756-UM015O.Logix firmware update: the steps in Rockwell's documents1 · Choose the revisionon the PCDCmajor revision equals the Logix Designer versionPCDC Compare and release notesDMK in a monitored folder2 · Preparecontroller and computerRemote Program or Program modemajor recoverable faults cleared, no safety lockSD card load option; CIP Security warningcomputer powered, no sleep3 · FlashControlFLASH Plusselect devices and the Flash To revisionopen the Compatibility dialog when flaggedorder from topology: parents before children4 · Watch and recordStatus columnTransmitting update, Polling for power-up, Flash finishedFlash interrupted: View, then Resolveflash report saved as a CSV fileRunning redundant pair (1756-UM015O, chapter 15)Secondary chassisupdate theredundancy module,then the othermodulesDownloadthe converted projectto the secondarycontrollerLocked switchoverlock the system, thenswitchNew secondaryupdate, thensynchroniseBased on Rockwell Automation: ControlFLASH Plus 6.02 help, 1756-UM543 online edition, 1756-UM001Q and1756-UM015O (read 15 November 2026). Figure: drawn by TDL.
Figure 1: Logix firmware update: the steps in Rockwell's documents. On a phone, swipe sideways to see the whole figure.

1. ControlFLASH Plus, ControlFLASH and AutoFlash

The ControlFLASH Plus help calls the tool the next generation of ControlFLASH. It updates controllers, I/O, drives, servo drives and overloads, several in one operation, and downloads firmware from the PCDC. It updates only devices that support the Common Industrial Protocol (CIP); for other devices the help points to the legacy ControlFLASH. FactoryTalk Linx 6.60.00 and FactoryTalk Services Platform 6.60.00 must be installed first, with the communication drivers configured and tested in FactoryTalk Linx. From ControlFLASH Plus 2.00.00 an optional package installs both.

Both tools can run on one computer and share one policy, ControlFlash, in FactoryTalk Administration Console; its Firmware: Update action sets who may update devices. Uninstalling ControlFLASH cuts ControlFLASH Plus off from the older MSI-based firmware kits.

AutoFlash is the route from Logix Designer: Who Active, select the controller, Update Firmware, choose the revision. For ControlLogix 5570 and 5560, 1756-UM001Q names ControlFLASH, installed with the Studio 5000 environment, and AutoFlash (p. 48). 1756-UM543 (ControlLogix 5580) describes ControlFLASH Plus and AutoFlash; 5069-UM001N (CompactLogix 5380) lists ControlFLASH Plus (p. 19).

2. Choosing the revision: PCDC, kits and the major revision

Controller firmware and Logix Designer must have the same major revision; 1756-UM543 gives the example of firmware 38.xxx with Logix Designer version 38. On the PCDC, firmware sits in the Download section and product compatibility in Compare; builds listed as compatible were tested together, others were not. The firmware installed with Logix Designer is the initial release of that version, and later revisions with fixes may follow. A new controller ships with firmware 1.xxx and must be updated before it is used in a project.

Firmware comes as a Device Management Kit (DMK): one file with everything needed to update one or more catalogue numbers, the digital signature files and, where included, the release notes. ControlFLASH Plus looks for kits in the monitored folders set under Settings, Firmware Locations; the help advises against the legacy ControlFLASH installation folder, where files can in rare cases be deleted. A kit whose publisher is not yet trusted brings up a prompt, and the update goes on only if the publisher is trusted.

The help says to specify the exact revision; otherwise the result is unpredictable. Connected to the PCDC, the Manage Firmware tab shows each device's lifecycle status and each revision's release notes. A firmware series that does not match the device series is flagged in the Status column.

3. Before flashing: mode, faults, SD card, security

The ControlLogix manuals require the controller to be in Remote Program or Program mode with all major recoverable faults cleared (1756-UM543; 1756-UM001Q p. 49). Reading those faults: Logix major fault codes. ControlFLASH Plus warns that a device in Remote Run or Hard Run is not in the correct mode; the mode is changed in Logix Designer or on the device, then the list is refreshed. A safety-locked controller cannot be updated until the safety lock is released in Logix Designer.

The help adds: update only when the process can stop and the devices can be taken out of service, check connections and bandwidth, and keep the computer powered and out of sleep mode, because sleep can interrupt the update.

Two more things can undo or disturb an update:

  • SD card. On a 5570 with a locked card set to load On Power Up, the firmware is not updated and the stored firmware and project load instead (1756-UM001Q p. 50). On a 5580 the update switches the card's load option to User Initiated where it can; on a locked card it cannot, and the card's firmware can overwrite the new firmware (1756-UM543). PDF edition: 1756-UM543.
  • CIP Security. On a CIP-secured device, ControlFLASH Plus warns that communications may be lost after the update, because flashing can disturb security information; it gives the same warning while a CIP Security configuration is in progress. See CIP Security on ControlLogix 5580 and CompactLogix 5380.

4. The update and the order of devices

On the Flash Devices tab: set the browse path, tick the devices, pick a revision in the Flash To column, read the warnings, and open the Compatibility dialog box for any device marked Not compatible or Maybe compatible. After Next, revisions not yet on the computer are downloaded from the PCDC once the licence agreement is accepted; firmware that is not in a DMK is installed by hand, followed by Refresh Firmware. Flash starts the update; Retry repeats the devices that failed or were cancelled. A flash report is saved as a CSV file.

The Status column moves through Pending, Transmitting update, Polling for power-up and Flash finished, or ends in Failed, Flash interrupted or Canceled. Cancel stops only pending updates; running ones finish.

ControlFLASH Plus sets the order itself, from the topology and parent-child relationships. Up to version 2.00.00 it flashes up to 20 devices at once, but parents before children, peers on a linear bus (Ethernet linear or DLR, SERCOS) one after another, and a device with several active ports, such as a 1756-EN2TR, on its own. From version 3.00.00, enhanced concurrent flashing flashes parents with children, and peers on a linear bus, together where the tool can hold the device in reset; a 1756-DNB or PowerFlex drives still go one by one.

For GuardLogix 5580, selecting the safety controller, for example a 1756-L84ES, also selects and locks its 1756-L8SP safety partner at the same revision, and 1756-UM543 says updating the primary updates the partner. The same manual requires the safety signature to be removed and regenerated, every release note between the two revisions to be reviewed, and the application checked, because the safety logic compiler can change.

5. When an update is interrupted

ControlFLASH Plus shows the number of interrupted flashes at the top of the Flash Devices tab: click View, then Resolve in the device's Status column, and follow the Flash interrupted dialog box. 1756-UM001Q says not to cycle power or interrupt the update before it completes; an interrupted ControlLogix 5570 or 5560 update leaves the controller on boot firmware 1.xxx (p. 54, 58). That is the firmware a new controller ships with, which 1756-UM543 says must be updated before the controller is used in a project. If a 1756-L7x reports a Script File Error after the revision is chosen, the firmware files may be damaged, and the manual says to download that revision again (p. 53).

6. Redundant pairs: one bundle, secondary chassis first

For a redundant ControlLogix pair, 1756-UM015O asks for compatible versions of Logix Designer, the communication software and ControlFLASH Plus, the firmware bundle's release notes checked against the hardware, and running communication software closed before installing (p. 39). The bundle comes from the PCDC, and its installer places a DMK in the ControlFLASH Plus download folder (p. 40). Which bundle, and how partner modules must match: ControlLogix redundancy before FAT.

The manual's chapter on online firmware updates (pp. 187–195) runs in this order: verify the version of the Redundancy Module Configuration Tool (RMCT), prepare the project, update the redundancy module in the secondary chassis and then in the primary, update the other modules in the secondary, download the project to the secondary controller, lock the system and initiate a locked switchover, update the new secondary, and synchronise. The Logix Designer 37.00 help adds that the secondary is disqualified first, the project is uploaded from the primary, converted and downloaded to the secondary, and redundancy is off during the update, so the secondary cannot take over if the primary fails. Firmware cannot go to a locked primary or through a synchronised or locked secondary.

The RMCT 10.01 help sets Auto-Synchronization to Never and allows Lock For Update and Initiate Locked Switchover only from the RMCT opened on the primary redundancy module. If a locked switchover fails, both redundancy modules show DISQ and control is lost.

What we check first

This is TDL's practice, not a Rockwell Automation requirement.

  • We back up the program and record the current revision of every module in the chassis first.
  • We run PCDC Compare for each catalogue number against the Logix Designer version the plant uses, and read every release note between the old and the new revision.
  • We keep the old DMK on the laptop, so the way back is ready.
  • We check the SD card: load option, lock, and which firmware is stored on it.
  • We ask whether CIP Security is deployed and who holds the policy.
  • We flash on mains power with sleep off, inside a shutdown window agreed with the plant; on a redundant pair, the locked switchover is agreed with operations.
  • We file the flash report with the backup.

Firmware work at TDL

TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. At Samsung's SEHC complex our scope includes ControlLogix firmware migration and redundancy reconfiguration, and the preventive maintenance of the PLC stations includes firmware and redundancy checks. The same work is a service package, controller firmware upgrade and Studio 5000 compatibility check, ending with the final revision table at handover. Related: Rockwell PLC security, FactoryTalk Linx cannot see the controller, Rockwell system upgrades.

Frequently asked questions

Which software updates ControlLogix and CompactLogix firmware?

ControlFLASH Plus, or AutoFlash from Logix Designer. ControlFLASH Plus updates only CIP devices; the legacy ControlFLASH handles the rest. ControlFLASH Plus needs FactoryTalk Linx 6.60.00 and FactoryTalk Services Platform 6.60.00.

Why does ControlFLASH Plus say the device is not in the correct mode?

The controller is in Remote Run or Hard Run. The manuals require Remote Program or Program mode with all major recoverable faults cleared; change the mode in Logix Designer or on the controller, then refresh.

What happens if a ControlLogix firmware update is interrupted?

ControlFLASH Plus marks it Flash interrupted and offers Resolve in the Status column. For ControlLogix 5570 and 5560, 1756-UM001Q says the controller reverts to boot firmware 1.xxx, which must be updated before the controller is used in a project.

Can firmware be updated on a running redundant ControlLogix system?

Yes, the secondary chassis first: update it, download the converted project, lock the system and initiate a locked switchover, then update the new secondary and synchronise. Redundancy is off during the update, and a failed locked switchover leaves both redundancy modules in DISQ with control lost.

Where do I download ControlLogix firmware?

From the Product Compatibility and Download Center, as Device Management Kits that ControlFLASH Plus can download directly. Logix Designer also installs firmware, but that is the initial release of its version.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Rockwell Automation (Allen-Bradley) Rockwell Automation upgrades