Lenze PLC Designer PLC Designer (R3-1) - Manual (Page 135)

L-force | PLC Designer
Concepts and Base Components

DMS 4.1 EN 03/2011 TD29 133
Creating V3.x libraries, Encoding, Documentation
• A »PLC Designer« project can be saved as library (<projectname>.library) and
optionally can be installed at the same time in the "System" Library Repository.
Only the objects managed in the POUs window will be regarded for a library
project. If you pointedly are going to create a library project, it is recommended to
choose template "Empty library" in the 'New Project' dialog.
Notice further on the following:
• In the Project Information a Title and a Version and the Company must be
specified. If the Default Namespace should be another than the library name, this
can be defined immediately here. Additionally it is recommended to specify a
category, because these will later serve for sorting the entries in the Library
Repository and Library Manager dialogs. If the library should belong to another
category than the default "Miscellaneous", an appropriate category description
must be loaded, either from a XML-file *.libcat.xml or from another library, which
already contains the information of such an description file. If necessary, a new
category description file must be issued or an existing one must be modified. The
information of the selected categories and the basic category description file will
be transferred to the local library project and later, when installing the library - to
the Library Repository. So the categories will be known in the Repository. If
afterwards another library again brings a description file with the same ID but
different content, then the information of the new file will be valid in the
repository.
• If the library includes further libraries, you should consider, how those referenced
libraries should behave later, when the "father" library will be included in a project.
This concerns version handling, namespace, visibility and access properties, which
can be configured in the properties dialog of the particular, referenced library. If the
library later, when it gets included in a project, always should reference another,
device-specific library,a placeholder can be used when configuring the reference.
• If the library modules should be protected against viewing and accessing, a library
project can be saved in encoded in encoded format (<projectname>.compiled-
library).
• Data structures of a library can be marked as libinternal. These non-public objects
carry the attribute 'hide' and therefore do not appear within the library manager,
the "List Components" functionality or the input assistant.
• In order to provide the user with information on a library module in an easy way,
an appropriate comment can be added to the declaration of a module parameter.
This comment will be displayed later, when the library is included in a project, on
the 'Documentation' tab of the Library Manager.