Creating a licensed library in CoDeSys

As is known a CoDeSys project can be saved as a library. If you want to create a licensed library you have to add the appropriate license information. For this perform the command File Save as ‘File’ ‘Save as’, choose data type ‘Internal Library’ or ‘External Library’ and press button Edit license info ….

In the dialog Edit Licensing Information enter the information described below. The license information will be added to the Project Info ‘Project’ ‘Project info’.

When later on the library will be included in a CoDeSys project, the license information can be checked up in the object properties dialog of the library in the:emphasis:library manager Library Manager.

Dialog: Edit Licensing Information

../_images/12a86802437390ee0a33139006eab46b

  • Common

    • Name: Enter a name for the library module which is used to represent it in the 3S Licensing Manager. This input is mandatory.

    • Vendor-ID: A manufacturer identifier, depending on the manufacturer specific licensing management tool.

    • Targets: Enter here the target ID(s) of the target system(s) for which the license should be valid. You can enter multiple IDs separated by a semicolon or as a range.

      Example: “12;15-19;21”;

      Herewith the IDs 12,15,16,17,18,19,21 are entered.

  • Contact

    • Licensing via phone / Licensing per via mail: Insert here the phone number resp. email address of the license provider. These inputs are mandatory.
    • Optional information: In the right window you can enter a text referring to the item currently marked in the left window: Description, Manufacturer, Vendor, Pricing information

Note

- It is reasonable to protect a library, which has been provided with licensing information, by a password Passwords. If you are going to save the project without password you will be pointed to that by a message box.

- The licensing information of a 3S library is stored internally with the library and will be registered on the computer automatically as soon as the library is included in a project. But the license information of modules which are not provided by 3S must be provided in a separate description file in compatible XML format, which can be read by the 3S Licensing Manager.