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

L-force | PLC Designer
Concepts and Base Components

DMS 4.1 EN 03/2011 TD29 57
3 Concepts and Base Components
3.1 Introduction and Basic Concepts
»PLC Designer« is a device-independent PLC-programming system. Matching the IEC
61131-3 standard it supports all standard programming languages but also allows
including C-routines. In combination with the »PLC Designer« runtime system it allows
to program multiple controller devices within one project.
Regard the following basic concepts determining programming with »PLC Designer«:
• Object Orientation: The mind of object orientation is not only reflected by the
availability of appropriate programming elements and features but also in the
structure and version handling of »PLC Designer« and in the project organization.
Multi-device and multi-application usage of a »PLC Designer« project is possible
basing on jointly used, instantiated programming units. So running various
applications on the same device and cloning of applications is possible as well as
mixing parameterizable and programmable controller devices in one project.
• Component-based structure of the programming system: The functionality
available in the user interface (editors, menus etc.) depends on the currently used
components (plug-ins) defined in a profile. There are system components, which
are essential, and optional components. Additionally to the default 3S plug-ins,
customer specific plug-ins can be created by means of the Automation Platform
tool-kit.
• Version handling: A simultaneous installation of several versions of »PLC Designer«
components and working with the desired combination of versions is possible. This
also pertains the device-specific use of different compiler versions. Individual
functions can be added without having to update the whole version.
• Project organization is also determined by the mind of object orientation:
A »PLC Designer« project contains a PLC program composed of various
programming objects and it contains definitions of the "resources" which are
needed to run instances of the program (application) on defined target systems
(devices, PLCs).
So there are two main types of objects in a project:
Programming objects (POUs):
These are programs, functions, function blocks, methods, interfaces, actions, data
type definitions etc.
Programming objects which can be instantiated in the entire project, i.e. for all
applications defined in the project, must be managed in the POUs window.
The instantiating is done by calling a program POU by an application-assigned task.
Programming objects which are managed (only!) in the devices window, i.e. which
are directly assigned to an application, cannot only be instantiated by another
application inserted BELOW.