The richness of platforms like CODESYS often remains untapped due to a common challenge: understanding how to utilise these tools to their fullest potential. All too frequently, engineers and automation enthusiasts encounter hurdles in harnessing the complete capabilities of such platforms simply because the intricacies and functionalities aren’t crystal clear.
This blog aims to bridge that gap by diving deep into the recent CODESYS Recipes 4.3.0.0 release. We’re dissecting each newly addressed issue and enhancement not just for the sake of technical jargon, but to empower engineers and enthusiasts alike. Understanding these updates isn’t just about deciphering codes or patch notes; it’s about empowering users to leverage CODESYS effectively, ensuring that every feature, every tweak, and every resolution serves as a catalyst for innovation.
The goal? To equip you with the insight and understanding needed to navigate CODESYS with confidence. By unpacking these updates, we’re exposing the true potential of CODESYS. There will be specific, to the point information on the issue, resolution, and engineer benefits to help you unpack these fixed and enhancements better.
Table of content:
- Bug Fixes and Enhancements
- REC-130: Recipe Definition Transformation Bug
- REC-126: Array Optimisation Check Fix
- REC-125: Writing Variables Issue Resolution
- REC-120: Prohibition of Backtick Identifiers
- REC-117: Correcting Data Type Handling for TOD
- REC-114: Resolving Inconsistencies in Recipe Manager
- REC-109: Addressing Documentation Requirements
- Conclusion
Bug Fixes and Enhancements
- REC-130: Recipe Definition Transformation Bug
Issue: When defining a recipe involving Time of Day (TOD) and arrays, an unintended transformation occurred, converting the data type to BOOL, which was incorrect.
Resolution: The bug causing this unintended transformation was fixed, ensuring that the recipe definition involving TOD and arrays retains the correct data type without transforming into BOOL.
Engineer Benefit: Engineers working with recipe definitions involving Time of Day (TOD) and arrays can now rely on accurate data representation without unintended transformations to BOOL. This ensures that time-related data in recipes remains consistent and usable, avoiding unexpected data changes that could affect critical processes or calculations.
- REC-126: Array Optimisation Check Fix
Issue: The minimum and maximum value checks were not working properly for arrays that were optimised with structures. This caused inconsistencies in validating the array values.
Resolution: The issue was rectified to ensure that the minimum and maximum value checks function correctly for arrays optimised with structures, ensuring accurate validation of array values.
Engineer Benefit: Engineers dealing with arrays optimised with structures will now have reliable minimum and maximum value checks. This accuracy is crucial in ensuring data integrity and adherence to specified limits, preventing potential errors in systems relying on validated array values.
- REC-125: Writing Variables Issue Resolution
Issue: While using the ReadAndSaveRecipe function with multiple recipes and arrays, there were instances where the function inappropriately wrote to certain variables, leading to unexpected behavior.
Resolution: The problem causing unintended variable writing during the use of ReadAndSaveRecipe with multiple recipes and arrays was fixed, preventing inappropriate writing to variables.
Engineer Benefit: Engineers dealing with arrays optimised with structures will now have reliable minimum and maximum value checks. This accuracy is crucial in ensuring data integrity and adherence to specified limits, preventing potential errors in systems relying on validated array values.
- REC-120: Prohibition of Backtick Identifiers
Issue: Backtick identifiers (such as “`”) were permitted for recipe definitions, causing inconsistencies and potential conflicts within the system.
Resolution: The platform was updated to disallow the use of backtick identifiers for recipe definitions, ensuring consistency and preventing potential conflicts within the system.
Engineer Benefit: By disallowing the use of backtick identifiers in recipe definitions, engineers can avoid potential conflicts or inconsistencies within the system. This helps maintain system stability and reliability, reducing the likelihood of errors caused by conflicting identifiers.
- REC-117: Correcting Data Type Handling for TOD
Issue: There were inaccuracies in handling data types associated with Time of Day (TOD) within the Recipes, leading to incorrect processing or interpretation of TOD-related data.
Resolution: Corrective measures were implemented to ensure accurate handling and processing of data types linked to Time of Day (TOD) within Recipes, rectifying any inaccuracies.
Engineer Benefit: Engineers working with Time of Day (TOD) data in recipes will see improvements in data handling accuracy. This ensures precise processing and interpretation of TOD-related data, crucial in time-sensitive applications where accurate time representation is essential for correct system behavior.
- REC-114: Resolving Inconsistencies in Recipe Manager
Issue: In specific customer projects operating under Linux RT, inconsistencies arose when assigning values within the recipe manager, causing irregularities in the functionality.
Resolution: The inconsistencies observed while assigning values within the recipe manager, particularly in Linux RT environments for specific customer projects, were resolved to ensure proper functionality.
Engineer Benefit: Engineers working with Time of Day (TOD) data in recipes will see improvements in data handling accuracy. This ensures precise processing and interpretation of TOD-related data, crucial in time-sensitive applications where accurate time representation is essential for correct system behavior.
- REC-109: Addressing Documentation Requirements
Issue: Essential Python stubs required for documentation purposes in the new recipe scripting were missing.
Resolution: The necessary Python stubs were created and integrated into the system to support documentation needs for the new recipe scripting, ensuring comprehensive and accurate documentation.
Engineer Benefit: Engineers working with Time of Day (TOD) data in recipes will see improvements in data handling accuracy. This ensures precise processing and interpretation of TOD-related data, crucial in time-sensitive applications where accurate time representation is essential for correct system behavior.
Conclusion
The CODESYS Recipes 4.3.0.0 update isn’t just about fixing bugs—it’s about engineering precision and user-centric solutions.
Each bug addressed in this update had a tangible impact. Take REC-130, for instance. The fix ensures that Time of Day (TOD) data in recipes won’t unexpectedly transform into BOOL, maintaining data integrity critical for accurate calculations.
REC-126’s resolution is a game-changer. Engineers using arrays optimised with structures can now rely on precise minimum and maximum value checks. This means accurate data validation, a must for robust systems.
The ReadAndSaveRecipe fix (REC-125) eradicates variable writing mishaps. No more surprises while managing multiple recipes and arrays, ensuring rock-solid data integrity.
REC-120 might seem minor, but prohibiting backtick identifiers in recipe definitions ensures system stability. It’s about avoiding conflicts and maintaining a reliable environment for engineers.
Handling TOD data (REC-117) is now spot-on. Accurate processing means flawless time representation, crucial in time-sensitive applications.
REC-114 resolved inconsistencies in Linux RT projects. It’s not just about fixing bugs; it’s about ensuring seamless functionality, particularly in critical environments.
Lastly, REC-109—the inclusion of Python stubs—is about comprehensive support. It’s a nod to engineers, offering vital documentation for new recipe scripting.
This blog isn’t just a breakdown of updates; it’s a toolbox for engineers. It arms them with precise information to harness CODESYS confidently, leveraging every update to fuel innovation and progress in automation and engineering. The aim is clear: empower engineers, elevate precision, and fuel progress.
Contact us HERE if you’re interested in implementing CODESYS in your industrial projects to unlock its benefits and drive innovation in your industry.
Or to learn more about what we can do to help your automation requirements, please click projects, products & services.
Ti2 is currently very focused on working with its global partners to secure stock and avoid long delay times in delivering products to their customers. Together with our trusted partners, we are here to provide solutions for your needs.
Please click here to email us your inquiry, we would like to hear from you.
