RSLogix 5000 vs Studio 5000: which version works with your controller

Every few weeks somebody sends me the same photo. A laptop with Studio 5000 v35 on it, a ControlLogix nobody has touched in years, and the software refusing to go online with it. Nothing is broken. The controller's firmware picks the software version, and RSLogix 5000 is just what that software was called up through v20.

Here's how I match a controller to the right RSLogix 5000 or Studio 5000 version and where the old versions come from. Plus the shortcut people take instead, which wipes the program out of a running controller.

RSLogix 5000 and Studio 5000 are one program, renamed at v21

Everything up to and including v20 is RSLogix 5000. From v21 on, the same programming software is Studio 5000 Logix Designer, and it launches from inside the Studio 5000 environment. The last RSLogix 5000 build is 20.06.00, released in October 2022. Logix Designer is up to 38.03.00 as of October 2026.

Rockwell mixes the two names up itself. In the download center and in FactoryTalk Activation Manager they get used interchangeably, and RSLogix 5000 20.06.00 can show up there labeled Studio 5000 20.06.00. Same software, so don't go hunting for a second file.

The software's major version has to equal the controller firmware's major version. A controller on firmware 20.013 needs v20 software, and newer versions don't cover older firmware, so Logix Designer v30 won't open a v20 project without converting it and won't go online with a controller on 20.xxx firmware. Projects convert to a higher major version, never a lower one.

Find your controller's row. Left of the red line is RSLogix 5000 territory, right of it Studio 5000 Logix Designer. The two bars that cross it can run either, depending on firmware.

Which RSLogix 5000 version your controller can run

Controller family	Catalog numbers	First version	Last version
ControlLogix 5560	1756-L61, L62, L63, L63XT, L64, L65	v10 to v17, by model and series	v20
CompactLogix L4	1768-L43, L45	v15 or v16, by model and series	v20
CompactLogix L2 and L3, older style	1769-L23x, L31, L32C, L32E, L35E	v12 to v17, by model	v20
ControlLogix 5570	1756-L71, L72, L73, L73XT, L74, L75	v18 or v19 on Series A by model, v20 on Series B and on any L71	Current Logix Designer
CompactLogix 5370	1769-L16ER, L18ER, L18ERM, L24ER, L27ERM, L30ER, L30ERM, L33ER, L33ERM, L36ERM	v20	Current Logix Designer
ControlLogix 5580	1756-L81E, L82E, L83E, L84E, L85E	v28 or v29 on Series B, v33 on NSE and EP models	Current Logix Designer

 

The first three rows stop at v20, and so does the GuardLogix 5560. Those controllers will never run Studio 5000. The 5570 and most 5370 models sit on both sides of the rename: same hardware, either firmware v20 or older and RSLogix 5000, or something like v35 and Logix Designer, depending on what somebody flashed into it last. And the 5580 skipped the old name entirely. Logix Designer only, from day one.

Series B moves the bottom of the range

This is the one that catches people buying a replacement. A 1756-L73 Series A runs v19 firmware fine, but a Series B won't take anything older than v20. So a dead Series A that ran a v19 project can't be swapped for a Series B without converting the project to v20 first, which means a fresh download on that machine and all the testing that goes with it.

Old L6x controllers have two catches of their own. A controller still on firmware 11 or earlier can't jump straight to v20; it has to stop at 12 or 13 on the way. And v20 can need more memory than earlier revisions, so a program that barely fit an L61 on firmware 11 or earlier might not fit on v20 at all.

Read the firmware revision first

On an L7x this takes seconds. The four-character display scrolls the catalog number and series, then Rev and the firmware revision. If it scrolls Firmware Installation Required instead, the controller is sitting on boot firmware 1.xxx and needs real firmware before it does anything.

An L6x has no display, just six status lights. Browse to it in RSLinx Classic, right-click it in RSWho, open Device Properties and read Revision.

The number before the dot is the version you install. One catch with older L7x units: on firmware 18 or 19, or still on the 1.008 boot image, the USB port won't connect from a 64-bit Windows 7 PC. Go in over Ethernet instead.

Two minor versions that break the rule

Minor versions usually don't matter, but these two will catch you.

Version	What breaks	Way around
20.03	Breaks compatibility with 20.01. A 20.03 file won't open in 20.01, and 20.03 asks to convert 20.01 and 20.04+ files to 20.03	Use 20.04, 20.05 or 20.06. They open both 20.01 and 20.03 files
21.03	Projects converted to 21.03 or later won't open in 21.00. Neither version can go online to a controller the other one downloaded, and only one of the two can be installed on a PC	Keep 21.00 on its own PC or VM, or upload with 21.03, convert and download again

 

Need a 20.03 file back on a 20.01 machine? There's a manual way. Open it in 20.04, save it as L5K or L5X, and in a text editor change CompatibilityMode from V20.03 to V20.01, then import it back into 20.04, save and download. If there's ControlNet on that controller, reschedule the network after the download.

Can you run several RSLogix 5000 versions on one PC?

You can, and on a maintenance laptop you pretty much have to. Major versions from v10 up install side by side, plus one version older than v10. The limit is one minor per major: 20.06 or 20.04, not both.

