Limitations of Conversion
Important
Device projects cannot be exchanged between CODESYS 3 and CODESYS 4.
Development projects of the CODESYS File-Based Storage add-on in FBSPROJ format and device projects from CODESYS 4 in FBSDEV format are not compatible. Although both use the same storage format for the objects, the project structures above these objects differ.
Basically proceed as follows:
Save the reusable code in CODESYS 3 in a library.
Convert the library for CODESYS 4.
For more information, see the following: Converting Projects from CODESYS 3 for CODESYS 4.
In CODESYS 4, create a new device project and reconfigure the devices, the task configuration, and the communication settings.
Reference the imported library in the
Libraries.jsonfile.
Individual components of a device project in CODESYS 3 must be created new for the text-based, open data storage used in CODESYS 4.
In CODESYS 3 | In CODESYS 4 |
|---|---|
Device tree and device repository | File |
Library manager | File |
Task configuration | File |
Communication settings | File |
Project information | File |
In CODESYS 4, there is no pool of programming objects, as provided in the POUs by CODESYS 3. Instead, you can edit library projects in the same workspace as device projects.
In CODESYS 4, options and project settings are managed in the preferences. You can use the Preferences command to open this.
A scripting interface is not provided in CODESYS 4. Instead, you can use external tools – such as Python scripts or GitLab pipelines – to directly access the project files. Furthermore, comprehensive CLI commands are available to you to automate your workflows.
For more information, see the following: Switching from CODESYS 3