Off Topic: After submitting many and varied messages to Rockwell about how tech notes like these (you know, the ones with information you need to actually get the product you purchased to work) should not be locked, I’ve come to the conclusion either they don’t read customer feedback, or they just don’t agree with these sentiments.

Sadly, while I did find two tech notes covering this error, it appears that just being a customer who purchased this expensive software wasn’t enough to unlock the solutions to this bug: Note: While our blog does not have permission to share the contents of locked tech notes, the good news is your local Rockwell distributor or rep should be able to share them with you 🙂 Not having run into any issues with either v20 or v30, you can probably imagine that I was a little frustrated during rehearsals for my “Studio 5000 First Look” lesson, when every time I tried to create a v21 project Studio 5000 crashed.Īnd since I was able to easily duplicate the issue on multiple VMs, I figured it had to be a known bug, so I pointed my browser at Rockwell’s Knowledgebase to search for a solution. In fact, over the last few months I’ve been spending a lot of time in RSLogix 5000 v20, and Studio 5000 Logix Designer v30, creating and refining the code and scenarios for my Compact Basics course’s new programming lessons.

NOTE: For those who are having this issue and need to fix it asap, use this LINK to scroll down to the details about the fix I implemented. As I was prepping to film additional lessons for my CompactLogix course yesterday, I ran into a completely new Studio 5000 Logix Designer “Fatal Error” that I hadn’t run into before.Īfter I duplicated the issue on two different PCs, each running two different Windows 10 VMs, I was convinced something was wrong with the software and not just my installation.

Rslogix 5000 emulator download v30