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

Lenze · ApplicationTemplate · 1.3 EN - 04/2013
83
Architecture: The ApplicationTemplate in detail
Default coupling
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Example
The MachineModuleTree has the following exemplary structure:
[9-16] MMT view in the ApplicationTemplateCounter with two lower-level machine modules
Example
The MFB_MachineControl machine control module sets the "Automatic" state for the lower-level
machine modules:
An overview of all BaseChannel methods can be found under: Method overview -
ApplicationTemplate ( 131)
9.4 Default coupling
The state machine in the ApplicationTemplate is provided with a standard response. In this section
you'll be provided with information about how subordinated (slave) machine modules are to be
decoupled from the standard response.
• The higher-level machine module specifies setpoint states for the lower-level slaves and, in
doing this, checks the current actual states of the slaves.
• If a subordinated slave module detects an error...
• ...this module responds with an error response (according to the error response
programmed), and
• ...forwards this information to the higher-level machine module which then changes to the
"Quick stop" status.
• If there is another higher-level machine module, the information is forwarded to the top level
and this module correspondingly responds with the "Quick stop" status. The top machine
module then transfers the information back to its subordinated machine modules, which
change to the "Quick stop" status.
This standard coupling can be deactivated by corresponding programming. This requires that the
user defines the error behaviour by programming.
9.4.1 Standard mechanisms of the ApplicationTemplate
• The standard behaviour is active if the module in the machine module tree (MMT) is provided
with at least one subordinated slave module.
• The standard behaviour can be controlled by means of the corresponding methods ("TRUE" is
the initial value):
baseChannelSetNominalState(MM_Address := L_EATP_CONST.OWNID, eState :=
L_EATP_SMStates.Automatic)
SMDisableDefaultCouplingMaster(TRUE)
SMDisableDefaultCouplingSlave (TRUE)