Lenze PLC Designer ApplicationTemplate (PLC Designer R3-x) - Manual (Page 27)

Lenze · ApplicationTemplate · 1.3 EN - 04/2013
27
Structuring the automation system: Standard procedure
Structuring within a machine module
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Recommendation - which function is to be called in which task?
5.2.2 Programming recommendations for structuring
The following table presents the structuring possibilities of the ApplicationTemplate as a decision
recommendation:
Which features of the ApplicationTemplate should I use and for what purpose?
Task/priority Function (example)
"High"
HighPriority
Execution of Motion functions
"Mid"
MidPriority
Conversion for an external visualization
"Free"
Unsolicited
NRT Ethernet communication
What do you want to do? FB Action Method More suitable
is...
Work with local variables z Local variables are to be
declared in the FB
assigned.
Local variables (if
possible) are to be
declared in the FB
assigned.
-
Debugging z z No local variables Action, FB
Reuse:
In the event of an error (when
creating the user software), error
handling can be executed at one
point.
z - To a limited extent - for
instance if FBs are
integrated in the
method.
Example: "Statemachine"
in the
ApplicationTemplate
FB
Instancing z - - Action,
method
Access all data types z z z Action, FB,
method