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

L-force | PLC Designer
The Resources

DMS 3.2 EN 02/2011 TD29 401
The name of such a variable consists of a complete instance path through which the
individual POUs and instance names are separated from one another by periods. The
declaration must contain an address whose class (input/output) corresponds to that
of the incompletely specified address (%I*, %Q*) in the function block. Also the data
type must agree with the declaration in the function block.
Configuration variables, whose instance path is invalid because the instance does not
exist, are also denoted as errors. On the other hand, an error is also reported if no
configuration exists for an instance variable. In order to receive a list of all necessary
configuration variables, the "All Instance Paths" menu item in the 'Insert' menu can be
used.
Example for a Variable Configuration
Assume that the following definition for a function block is given in a program:
PROGRAM PLC_PRG
VAR
Hugo: locio;
Otto: locio;
END_VAR
Then a corrected variable configuration would look this way:
VAR_CONFIG
PLC_PRG.Hugo.loci AT %IX1.0 : BOOL;
PLC_PRG.Hugo.loco AT %QX0.0 : BOOL;
PLC_PRG.Otto.loci AT %IX1.0 : BOOL;
PLC_PRG.Otto.loco AT %QX0.3 : BOOL;
END_VAR
'Insert' 'All Instance Paths'
With this command a VAR_CONFIG - END_VAR-block is generated that contains all of
the instance paths available in the project. Declarations already on hand do not need
to be reinserted in order to contain addresses already in existence. This menu item can
be found in the window for configuration of variables if the project is compiled
('Project' 'Rebuild All').