Lenze PLC Designer Migration PLC Designer (R2-x)-PLC Designer (R3-x) - Manual (Page 12)

General information
»PLC Designer« - preparing internal visualisation
12
Lenze · PLC Designer | Migration of V2.x projects · 1.2 EN - 02/2013
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
5.2 »PLC Designer« - preparing internal visualisation
• Visualisation: All variables in the visualisation must be declared. In the »PLC Designer« V2, a
warning is displayed, in the »PLC Designer« V3, an error is displayed.
• Remedy: Check visualisation: Remove non-declared variables.
"Single" wildcards
• The following wildcards can be imported error-free in the »PLC Designer« V3:
$Var$.StructName.Varname
ArrName[$Index$]
"Double" wildcards
• The following wildcards cannot be imported in the »PLC Designer« V3:
$Instance$.$VarName$...
$Achse$$Spur$...
Problematic wildcards
1. The wildcard occurs in a fixed text:
Text: $axle$-AchselocalVar : STRING;
Text: %s-Achse TextVariable: localVar
• Remedy:
localVar : STRING;
Text: %s-axis
TextVariable: localVar
2. The wildcard describes only a part of a variable name:
achse$achse$spur$spur$.fActPosition
• Remedy: Only one wildcard is defined for the achse$achse$spur$spur$ wildcard:
achse_spur : MyFunctionBlock;
• Then the corresponding instance of the function block is passed directly:
achse_spur := PLC_PRG.achse1Spur2;
3. The wildcard is replaced by an expression:
$Expression$ ?? PLC_PRG.var1 + PLC_PRG.var2
• Remedy: The expression must be transmitted to an auxiliary variable. This auxiliary variable
is then transmitted as an instance.