Are my projects upwards and downwards compatible?

  • Yes to the upwards compatibility but with one restriction: You may import your projects which you have created in a previous version of logi.CAD 3 in any subsequent version. But use a new workspace for each version (see the following warning).

  • Yes to the downwards compatibility but with restrictions: You may import your projects which you have created in a subsequent version of logi.CAD 3 in any previous version – if the previous version does support all features that you are using in the project (e.g. the used keywords for the ST-syntax or new possibilities in the FBD-editor). Again, use a new workspace for each version (see the following warning).
    The article "Release notes for version" lists extensive information which version provides which features. If a used feature is not supported in the previous version, the Error view lists appropriate messages after you have imported the project.

    Special restrictions

    • FBD -objects that have been saved in version 2.5.0 or a following version cannot be opened in versions < 2.5.0 anymore.

    • For projects created or imported in version 3.0.0 (or a later version), some steps are required after the projects have been imported within versions < 3.0.0. These steps are:

      1. Delete the object library.libref that is displayed in the project.

      2. Install any custom libraries within the properties of the project. Details: See "Installing a library".

      3. Close the project and reopen it.

    • For projects that are containing function blocks with in-out variables (= VAR_IN_OUT) and that have been created or imported and cleaned in version 3.1.0 (or a later version), some steps are required after the projects have been imported within versions < 3.1.0. Details: See "Functions blocks with VAR_IN_OUT from version < 3.1.0 prevent the building of the application".

If you have installed different versions of logi.CAD 3 and you want to use them at the same time or you want to start the same version of logi.CAD 3 repeatedly, enter a new workspace per started version of logi.CAD 3. If you are using the same workspace for versions that are opened at the same time, unforeseen problems might occur when operating logi.CAD 3. A workspace used in logi.CAD 3 < version 1.27.0 is not compatible to logi.CAD 3 ≥ version 1.27.0.

If you use such a workspace in a following version anyway and you load an application onto a PLC, the application is not loaded for the imported project and this message is displayed: The application for the PLC (resource "name", platform toolkit "name") cannot be created/loaded. Check the views "Error Log" and "Problems" for more information.
This is how you are able to continue using the workspace and loading the application onto the PLC:

  1. Click images/download/attachments/451280970/IconViewMenu-version-1-modificationdate-1598000630466-api-v2.png in toolbar of the project explorer and select Filters and Customization... In the dialog, uncheck src-gen folder and target folder (under Filter) and click OK.

  2. Delete the shown folders src-gen and target for the imported projects.

  3. Click images/download/attachments/451280970/IconViewMenu-version-1-modificationdate-1598000630466-api-v2.png again in toolbar of the project explorer and select Filters and Customization... In the dialog, check src-gen folder and target folder (under Filter) and click OK. Those folders are automatically created later on but you do not need those folders anymore.

  4. In menu Project, select Clean... In the dialog, select Clean all projects and click OK.

images/s/b2ic8e/9012/1ca6q62/_/images/icons/emoticons/information.svg logi.cals recommends to install and use the most current versions of logi.CAD 3 and the runtime system so that the latest features and problem fixes according to the release notes are provided in the used version.


Did this article help you? Did you find the requested information in this user documentation?
If not, contact the support team of logi.cals. State your questions or suggestions to improve/enhance the user documentation as detailed as possible.