Versions and their Significance

There are different versions in the CODESYS univers. Each one has a specific significance.

  • Version of the CODESYS development environment

    A new version of the CODESYS development environment is released at regular intervals. This creates a setup consisting of various components. This collection is given a specific version. New features and improvements are usually included in a service pack.

    Versions for a service pack have a zero in the fourth position.
    e.g: CODESYS V3.5 SP20 or 3.5.20.0
    Normal bug fixes are included in a patch.
    e.g: CODESYS V3.5 SP20 Patch 2 or 3.5.20.20
    Exceptional bug fixes in a hotfix.
    e.g: CODESYS V3.5 SP19 Patch 6 Hotfix 2 or 3.5.19.62

  • Version of the Compiler used inside the IDE

    The compiler is always distributed together with the CODESYS development environment. It therefore has the version number of the CODESYS version with which it was released. Every CODESYS development environment contains all compiler versions from the past back to 3.5.17.0. If CODESYS is started with a special parameter (--debug) , all built-in compiler versions can be selected.

    CODESYS.exe --profile="CODESYS V3.5 SP21" --debug

  • Version in which a CODESYS project was saved.

    Normally, a project or library is saved in the format that belongs to the current version of the development environment. This information can be retrieved via the project information dialog (see: storage format). The menu command “Save Project as …” can be used to select an alternative format that was used by earlier versions of the CODESYS development environment.

    This action can be used to prepare a CODESYS project so that it can be opened with an earlier version of the CODESYS development environment.

    Important

    A library should always be edited with the CODESYS development environment, compiler, or storage format version with which it is to be used, at a minimum. For example, if a library is to be used in CODESYS version SP18, it could be edited in CODESYS SP16 Patch 3.

    It is usually not possible to edit a library using the current compiler version of a modern version of the CODESYS development environment with its own storage format and enable the library to be used in an older CODESYS version at the same time.

  • Version of the CODESYS Runtime System on the PLC

    Currently, a version of the runtime system is published with every release of the CODESYS development environment. Therefore, the two usually have the same version. However, it is not necessary for the development environment and the compiler to be the same version. Newer compilers can typically generate code for older runtime systems without issue.

  • Version of the Library

    Every change to a library requires a change to the version of this library. Libraries implemented in the runtime system bear the version number of the system with which they were released. However, many libraries have not changed for years. These libraries have the number of an earlier runtime system but can be used on modern systems without any problems.

  • Version of a Device Description

    A device description is typically included in an extension of the CODESYS development environment and/or the runtime system. Any change to a device description requires a change to its version. Typically, the version number of the package with which the device description is supplied is given to a device description. The version of a device description does not necessarily have a close connection with the other versions mentioned here.