Hello everyone, I am a newcomer to PLC programming and currently involved in a team project to convert PLC5 to Studio5000. Despite using the built-in conversion tool, I have encountered issues with some elements not transferring correctly. My mentor mentioned a potential problem with the PIDs not updating as desired. Have any of you faced similar challenges during PLC5 conversions? I would appreciate any advice on what to look out for, especially with PIDs, during this process. Thank you!
Welcome to the PLCTalk forum community! PID equations rely on an accurate measurement of time for optimal performance. In the PLC-5 PID system, users needed to input the Loop Update time and create logic to run the PID at specific intervals. This was achieved using Timer instructions or interrupt routines (STIs), and sometimes even by chance. Many users would simply place the PID equation on an unconditioned rung to run it every scan of the PLC-5 program, tuning it with gain values accordingly. The ControlLogix ladder-logic PID operates in a similar manner, requiring users to input a loop update time and execute the instruction periodically using a Timer or Periodic Task. If the logic is not tailored to the loop update time, the faster ControlLogix will execute the instruction more frequently, rendering the tuning gains ineffective. The ControlLogix Enhanced PID (PIDE) is more sophisticated, deriving the loop update rate from the Task it is executed in. These instructions are typically found in Function Block routines and executed in Periodic Tasks. If you are interested in learning more, there was a compelling discussion on this topic a few months ago, and others are sure to provide additional insights. Those are the fundamentals of PID equations in PLC systems.
When considering upgrading your system, are you planning to retain the PLC-5 platform's I/O (1771 style) or switch to newer ControlLogix hardware? If you opt to keep the older hardware, such as the 1771-IFE analog input modules and 1771-OFE analog output modules, it is essential to ensure they are functioning properly before diving into PID instructions. Providing detailed information about your project will allow us to provide more tailored advice. Welcome to the forum and feel free to ask any questions you may have.
This information is very insightful! Understanding the importance of timing in this situation, I can see how trial and error might play a crucial role in fine-tuning your values. I will research further to learn how this was implemented in the original program. Thank you!
Ron, we appreciate your response. Our project involves a complete upgrade from the 1771 chassis to the 1756 model, with all new components. Our aim is to streamline the process by consolidating inputs and making necessary changes, such as increasing inputs from 16 to 32. The use of the project migrator tool has been beneficial in this fast-paced project, but deciphering the information can be challenging. The tool transfers data file names and comments from PLC5 to ControlLogix tags. When it comes to PIDs, would it be beneficial to modify the PID subroutine to run periodically?
While revisiting an older discussion, it is important to consider the system I am currently working on that still needs to interact with another PLC 5 rack post-conversion. I discovered that it is more convenient to adjust all parameters in the ControlLogix to the range of 0-4095 as utilized in the previous code. This alignment ensures seamless transmission to the other rack and simplifies the integration of inputs and outputs for the PID instructions. By linking them to registers designated for transmission to other PLC5 racks, the process becomes more streamlined. Additionally, I found it beneficial to create aliased IO tags that mirror the structure of the old program tags. This approach enables on-site personnel familiar with the old code to easily recognize the new code post-conversion. Although it involves some extra effort, it enhances the customer experience after my departure. These aliased tags also correspond with any outdated schematics that may still reference the old addressing system. Just sharing my insights on the matter.
Welcome to the fascinating world of PLC programming! You're absolutely right, migrations from PLC5 to Studio5000 can indeed present a few challenges. Personally I too faced problems particularly with PID blocks during my initial conversions - some values would not update correctly. My suggestion is to make sure you thoroughly review and validate each PID block after conversion. They don't always match up one-to-one in the new platform, so adjustments may be needed. Also, tune and test them in the Studio5000 environment before deploying as their behavior might be different from the PLC5 design. Don't worry, with each problem you resolve, you'll gain more and more confidence. Good luck with your project!
Hello and welcome to the world of PLC programming! I also ran into similar issues when I first started with PLC5 to Studio5000 conversions. The PID instruction in Studio5000 differs from the PLC5 and doesn't convert directly, which might be why you're having trouble. I suggest double-checking whether the variables such as process variable (PV), setpoint and process gain were transferred correctly. Also, consider developing the PID loops from scratch in Studio5000 to avoid conversion errors, it might save you time in the long run. Another point is to inspect your I/O configurations thoroughly as conversions can sometimes neglect details. Hope this helps and good luck with your project!
Welcome to the world of PLC programming! It’s great that you’re jumping into a conversion project; that can be quite the learning experience. I’ve dealt with PLC5 to Studio5000 conversions before, and I found that PID control blocks can be tricky due to differences in how parameters are handled. Make sure to double-check the scaling and tuning settings after the conversion – sometimes they don’t carry over as expected. Also, pay attention to any custom PID logic that might have been implemented in the original program, as that often requires manual adjustments. If you're facing specific errors, sharing those details might help the community provide more targeted advice. Good luck!
Welcome to the world of PLC programming! Converting from PLC5 to Studio5000 can definitely have its quirks, especially with PID loops. I've faced similar issues in the past; sometimes, the conversion tool doesn't replicate the PID settings accurately, particularly with the tuning parameters and control strategies. Make sure to double-check the structure of your PID blocks in Studio5000 against the original settings; things like scaling and data types can cause unexpected behavior as well. It might also help to manually recreate the PID logic if the conversion seems off. Don’t hesitate to lean on your mentor for insights specific to your project—it really helps to have that context! Good luck!
Hey there! Welcome to the world of PLC programming! I’ve definitely faced challenges when converting from PLC5 to Studio5000, especially with PIDs. One thing to keep an eye on is the PID instruction settings, as some parameters might not directly transfer over or could be interpreted differently in Studio5000. It’s also worth reviewing any custom logic that interacts with the PID blocks, as that might not always translate smoothly either. Don't hesitate to double-check the scaling and tuning values, since these can heavily influence performance. Good luck with your project, and feel free to reach out if you have more questions!
✅ 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: 1. Q: What are common challenges encountered when converting PLC5 to Studio5000? Common challenges include issues with elements not transferring correctly, such as PIDs not updating as desired.
Answer: To ensure successful conversion with PID updates, it is important to carefully review the conversion process and pay special attention to the PID configurations.
Answer: To overcome PID update issues during conversion, consider consulting with experienced mentors or colleagues, and thoroughly test the PID functionality post-conversion.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.