dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separatorCreating and Configuring a Projectdl-breadcrumb-item__separatorConfiguring a Projectdl-breadcrumb-item__separatorRetrieving and Editing Project Information
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Retrieving and Editing Project Informationdl-permalink__symbolPermalink

You can use the “Project Information” object to retrieve information about your project and the associated file, and edit certain information.

The object contains information about

  • File attributes

  • Meta-information, such as manufacturer, title, or author

  • Properties with keys

  • Statistics

  • Licensing

  • Signing: This way of signing translated libraries is deprecated, and for security reasons should only be used if compatibility with older versions is required. If this method is used, then later you can use a public key token to verify that the library was last signed by the library vendor. As a library vendor, it is therefore crucial that you make the public key used available to the customer, for example in the documentation.

CODESYS saves the project information as an object within the project. When you transfer a project to another system, the “Project Information” object is transferred with it. There is no need for a project archive.

You can use property keys to access the project information externally via function blocks. For a library project, you can also query information about the licensing.

Editing meta-information

  1. Click “Project  Project Information”.

    The “Project Information” dialog opens.

  2. Click the “Summary” tab.

  3. Specify your data in the input fields (example: ‎0.0.0.1‎ in the “Version” input field).

    CODESYS creates a property with a key for each given value and manages them on the “Properties” tab. For a library project, CODESYS still uses the properties and sorts later in the library repository.

    If you select the option for CODESYS to create a functions block for these properties, then you can access the properties programmatically.

Creating functions for accessing properties

  1. Click “Project  Project Information”.

    The “Project Information” dialog opens.

  2. Select the “Automatically generate 'Project Information' POUs” option.

Example

Requirement: The following property is defined.

Key = nProp1
Type= number
Value= 333

  1. Select the “Automatically generate 'Project Information' POUs” option.

  2. Declare a property of the type ‎DINT‎, for example ‎showprop : DINT;‎.

  3. Call the function ‎GetNumberProperty‎: ‎showprop := GetNumberProperty("nProp1"); ‎

    You are granted access to the value in the application.

Note: The functions that are created with the “Automatically generate 'Project Information' POUs” option can be used only if the runtime supports the ‎WSTRING‎ data type. If this is not the case, then instead you can apply the “Automatically generate 'Library Information' POUs” option. You can use the functions created in this way at least in the application to access properties. These functions are not registered in the runtime.

Licensing library projects

If your project is a library project, then you can activate the library licensing in use here. The CODESYS Security Key is a dongle.

Requirement: The project is a library project.

  1. Click “Project  Project Information”.

    The “Project Information” dialog opens.

  2. Click the “Licensing” tab.

  3. Select the “Activate dongle licensing” option.

  4. Specify the dongle data in “Firm code”, “Product code”, “Activation URL”, and “Activation mail”.

    The library is licensed.

Creating private key files

  1. Click “Project  Project Information”.

  2. Click the “Signing” tab.

  3. Click the “Create Private Key File” button.

    The “Create Private Key File” dialog opens.

  4. Select a safe location, e.g. ‎D:\for lib developers only\mycomp_libkey.libpk‎ and exit the dialog with “Save”.