Lenze PLC Designer PLC Designer (R2-x) - Manual (Page 187)

L-force | PLC Designer
The Individual Components

DMS 3.2 EN 02/2011 TD29 185
Take note of the following restrictions:
• The name of a POU can not include any spaces
• A POU can not have the same name as another POU, a data type and should not
have the same as a visualization in order to avoid problems with visualization
changes.
• A data type can not receive the same name as another data type or a POU.
• A global variable list can not have the same name as another global variable list.
• An action can not have the same name as another action in the same POU.
• A visualization can not have the same name as another visualization and should
not have the same as a POU in order to avoid problems with visualization changes.
In all other cases, identical naming is allowed. Thus for example actions belonging to
different POUs can have the same name, and a visualization may have the same as a
POU.
In the case of a POU, the POU type (program, function or function block) and the
language in which it is programmed must also be selected. 'Program' is the default
value of Type of the POU, while that of Language of the POU is that of most recently
created POU. If a POU of the function type is created, the desired data type must be
entered in the Return Type text input field. Here all elementary and defined data
types (arrays, structures, enumerations, aliases) are allowed. Input assistance (e.g. via
<F2>) can be used.
Dialog for creating a new POU
After pressing OK, which is only possible if there is no conflict with the naming
conventions described above, the new object is set up in the Object Organizer and the
appropriate input window appears.