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

L-force | PLC Designer
Concepts and Base Components

DMS 4.1 EN 03/2011 TD29 131
Referenced Libraries
• Libraries can include further libraries (referenced libraries), whereby the nesting
can have any desired depth. When you add a library including other libraries in the
library manager, the referenced libraries will be added automatically too.
• When creating a library project which includes other libraries, in the Properties of
each referenced library it can be defined, how it should behave later when getting
inserted in a project with its "father" library:
• 1. Its pure visibility in the Library Manager, indented below the "father" library, can
be deactivated. Thus "hidden" libraries can be available in a project.
• 2. If you are just creating a pure "container" library, that is a library projects which
is not defining own modules, but only is referencing other libraries, the access on
the modules of these libraries can be simplified. A "container" library is created
because you want to include a complete set of libraries in a project at the same
time by just including the container library. In this case it might be desired to
simplify the access on the modules of these libraries by making them "top-level"
libraries, which allows to leave out the namespace of the "container" library in the
access path. This can be reached by activating option "Publish...". However this
option should really only be activated when creating a container library and should
be handled with great caution!
• For how to uniquely access modules or variables of referenced libraries see below.
Library Versions
• Multiple versions of the same library can be installed on the system.
• Multiple versions of the same library can be included in a project. It is regulated like
described in the following, which version of a library an application will use:
If multiple versions are available on the same level within the same Library
Manager, it will depend on the current library properties, which version will be
accessed (a defined one or always the newest).
If multiple versions of the same library are available on different levels within the
same Library Manager (which is the case for referenced libraries), unique access to
the library modules or variables is reached by adding the appropriate namespace
(see the following paragraph).
Unique access to library modules or variables
• Basically, if there are several modules or variables with the same name within a
project, the access on a module component must be unique, otherwise compile
errors will be detected. This applies for local project modules or variables as well as
those which are available in included libraries and in libraries referenced by the
included ones. The uniqueness is reached in such cases by prefixing the module
name by the appropriate library namespace.