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

Working with the ApplicationTemplate PackML
Creating module applications
54
Lenze · ApplicationTemplate PackML · 1.0 EN - 05/2014
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
• The FB name (previously: MAP_Module1_App1): MAP_Module1_App2
The module application has now been inserted.
The module application inserted is to be declared in the MFB_Module1 function block:
8.11.1 Programming with the module application
In order to structure the subfunctions of a module applications, the actions contained in the
ApplicationTemplate have to be used.

Tip!
For programming, use the actions and methods that are contained in the
ApplicationTemplate PackML.
 State machine in detail ( 65)
 Alarm handling (error handling) ( 76)
 The AppChannelData structure(ACD) ( 60)
• The actions are contained in each mode.
• The state machine can be individually
programmed within each mode. This
serves to influence the behaviour of each
state separately.
• An individually programmed state
machine/a mode only has an impact
within the respective module application,
example: ModApp1/MAP 1.
• The other module applications can query/
changeover the current state of mode/
state machine but do not have any impact.