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

Lenze · PLC Designer | Migration of V2.x projects · 1.2 EN - 02/2013
17
Programming languages
AS / SFC
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
6.5 AS / SFC
6.5.1 Step variables
Step variables explicitly declared by the user...
• must be declared locally in the SFC.
• must not be declared as VAR_INPUT, VAR_OUTPUT or VAR_INOUT since the calls cannot be ad-
apted automatically.
Steps do not use any boolean variables for managing the internal states in the »PLC Designer« V3.x
but structures of SFCStepType type.
6.5.2 Identifier
The following must not begin with an underscore...
• IEC actions in the tree
• boolean variables that are called in an IEC association list.
• the names of programmed transitions.
In the »PLC Designer« V3.x, the implicit variables (created for actions) get an underscore as prefix.
An invalid identifier with a double underscore would be generated.
6.6 CFC
6.6.1 Big blocks
The graphical presentation of big blocks is insufficient after the import into »PLC Designer« (e.g.,
graphical fields may overlap).
6.6.2 Comments
When a multiline comment is imported, only the first line is displayed.
6.6.3 Macros
Macros cannot be imported into the »PLC Designer« V3.