Hello there, currently we are working on a project that involves multiple PLC's with a strong emphasis on redundancy through the use of ControlLogix and CompactLogix PLC's. The customer has requested that we standardize the firmware across all processors, with options including 34.xx, 35.xx, and 36.xx. While we are currently using 34.xx, we are considering upgrading to 35.xx to take advantage of any potential updates in the newer firmware version. Additionally, v35 will be supported for a longer period compared to v34, which may be phased out soon. As for v36, I personally have reservations about using it as it is relatively new. I recommend letting others test it first before considering its implementation. What are your thoughts on this matter?
Adding some context, based on the information provided, I am leaning towards using v35. Rockwell typically provides guidance and highlights known issues with previous firmware versions, so I will further research this. Thank you to everyone for your help!
When deciding between software versions like 35 and 34, it's important to weigh the benefits of new features against the risk of potential bugs. While some may think that version 34 is becoming outdated, it still runs smoothly for many users even after almost a decade. For example, one of our customers continues to use v23 without any issues, despite its age. It's crucial to evaluate your specific needs and goals for your programs before making a decision. Some versions, like v31, may have had significant bugs that could impact performance. Consider whether the new features in a newer version are worth the risk of potential issues, and choose the version that aligns best with your requirements.
I typically remain loyal to a specific software version for an extended period, especially if it is functioning effectively. However, it is essential to consider upgrading due to advancements in hardware. For instance, if you are utilizing a PLC that is only compatible with versions above v34, it is imperative to have the latest version installed.
It can be challenging to declare that a particular version is becoming obsolete. Versions tend to remain available for download even after newer ones are released. Personally, I don't see any issue with sticking to older versions, as long as they are compatible with the hardware in use. OG
I was upgraded to version 36 due to safety compatibility issues with servos, but everything is running smoothly now. The updated instructions have been beneficial in ensuring proper functioning.
While it is understandable to want to keep the firmware standardized across all processors, I agree with your cautious approach towards the new v36. It's always beneficial to see how the new firmware version performs in real-world applications before deploying it across your operation. As for upgrading to v35 from v34, given its extended support period, it seems like a wise decision. Remember, however, to thoroughly test how the upgrade impacts your current setup before any implementation, as even minute changes in operations can sometimes dramatically affect processes, especially in PLC operations.
I think you're on the right track with considering v35; it's a nice balance between stability and new features, plus the extended support is definitely a plus. I understand your hesitation with v36; it makes sense to let it mature a bit more before jumping in. Maybe a phased approach where you pilot v35 initially could provide the reassurance you need before possibly adopting v36 later down the line. It’s always good to make sure the whole team is on the same page with firmware standards, especially with redundancy in mind!
I think you’re on the right track considering an upgrade to v35.xx, especially with its longer support life and improvements over v34. It's definitely wise to be cautious about jumping to v36 right away; waiting for more feedback and real-world testing can save you from potential issues down the line. Plus, if you standardize on v35, you’ll benefit from consistency across all systems, which helps with maintenance and troubleshooting. How are you planning to manage the transition for the customer while minimizing downtime?
✅ 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: Some key considerations include the availability of updates and support, the maturity of the firmware version, and potential risks associated with using newer versions.
Answer: Answer: Upgrading to firmware version 35.xx may offer potential updates, longer support duration compared to v34, and improved features that could benefit the project's performance and reliability.
Answer: Answer: Some reservations about using firmware version 36.xx may include concerns about stability, compatibility with existing systems, and the need for more extensive testing before implementation due to its newness.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.