Hello everyone, I am currently facing a challenge with a system integration done by a third-party provider prior to my tenure at the company. I am unable to access the logic within the system, with only JSR instructions available in the Main Routine. This limitation is impeding my ability to identify and address the issue at hand. It appears that access to the system may be restricted by the original installers to prevent tampering and potential legal disputes. Despite this obstacle, I am optimistic that there may be a workaround to help us troubleshoot the problem and get production back on track. Your assistance in this matter is greatly appreciated. Thank you for your support.
Which programming language does your studio support? Is it standard, lite, or pro? If you're unable to open a certain language, right-click on it and go to properties to see if it's written in ladder logic, structured text, or function blocks. It's possible that you may not have access to certain languages, as only the standard version offers access to ladder logic.
If you are unable to access certain routines, you may have them locked out. To unlock them, search for "License Source Protection" in the Help pull-down menu under Contents in Studio. This will provide guidance on how to manage security settings and permissions for your software.
When a subroutine is locked out, a popup should appear when attempting to access it. If the subroutine is empty, it may indicate that your version of RSL/Studio 5000 lacks the necessary language, preventing the popup from showing. Without the required language, the entire PLC program will be uploaded and saved, and the complete program will be downloaded to a new CPU. However, you will not have the ability to view, monitor, or edit it.
Hey there, it indeed sounds like you've stumbled onto a tricky problem. If your access is restricted and you're only having JSR instructions, a good place might start by contacting the third-party provider. They should, at minimum, be able to guide you on the debugging process or provide some insights into the integration logic. Sometimes initial agreements with providers include some kind of support. Meanwhile, remember to document the specific issues you're encountering. That way when you do get in contact with them, you can give a detailed report, speeding up the troubleshooting process. All the best!
Hey there, it sounds like you're in a tough spot. One method that has worked for me in similar circumstances is contacting the original third-party provider. Usually, they should be able to either explain the logic behind the system or provide you with a bit of technical support, even if there is any contractual challenge to system access. Alternatively, if access is completely out of the question, you might have to consider a re-engineering strategy for your current system - a more comprehensive, but a possibly necessary solution. Good luck!
Hi there! Your predicament does sound sticky! In your position, the first step I would suggest is reaching out to that third-party provider your company previously worked with, if at all possible. They may have some unique insight or even documentation to help understand the system and evaluate the issues more effectively. In case of limited or no access to the third-party provider, try to find out if the vendor provided any troubleshooting guide/manual. That could provide a good starting point, even with the given limitations. Another thought: try talking to your fellow engineers in case they have some experience with similar issues before. Perhaps there's someone on your team or in your network who already has a way to crack this nut! Good luck, keep us posted.
I've had a similar experience in the past with third-party providers making it tricky to gain access to a system's logic. While it does come across as restrictive, it's often tied to some legalities, as you've said. One solution that worked for me was directly contacting the provider and requesting a walk-through of the system. You'd be surprised at how many providers are willing to offer assistance, especially if your issue halts production. And in case they are not forthcoming, seeking help from a different consultant who is familiar with the particular system integration might prove beneficial. Remember, patience will be key here. Good luck with everything!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: It is possible that the original installers restricted access to the subroutines to prevent tampering and legal disputes, which is limiting your ability to troubleshoot the system.
Answer: Answer: To troubleshoot the issue and access the logic within the system, you may need to explore workarounds or seek assistance from experts familiar with Logix 5000 systems.
Answer: Answer: You can try reaching out to the third-party provider or consulting with professionals who have experience working with Logix 5000 systems to help you navigate through the limited access and troubleshoot the system effectively.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.