Lenze ApplicationTemplate PackML (PLC Designer R3-x) - Manual (Page 75)

Lenze · ApplicationTemplate PackML · 1.0 EN - 05/2014
75
Architecture: The ApplicationTemplate PackML in detail
Where can the response of a machine module be programmed?
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.7 Where can the response of a machine module be programmed?
The individual PLC application has to be programmed in the state machines of the single operating
modes.  Structuring within a machine module: Assigning MAP subfunction to the tasks ( 28)
9.7.1 State transition (state entry/state exit)
Every change of a status-related action (within an action or from an action) sets a specific flag for a
task cycle to "TRUE".
• xStateEntry: The status-related action sets this flag to "TRUE" during the entry for one task cycle.
• xStateExit: The status-related action sets this flag to "TRUE" during the exit for one task cycle.
[9-27] Predefined states: Example program frame with xStateEntry/xStateExit

Note!
The following procedure is to be taken into consideration for task timing-related
program commands:
• At a state transition, actions are assigned to the individual task cycles in the same way
as for the sequential function chart AS.
• In case of "Idle""Execute" state transition the task cycle...
...first passes the Idle action with set xStateExit flag.
...and then the Execute action with set xStateEntry flag.