2 the "disabledefaultcouplingmaster" function, The "disabledefaultcouplingmaster" function, Is activated – Lenze PLC Designer ApplicationTemplate (PLC Designer R3-x) User Manual
Page 85: Architecture: the applicationtemplate in detail

Lenze · ApplicationTemplate · 1.3 EN - 04/2013
85
Architecture: The ApplicationTemplate in detail
Default coupling
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.4.2
The "DisableDefaultCouplingMaster" function
The "DisableDefaultCouplingMaster" function (during operation) decouples the state machine of
the higher-level master module from the associated slave modules.
• This function is required if...
• ...specific machine parts / machine modules are to be decoupled specifically (during
operation).
• ...a different status is required for the decoupled machine parts / machine modules than for
the other machine modules.
• Due to the addressed method access of the master, the state machine of the slave can be
influenced. Alternatively, the state machine can be programmed within the slave. The error
handling of the slave does not affect the state machine of the master.
Example
[9-17] Example of a machine structure with three hierarchy levels.
The M1.2 master decouples its state machine from the state machines of the subordinated slaves
M1.2.1 and M1.2.2. This means that the setpoint states for the subordinated slave modules M1.2.1
and M1.2.2 have to be programmed manually in the M1.2 machine module.
• The SMDisableDefaultCouplingMaster(TRUE) method call from a module application (MAP)
activates the function.
• The SMDisableDefaultCouplingMaster(FALSE) method call deactivates the function.
• The method call has no impact on the connection to the ACD structure of the respective
machine module.
• Optionally, the baseChannelSetErrorQuit method forwards the error acknowledgement to the
slaves. The L_EATP_GVL.xDisableGlobalErrorReset variable serves to activate / deactivate a
global error reset:
• The master of the respective state machine can read out the status of a decoupled module (via
the corresponding methods).
• The use of this mechanism is only advisable if the module is provided with at least one
subordinated slave module.
[9-18] Sample program: Deactivating "DefaultCouplingMaster"
: "Disable" = "TRUE"
L_EATP_GVL.xDisableGlobalErrorReset := FALSE; //default setting
SMDisableDefaultCouplingMaster(xValue := TRUE);