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

Structuring the automation system: Standard procedure
Structuring within a machine module: Assigning MAP subfunction to the tasks
28
Lenze · ApplicationTemplate PackML · 1.0 EN - 05/2014
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
5.2 Structuring within a machine module: Assigning MAP subfunction to the tasks
In order to create a clearly arranged module application, it is advisable to divide the module
applications (MAPs) into subfunctions and to structure them correspondingly.
• Each machine module contains three module applications MAP 1-3 which can be assigned to
tasks differently prioritised.
• Task and module application are assigned in the A11_ModuleAppCalls folder. The
assignment can be made by right-clicking the folder: With command Create Task Call .
 Assigning the module application (ModApp) to the task ( 43)
In a first step, the functions are to be assigned to the individual tasks. The ApplicationTemplate
PackML supports multitasking with three tasks. More information can be found under:
 Multitasking ( 82)
Predefined tasks
One module application can be used per task.
• Task and module application are assigned in the A11_ModuleAppCalls folder.
• The MAC_Task_High program part for instance calls all module applications which are to
pass through a high priority task Task_High.
Task/priority Standard value To be used for... (example)
"High"
HighPriority
2 ms Execution of Motion functions
"Mid"
MidPriority
6 ms Conversion for an external visualization
"Free"
Unsolicited
Unsolicited Communicating via NRT Ethernet