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

Working with the ApplicationTemplate
Creating module applications
64
Lenze · ApplicationTemplate · 1.3 EN - 04/2013
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
8.10.2 Frequently asked question: Connection between MFB and MAP
MFB_Module1 function block
The MachineModuleTree (MMT) maps the mechatronic structure of the automation system by
means of the MFB function blocks (MFB_Modulexx).
• Instancing of the MFB_Module1 must be executed in the MM_Dcl structure of the
A55_VarLists folder.
• Insert the instance in the desired position of the MMT.
[8-3] Example: Machine module tree in the ApplicationTemplateCounter
• A machine module encloses the module applications in the machine module.
• Therefore the module applications are to be declared within the machine module.
Instance the MAP_Module1_App1 module application with the following declaration line, so that
the instance can be called according to the task in the module application of ModuleAppCalls:
• The parentModule:= THIS^ instruction connects the App1 module application to the basic
functions of all machine modules (e.g. state machine, error handling, BaseChannel). That way,
the App1 module application can access the basic functions of the ApplicationTemplate.
• Assign the ACD structure manually.  The AppChannelData structure(ACD) ( 73)
[8-4] Example: App1
App1: MAP_Module1_App1 := (parentModule := THIS^);