RSLogix 500 software: what is actually free, and which edition talks to your processor

Every few months I get the same call. Somebody picked up an SLC 5/03 off the surplus market, downloaded the free Rockwell programming package, wired up a cable, and got told the processor is not supported. Nothing wrong with the cable. Driver is fine, controller is fine. They installed a product that was never going to talk to that processor, and nothing on the download page makes that obvious until you are already standing in front of the panel. So here is the whole picture on RSLogix 500 software: which pieces are genuinely free, what the paid editions cover, roughly what they cost, and where the activation will quietly eat your afternoon.

The moment this article is about: the hardware is fine, the cable is fine, and the software still says no.

What you can download for free, and exactly where it stops

The free part is real and it comes straight from Rockwell. Three pieces: RSLogix Micro Starter Lite, RSLogix Emulate 500, and RSLinx Classic Lite. No trial clock ticking on any of them. You do need a Rockwell Automation account to pull them from the Product Compatibility and Download Center. There is also an extra unlock request step on the download now that was not there a few years ago, though it looks automated and clears right away.

Then the part that catches people out. Micro Starter Lite programs the MicroLogix 1000 and 1100. That is the list. Point it at a 1747-L532 and it will tell you the processor is not supported, because it genuinely is not. No 5/01, no 5/02, no 5/03, no 5/04, no 5/05. Free RSLogix 500 software covering the SLC family does not exist, and every hour spent hunting for it is an hour not spent getting a quote.

RSLinx Classic Lite has an edge worth knowing before you plan around it. It ships with RSLogix 500 and RSLogix Micro, and it carries the communication drivers you need to go online with a processor. What it will not do is DDE or OPC. Those need full RSLinx Classic, which is a separate paid product. Rockwell puts that in writing in the RSLogix 500 Getting Results Guide, publication LG500-GR002J-EN-E.

One caveat I would rather state than skip, because it changes how you plan the job. Not everyone lands on a free download. Depending on the account and the region, people do get steered toward a paid license instead. The old habit of grabbing a short trial of the full package has also tightened up: the installer wants a serial number and a product key before it will go anywhere. Budget for the paid path and treat the free download as the good outcome, not the plan.

The MicroLogix 1100 is one of the two controllers the free Micro Starter Lite download will actually talk to.

The editions, and the one line that decides your day

Rockwell splits RSLogix 500 software two ways and the naming helps nobody. Chapter 9 of LG500-GR002J-EN-E puts it plainly. RSLogix 500 comes in a Standard edition with basic ladder editing and a Professional edition that adds the developer functions. Over on the Micro side the two tiers are called Starter and Developer. Two product families, two tiers each, and the cheap tier of the wrong family is the one people install by accident.

The edition names and the two-tier split come from the Getting Results Guide. Rockwell documents those tiers but not the model coverage of the free Micro Starter Lite flavor, so check the download page for the version you are pulling. The SLC exclusion is not in question.

That VBA split is worth reading twice, because it is not what most people assume. You can run VBA code in RSLogix 500 Standard and in RSLogix Micro Starter. Creating or editing it needs Professional or Micro Developer. So inheriting a project with VBA in it does not force you up a tier. Touching that code does. The object model behind it is documented in publication LOGIX-RM001B-EN-P, the RSLogix Automation Interface Reference Manual.

Two other differences matter on legacy work. SLC libraries, the saved chunks of ladder you move between projects, are RSLogix 500 only and not part of RSLogix Micro at all. And both packages export a project to ACD or L5K format for Studio 5000 Logix Designer. That second one is easy to overlook. It is also why I would not write a software purchase off as sunk cost on a line heading for CompactLogix eventually: the export is step one of that migration, and it lives inside the package you already paid for.

An SLC 5/03 CPU. This is the processor the free download refuses, and the reason a paid RSLogix 500 software license ends up on the purchase order.

What RSLogix 500 software actually costs

Rockwell does not publish a number. Their support article on the package, document IN4194, dated September 16 2025, closes on exactly one line about money: contact your local Allen-Bradley or Rockwell distributor for pricing and availability. Every route to a price runs through a distributor quote. That is also why searching for the price online turns up so much noise and so little use.

