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

Lenze · ApplicationTemplate PackML · 1.0 EN - 05/2014
71
Architecture: The ApplicationTemplate PackML in detail
Standard coupling of the machine modules
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.4 Standard coupling of the machine modules
The state machine in the ApplicationTemplate PackML is provided with a standard behaviour. This
section describes how a lower-level slave machine module can be decoupled from the master
module if required.
• 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 lower-level slave module detects a triggered alarm...
• ...this module responds with an alarm response (according to the alarm response
programmed), and
• ...forwards this information to the higher-level machine module.
• If there is another higher-level machine module, the information is forwarded to the top
level.
The standard coupling of the machine modules in the ApplicationTemplate PackMLcan be changed
by appropriate programming.
9.4.1 Predefined standard mechanism of the state machine
In the ApplicationTemplate PackML the top master machine module controls/switches by default
the connected lower-level slave machine modules with their state machines and operating modes.
• Based on the master module on the top level, the state machine or the operating mode is
changed over by switching the module of the lowest level first. Only if all slave modules have
changed to the requested state, the master module changes to this state as well.
SUSPENDING Active green This state has to be used if it is not possible with the EXTERNAL process
state to let the machine continue the production. This means that the
upstream or downstream machine in a line leaves the EXECUTE state.
Possible triggers are blockades or supply shortfalls in the machine.
• The SUSPENDING state could be triggered by a local sensor in the
machine or by a external control system. Usually, the machine is
stopped in a controlled manner in this state and then changes to the
SUSPENDED state.
• In order to restart the machine in a controlled manner after the
SUSPENDED state, all relevant process setpoints/return states of the
procedures have to be saved that are available while the SUSPEND
command is triggered.
UNHOLDING Active green This state is reached as described for the HOLDING state. In this state,
the machine is stopped either by a complete stop or by a continuous "dry
running".
• As soon as the INTERNAL machine state changes/the operator
triggers the UNHOLD command, the machine changes to the
UNHOLDING state.
• Usually, the Performance Management/OEE system considers the
SUSPENDED state (blockade/supply shortfall) as "available".
UNSUSPENDING Active green This state is reached as described for the SUSPENDED state. The
UNSUSPENDED state can be reached as soon as the external state of the
machine has normalised.
• The UNSUSPENDING State initiates all necessary actions/sequences
in order that the machine can change to the EXECUTE state.
• For a restart of the machine, the data has to be restored that has been
previously saved while the SUSPEND command was triggered (see
SUSPENDING state).
State Category Colour Description