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

Lenze · ApplicationTemplate · 1.3 EN - 04/2013
73
Architecture: The ApplicationTemplate in detail
The AppChannelData structure(ACD)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.2 The AppChannelData structure(ACD)
If required, the data structure of the MACD_sc type module name can be assigned within the desired
machine module (MFB).
The data structure must inherit the L_EATP_ACD_Base contained in the
L_EATP_ApplicationTemplate library.  The L_EATP_ApplicationTemplate library ( 110)
• The MACD_scModule1 structure defines the diCounter variable of the DINT data type.
[9-5] Configuration of the ACD structure with an inherited L_EATP_ACD_Base structure
• The MACD_sc<Module name> can be individually extended by the data types required.
• By the inherited structure, specific control and status bits are provided in the ACD structure.
• In the structure, the L_EATP_CriticalSection block which ensures a consistent data exchange is
instanced (if the FB is used correctly).
More information about the L_EATP_ACD_Base structure:  L_EATP_ACD_Base ( 127)
9.2.1 Declaring/recording the ACD structure in the MFB
In order to be able to use the ACD structure in the module applications (MAPs) of an MFB and its
master, the instance of the ACD structure has to be declared locally in the MFB.
[9-6] Declaration of the ACD structure in the MFB_Module1
The ACD structure is recorded in the program part of the MFB; by this, safety mechanisms are
activated.
• The instance name and size of the structure are to be transferred to the RegisterACD() method.
• The structure is to be newly recorded during every cycle. (A missing recording triggers an
infrastructure error.)