The figures that come back are not small. Standard, catalog number 9324-RL0300ENE, has been quoted in the neighborhood of $3,600. Professional roughly doubles that. Take both as ballpark and get your own quote: these move, they vary by region, and whatever agreement your plant already holds with Rockwell can change them.

Put that next to the hardware and the shape of the problem is obvious. A used SLC 5/03 processor is a few hundred dollars. The software that talks to it is several thousand. That is backwards from how most equipment works. It is also the best argument I know for spending twenty minutes finding out whether the plant already owns a license before anyone raises a purchase order. Retired programming laptops sit forgotten in cabinets for years, and I have turned up more than one that way.

What else has to be on the machine before any of it runs

RSLogix 500 software is not one installer, it is a stack. The Getting Results Guide lists the pieces: RSLinx Classic Lite or full RSLinx, FactoryTalk Services Platform, and FactoryTalk Activation Manager. For RSLogix 500 specifically, add the Security Server Client and FactoryTalk Security if you intend to restrict features by user.

Rockwell's own install example explains why a legacy package eats two and a half gigabytes.

 

The programming package itself is under five percent of that. Everything else is plumbing.

One checkbox in the installer deserves a pause. Tick Enable FactoryTalk Security during setup, then decide later you do not want it, and the documented way back out is to uninstall RSLogix 500 and install it again. Not a settings change. A reinstall. Leave it clear unless you have a FactoryTalk Directory and an actual reason to use it.

You also need administrator privileges, stated in the first paragraph of the installation chapter. The number of failed installs that trace back to somebody running setup as a plain domain user is higher than it ought to be.

On the hardware side, Rockwell's list for getting a program off an SLC or MicroLogix is short. A version of RSLogix 500 software, a version of RSLinx, a communications port, and a communications cable suited to the model of processor. That last item is where surplus buyers stall, because it is not one cable. DH-485 on a 5/03 or 5/04 wants a 1747-UIC or equivalent converter. On a MicroLogix with the 8-pin mini DIN port you are looking for a 1761-CBL-PM02 instead. Buy a 5/05 and Ethernet sidesteps the question entirely, which is worth a thought when you are choosing which processor to source.

A 1747-UIC. Rockwell lists the cable as a requirement for pulling a program, and on a DH-485 processor this is usually the piece nobody has.

System requirements, and the Windows question everybody asks

The published minimum for RSLogix 500 software has not moved in years, and it shows.

 

Windows XP is not on that list. Worth saying out loud, because plenty of advice still treats this as an XP-era product you should keep an XP box around for. Old versions did run on XP. By the September 2018 revision of the guide, Rockwell had dropped it.

Windows 11 is not on the list either. I am not going to tell you it works or that it does not, because the guide predates it by three years. Rockwell points at its own compatibility site for current platform support, and on a question like this that is the only answer still correct next year. If you are specifying a programming laptop today and the choice is yours, Windows 10 is the boring option that matches what the documentation for RSLogix 500 software actually covers.

Activation is where the day actually goes

Installing is the easy half. Activation is where I have watched people lose whole days. On legacy and surplus equipment you can hit three different generations of it, depending on how old the license is.

Start with the old one, because it still turns up. Pre-FactoryTalk versions used EVRSI activation on a floppy master disk. Put the disk in, open it, and it looks empty. The activation file is a hidden system file, so Windows has to be set to show hidden operating system files before evrsi.sys will appear at all. Moving the license to the hard drive is done with the EVMove utility, and there is a flash-drive-capable variant, EVMoveCF.exe, for machines with no floppy drive. Moved, not copied. If you get a copy protection error at startup and then a complaint that the activation file is corrupt with an invalid serial number, one thing to check is a pair of leftover hidden files, 386SWAP.PAR and evrsi.sys, sitting where the license wants to land.

Current versions use FactoryTalk Activation Manager. When the install finishes you get an Activation page with two options: activate now, or skip activation and do it later with some features unavailable until you do. Activating asks for a serial number, a product key, and an earliest version selection, then whether you are activating locally or with a dongle. It restarts the computer afterward.

