Knowledge Protection for Libraries

When releasing libraries, two features are available to protect your know-how. Both are to be set in the 'Release As Library' dialog during the release procedure.

You can define the visibility of each user-defined POU and data type, i.e., define what the user of your distributed library can use and see in his project.

Visibility

Meaning

Visible

The user of the library can open the POU code/data type declarations in read-only mode.

The following items are always 'Visible':

safety-related POUs
devices

Restricted

The POU prototype is visible to the user of the library.

This setting is only available for non-safety-related POUs (category 'Programming').

Hidden

The data type/POU is not visible to the user of the library.

Note
Depending on the POU dependencies (FB calls between POUs), 'Hidden' may be not allowed to be selected. An appropriate message informs about this.

This setting is only available for non-safety-related POUs and data types (category 'Programming').

You can define the distributability of the entire released library in the drop-down list 'Redistribution'. This know-how protection applies to all project parts which are contained in the library (whereas the visibility can only be set for local POUs and data types).

Redistribution	Meaning
Unlimited (cascaded)	Your library can be redistributed. The user of your library will be able to release his own project as IEC library even if it contains your library.
One level only	Your library can only be included but not redistributed. The user of your library will not be able to release his own project as IEC library if it contains your library.