Optimizing Offline Editing Speed: A Comparison of Logix5000 v20 and Studio5000 v34

Question:

Looking for ways to speed up offline editing, particularly with search/replace functions? I have experience using both Logix5000 version 20 and Studio5000 version 34 for routine edits. When it comes to search/replace tasks, Logix5000 performs quickly, while Studio5000 operates at a slower pace. In Studio5000, each replacement triggers a "Loading Editor" message in the lower left corner, which appears to be the cause of the delay. Additionally, after finding the last element in a search, the dialog box often stalls for 4 to 5 seconds before allowing the next search operation.

Top Replies

I haven't come across any solutions yet. The newer versions seem to be plagued with slowness in various aspects. Opening IO module properties now is a painstakingly slow process with the "new" properties menus taking forever to load. Additionally, there are several extra clicks required, adding to the frustration. The structured text editor is also deteriorating in performance, causing lag issues when trying to view live values.

tlf30 mentioned experiencing slowness in newer versions of the software, particularly when opening IO module properties and navigating through the "new" properties menus. The structured text editor also seems to have worsening lag issues, especially when viewing live values. Additionally, the powerflex module properties and flex 5000 IO properties can take a long time to load, making tasks like copying and pasting devices and changing names or IPs more time-consuming due to the extra clicks required in the folder hierarchy.

Robertmee is looking for tips to speed up offline editing, specifically when it comes to search and replace functions. While searching and replacing a routine in Logix5000 version 20 is quick, the same process in Studio5000 version 34 is much slower. The bottleneck appears to be the "Loading Editor" message that flashes in the lower left corner with every replacement instance. Additionally, there is a delay of 4 to 5 seconds after finding the last element before being able to continue the search. One potential solution for offline editing could be to export the L5X file, perform the find and replace, and then re-import it. This may not always be feasible, but could be a helpful workaround in some cases.

I have not encountered any issues with slow search and replace in the various versions of the software, despite running large L83 programs. However, I have not tested them in a virtual machine - could this impact performance?

jstolaruk mentioned that in their experience, there have been no issues with slow search and replace functions in various versions of their L83 programs. However, they speculate that running the programs in a virtual machine (VM) may impact performance. Using a VMWare session with 8GB of memory and 60GB of hard drive space allocated for Win10 Studio 5000, while running Logix 5000 on a Win 7 machine with 4GB of memory, they found that the session itself was responsive, but tasks such as search/replace and loading module properties were frustratingly sluggish.

It sounds like you're dealing with a fairly common issue in Studio5000. Unfortunately, the "Loading Editor" message is inherent to the software and can't be bypassed as it involves reloading and recompiling the code after each modification. As for the delay, this could be due to the complexity and size of your code. However, you may want to consider breaking up larger routines into smaller, easier-to-manage segments which might help with performance. Also, consider consolidating repetitive code into AOIs (Add-On Instructions) or UDTs (User-Defined Types) to simplify your code and improve search/replace tasks. Rockwell's Knowledgebase might have some useful tips and tricks as well. Good luck!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

To add a comment, please sign in or register if you haven't already..   

Frequently Asked Questions (FAQ)

FAQ: 1. Question: Why does Studio5000 v34 operate slower than Logix5000 v20 for search/replace functions during offline editing?

Answer: Answer: Studio5000 v34 shows a delay in performance due to the "Loading Editor" message triggered with each replacement, along with a 4 to 5-second stall in the dialog box after finding the last element in a search.

FAQ: 2. Question: Are there any specific tips or workarounds to enhance the offline editing speed in Studio5000 v34?

Answer: Answer: Consider breaking down larger search/replace tasks into smaller segments to minimize the delay. Additionally, ensuring efficient system resources allocation and reducing unnecessary background applications can help improve speed.

FAQ: 3. Question: Is there a way to avoid the delay caused by the "Loading Editor" message in Studio5000 v34 during search/replace tasks?

Answer: Answer: Unfortunately, the "Loading Editor" message in Studio5000 v34 seems to be a built-in feature that may contribute to the delay. However, reaching out to Rockwell Automation support for potential updates or patches addressing this issue could be beneficial.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  â†’