That earliest version box is not decoration. Set it to the oldest release of RSLogix 500 software you expect to open, not the version sitting in front of you. On legacy work somebody will eventually hand you a project saved in something much older than what you just installed.

Here is the one that costs the most time. Moving a license from an old programming laptop to a new one: rehost the activation on the old machine first, then get the new activation on the new machine. Do it in the other order and you get told the license is already active while the download activation button sits there grayed out. Now you are on the phone with Rockwell trying to unpick it. The guide is blunt about the reason. Activation files cannot be copied to another computer. They move, or they do not go.

Dongle activation buys some slack. The license lives on the USB key, one machine at a time, with a grace period of roughly a week if the key is elsewhere when you need to open a project. For a contractor working across sites that is genuinely useful, and it is worth raising at quote time rather than six months later.

Two generations of the same problem: a node-locked floppy that has to be moved rather than copied, and a USB key that only covers one machine at a time.

Install errors worth knowing about before you start

A couple of habits head off most of them.

Run the installer as an administrator, from a package that finished downloading. Error 1723 reports that a DLL required for this install to complete could not be run, and it comes up often enough on this stack that ruling out a partial download belongs at the front of the list rather than the end. Pulling the files through Rockwell's own download manager instead of a plain browser grab is the dull fix that tends to work.

Install order matters more than it should. RSLinx Classic or Classic Lite goes on first, and the troubleshooting list in the guide opens in exactly that place: confirm RSLinx Classic or RSLinx Classic Lite is installed, latest version recommended. Next, check the machine has the memory the hardware requirements call for. Then, if FactoryTalk Security or Security Server support was enabled, find out whether the machine can still reach the FactoryTalk Directory Server. A programming laptop that has left the plant network will refuse to start RSLogix 500 software for reasons that have nothing to do with the software, and that one sends people chasing ghosts.

Frequently asked questions

Is RSLogix 500 software free?

Not for SLC 500 work. Three free downloads exist with no trial period: Micro Starter Lite, Emulate 500 and RSLinx Classic Lite, and between them they cover the MicroLogix 1000, the MicroLogix 1100 and the emulator. Programming any SLC 500 processor takes a paid license. Note also that the free RSLinx tier handles drivers but not DDE or OPC.

Can you still buy RSLogix 500 software?

Yes. The product documentation is still maintained and the Rockwell support article covering it was updated in September 2025. Purchase runs through Allen-Bradley and Rockwell distributors rather than a public price list. Rockwell's newer platform recommendations on its product pages are aimed at new installations, not at the SLC 500 and MicroLogix hardware already running on the floor, and that installed base is not going anywhere soon.

How much does RSLogix 500 software cost?

There is no published list price, so a distributor quote is the only real answer. Figures seen in the field put Standard, 9324-RL0300ENE, around $3,600 and Professional at roughly double. Confirm both for your own region before you budget against them.

Will RSLogix 500 software run on Windows 11?

The September 2018 Getting Results Guide lists Windows 7 SP1 and Windows 10 on the client side and says nothing about Windows 11, which did not exist when it was written. Check Rockwell's compatibility pages before committing to a machine. If the specification is yours to write, Windows 10 is what the documentation covers.

Do I need RSLogix 500 software just to back up an SLC 500 program?

Yes, along with three other things: RSLinx, a communications port on the PC, and a cable matched to that model of processor. A flash memory module such as a 1747-M11 holds a copy in hardware, which is worth having, but pulling the program onto a PC still needs the software and the right cable.

The hardware on the other end of the cable

Whichever edition you end up licensing, none of it matters if the controller is the weak link. IQElectro stocks the families RSLogix 500 software was written for. SLC 5/01 through 5/05 processors, 1746 I/O, power supplies, memory modules including the 1747-M11, and MicroLogix 1000 and 1100 controllers. The programming converters and cables are on the shelf too, the 1747-UIC and the 1761-CBL-PM02 among them. Everything is tested and carries a 2-year warranty. Send over the part numbers off your rack and we will tell you what we have.