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

Architecture: The ApplicationTemplate in detail
Default coupling
84
Lenze · ApplicationTemplate · 1.3 EN - 04/2013
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
• Individual programming of the module application is not required.
Rules defined by the standard mechanism:
1. If at least one slave module or the machine module itself shows an error status ("Quick stop",
"Fault", or "System fault"), the machine module sets the actual state to "Quick stop". All slaves
receive the request to adopt the "Quick stop" state.
Example:
A machine module M features four subordinated slaves: S1, S2, S3, S4.
• S2 goes to the "ErrorState FAULT" error status; S4 to "Quick stop".
By this,
• ...M changes to the "Quick stop" status,
• ...S1, S2, S3 receive the request to change to the "Quick stop" status (S4 already is in the "Quick
stop" status)
2. If no error is pending, the machine module forwards the module's intrinsic status request to all
slaves. The module's intrinsic actual state transition only takes place when all slaves have
changed to the status.
Example:
A machine module M features four subordinated slaves: S1, S2, S3, S4.
• By the higher-level master module, M receives the request to change from the "Ready" status
to the "Automatic" status.
• Machine module M forwards the state transition to all slaves.
• If all slaves (S1 ... S4) have completed the state transition and the module's intrinsic
conditions for the state transition have been met, M changes to the "Automatic" status.