CODESYS Development System

CODESYS is currently available in version V3.5 SP16 and can be downloaded from the CODESYS Store.

OEM customers (device manufacturers who offer devices programmable with CODESYS) can download the corresponding release document from the CODESYS Customer Portal or get the release information (inlcuding release notes) in the CODESYS JIRA database.

A detailed overview of all new features and improvements can be found in the features & improvements presentation.

• All editors of the IEC 61131-3 (FBD, LD, IL*, ST, SFC) plus different variants of the standard editors
  *IL was marked as obsolete by PLCopen, the IEC 61131-3 user organization, and is therefore no longer maintained. If required, IL can be enabled for use.
• Powerful and proven library concept for the reutilization of application
• Project configuration through wizards
• Input assistance for the input and configuration of data
• User-friendly programming with mouse and keyboard in all IEC 61131-3 editors
• Integrated compilers for many different CPU platforms optimize the controller performance.
• Comprehensive project comparison, also for graphic editors
• Extensive online features for debugging, optimization of the application code, and to speed up testing and commissioning
• Numerous security features for the protection of the source code and for safeguarding the operation of the controller
• Programmable devices from different manufacturers
• Extendibility and adaptability of the user interface without leaving the framework
• Transparent internal structures of the development tool and the available components
• Many seamlessly integrated tools for different kinds of automation tasks

• Real object-oriented programming (OOP) fully compliant with the 3rd Edition of the IEC 61131-3 Standard in all available editors without any additional tools
• Encapsulation of object-oriented program code in libraries with functional call interfaces: Convenient provision of, for example, system functions or special algorithms for PLC programmers without knowledge of OOP
• Inheritance of POUS to similar application parts to reduce development time and errors
• Object-orientation is not a must: Functional and object-oriented programming can be used and mixed as required.