There's no master installer, and the multi-version packages only cover some versions, so in practice each one goes on by itself, oldest first. That order isn't superstition. Version 20.05 brings .NET Framework 4.6 with it, and once that's on the PC, installing an earlier version afterwards can fail. With v21 came a new EDS subsystem and an RSLinx Classic upgrade, which can leave older RSNetWorx and the DeviceNet Tag Generator inoperable. Good to know before v21 goes on the one laptop that still configures your DeviceNet.

After that it mostly runs itself. Double-click an .ACD and the matching version opens. If that version isn't installed, you're asked to convert the project or install it. Anything older than v10 won't switch automatically and has its own icon.

Windows narrows it down

No version of RSLogix 5000 is supported on Windows 11. The Windows 11 list starts at Logix Designer 33.02.01, Pro or Enterprise only, and Windows 11 Home isn't supported for any version. Version 20.06 was tested on 64-bit Windows 10 Pro version 1703 and on Windows Server 2012 R2 and 2016. Further back it only gets narrower. Versions before 19 aren't supported on Windows 7, and v12 or earlier won't even install on 64-bit Windows 7.

That's why the oldest versions on my laptop live in a virtual machine. It's a supported setup under VMware, as long as the guest Windows is one that version supports. What breaks in a VM is usually the license binding, and I went through that in the virtual machine article.

Where old RSLogix 5000 versions come from

Rockwell's Product Compatibility and Download Center, with a serial number. Pick Download by Serial Number, validate the serial, then open the Version dropdown. The page lands on the newest release, so it looks like the old ones are gone. They aren't, the list still runs all the way down to 6.20.

The serial is only half of it. A current license activates the version that was current when it was bought, plus everything back to 20.05. Not 20.04, and not the v16 your L63 has been running since commissioning. Anything before 20.05 needs a Legacy license, which covers versions before and after 20.05 and gets ordered instead of a current one. Subscription portal licenses follow the same rule, so below 20.05 it has to be the Legacy one.

Check the edition too. Lite and Mini cover CompactLogix and Compact GuardLogix only. A ControlLogix needs Standard or higher, or the Service edition if all you do is upload, download and look. One serial number activates both RSLogix 5000 and Studio 5000, and each version you install doesn't need its own activation.

Upload first, flash last

The shortcut goes like this. Laptop has v32, the line runs an L7x on v20, and instead of installing v20, somebody flashes the controller to v32 so it matches the laptop. A firmware update erases every program and all data in the controller. If the running logic only existed in that controller, it's gone. AutoFlash makes this easy to do by accident, because it can start the firmware update right from a download.

I'd rather install one more version than flash one more controller. The order I stick to:

1.    Install the software version that matches the firmware major.

2.    Go online, upload, and save the .ACD somewhere other than that laptop.

3.    If newer firmware is really needed, convert the project up first: Controller Properties, Change Controller, higher revision.

4.    On an L7x, check the SD card. If it's locked and the stored project is set to Load Image On Power Up, the update won't take, and the old firmware and project load right back.

5.    Key in Program, major faults cleared, then flash. Don't touch power until it finishes. An interrupted update leaves the controller on boot firmware 1.xxx.

6.    Download the converted project and test it before the machine runs.

 

Match the software, upload, and only then think about firmware. Flashing goes last because it erases the program.

About step 2. A controller on v20 or earlier doesn't hold rung comments or tag descriptions, so an upload brings back the logic and the tags without them. Storing documentation in the controller came with v21, as an option, on L7x and 5370 controllers. On a v20 machine the comments live in the offline .ACD file, not in the controller. Find that file before anybody flashes anything.

Taking an old project all the way to v38? That release no longer installs add-on profiles for many discontinued devices. Logix Designer 37.01 or the individual profile installers bring them back.

FAQ

Is RSLogix 5000 free?

No. Every edition is a paid license, and the download only unlocks with a valid serial number. A current license reaches back to 20.05, so anything older needs a Legacy license.

Is RSLogix 5000 obsolete?

As a name, since v21. As software, no. It's the only thing that programs a ControlLogix 5560, a 1768 CompactLogix or an older 1769-L3x, plus any L7x or 5370 on firmware v20 or older. Version 20.06.00 is the last build, and it's still downloadable if you have a valid serial. Just don't plan on running it under Windows 11.

How much does Studio 5000 cost?

There's no single number. Price depends on the edition, Mini through Professional, and on perpetual versus subscription. A perpetual license includes the first year of support. After that you need support coverage to get new versions. If you need anything before 20.05, ask for the Legacy license by name, since it replaces the current one on the order.

What's the difference between RSLogix 500 and RSLogix 5000?

Different controllers. RSLogix 500 programs SLC 500 and MicroLogix with data-table addresses like N7:0. RSLogix 5000 programs the Logix 5000 family, ControlLogix, CompactLogix and GuardLogix, with tags. Neither opens the other's project files directly, and moving SLC code into Logix is a conversion job. Editions and the free tools on the 500 side are in the RSLogix 500 software article.

Before you order a replacement controller

If the controller is the part that's gone, match it to the project before it ships. We keep the 1756-L73, a ControlLogix 5570 that runs RSLogix 5000 or current Logix Designer depending on its firmware, the 1756-L71S GuardLogix 5570, and the 1756-L83E for anyone moving up to a 5580 and Studio 5000 for good. Send us the catalog number off the old controller, its series and the firmware your project runs, and we'll tell you what on the shelf fits. Two-year warranty on all of it.