Codesys serves as the basis for numerous OEM-branded HMI software options. Exploring the use of Codesys independently, without relying on OEM software, poses both benefits and drawbacks. While some OEMs may incorporate unique features into their software that are not present in Codesys, a direct approach using Codesys offers versatility and customization options. Any insights or illustrations regarding this matter are greatly appreciated in offering guidance on this subject.
When using the basic version of CoDeSys available for download, you are limited to run time targets for a PC. To develop on PLC hardware, you typically require the manufacturer's edition of CoDeSys or at least the appropriate targets to use with the basic version. One of the standout features of plain CoDeSys is its simulation capabilities, which, when paired with the included visualization tools, creates a robust platform for educational and proof of concept projects.
Whenever I inquire with a vendor promoting their CoDeSys capabilities, I often receive baffled looks in return. Why settle for anything other than "CoDeSys Provided by Festo," "e!****PIT," "EcoStruxture," "SoMachine," "Automation Builder," "IndraWorks," or "PLCNext Engineer"? These solutions are all CoDeSys-based and come equipped with the necessary libraries. However, what happens when you need to integrate multiple vendors and encounter conflicts or complex dependencies? Fortunately, Wago recently introduced libraries and target packages for standard CoDeSys v3 to support their PFC200 family controllers, a positive development. The compatibility of various CoDeSys libraries offers both advantages and disadvantages. Opt for a version that aligns with your specific requirements, such as support for numerous servos, IoT capabilities, or a cost-effective hardware platform, and consider running it in a Virtual Machine for added flexibility.
One of the key benefits is the ability to access the most up-to-date features and bug fixes, which are typically integrated into vendor-specific versions within 2 to 3 years. Additionally, you can purchase target licenses for PLCs from Codesys' online store for various models. Wago has made the decision to transition from e!****pit back to using Vanilla Codesys, a move that has been well-received. Personally, I utilize the PFC100 license from Codesys for our machines. The new CFC100 and PFC200 now come with an included target license for Vanilla Codesys. While the delay in updating the PFC100 is frustrating, the overall functionality is still impressive.
Thank you for sharing your input, everyone! I'm relieved to know that I'm not alone in wondering about this. I am intrigued by what I have heard about Wago, so I will begin researching their product range.
A key advantage of utilizing CODESYS is that Engineer does not seem to provide support for CFC programming. This makes CODESYS a valuable tool for developers looking to implement CFC in their projects.
In my experience, using Codesys independently does indeed allow for a higher degree of customization and versatility, which can be invaluable for certain complex projects. However, beginners or those under time constraints might benefit more from OEM software, which often presents a more straightforward, user-friendly approach with features specifically tailored to pertinent tasks. It essentially boils down to the balance between customization and ease-of-use based on individual project needs.
Absolutely agree with your point on the flexibility offered by using Codesys. Using it directly often means you're not limited by OEM-specific restrictions, which can be a huge advantage in certain projects. However, the downside could be that you might need to spend some extra time learning and getting accustomed to Codesys itself. It's a trade-off between convenience and customizability really. For example, in a recent project, I used Codesys independently and found it allowed for fine-tuning in my logic sequences that the OEM version wouldn't permit. However, I had to invest a significant amount of time understanding the Codesys setup. So, it definitely depends on what your specific project needs are and how much time you're willing to put into mastering the software.
You raise some great points! Using Codesys independently definitely gives you more flexibility and the chance to tailor solutions to your specific needs. I’ve found that while certain OEM software can come with handy pre-configured features, relying solely on Codesys allows for deeper customization and integration with various hardware. Plus, it can often lead to cost savings in the long run since you're not tied to licensing fees for OEM products. That said, it’s crucial to consider the learning curve and the initial setup time when going solo with Codesys; those can be a bit daunting, especially if you're used to the more polished interfaces of OEM offerings.
You've raised an interesting point about the balance between versatility and specialized features. Using Codesys independently can definitely open up a world of customization, allowing developers to tailor applications specifically to their needs. However, it's important to consider the potential learning curve and the investment required to recreate some of the unique functionalities that OEMs might offer. For instance, if you're working on a complex automation project, the time saved from using an OEM’s streamlined interface and pre-built templates could sometimes outweigh the benefits of full customization with Codesys. Ultimately, it comes down to your project requirements and how much you're willing to invest in development and ongoing support.
✅ 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: Using Codesys independently allows for greater versatility and customization options in your HMI development. It provides more control over the design and functionality of your system.
Answer: Answer: One drawback is that some unique features provided by specific OEM-branded HMI software may not be available when using Codesys independently. It's important to weigh the trade-offs between customization and potential feature limitations.
Answer: Answer: The decision between using Codesys independently or OEM-branded HMI software depends on factors such as the specific requirements of your project, the level of customization needed, and the importance of any unique features offered by OEM software. It's recommended to assess these aspects to determine the best approach for your HMI development.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.