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

Architecture: The ApplicationTemplate PackML in detail
The AppChannelData structure(ACD)
60
Lenze · ApplicationTemplate PackML · 1.0 EN - 05/2014
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
[9-6] Example: Access to all slave modules, without the own machine module.
• Writing of a UserTag element into the own machine module and all slave machine
modules.
[9-7] Example: Writing of a UserTag into all slave modules, including the own module.
9.1.3 Accessing structures of other machine modules
The global machine module structures are instanced in the A55_VarLists folder.
• Like this, the structures and machine modules of the ApplicationTemplate PackML can be
reused.
• The structure variables of an optional machine module can be used from another machine
module.
• In order to be able to use the variables of a global structure of machine module 1 (example:
MM_Module1) in another machine application of machine module 2 (example: MM_Module2),
the following program call is required:
[9-8] Sample program: Accessing the MM_Vis structure of module 1.
9.2 The AppChannelData structure(ACD)
If required, the data structure of MACD_scModulename type can be assigned in the desired machine
module (MFB). The data structure inherit the L_EATP_ACD_Base structure contained in the
L_EATP_ApplicationTemplate PackML library.  Die Bibliothek L_EATP_ApplicationTemplate ( 89)
• The MACD_scModule1 structure defines the diCounter variable of the DINT data type.
diPiecesModul1 := MM_Vis.scModule1;