States and Modes
The following table shows a brief description of individual machine states:
PackML States |
Description |
State Type |
---|---|---|
STOPPED |
In this state, the machine is powered and stationary. All communications with other systems are functioning (if applicable). |
Wait |
STARTING |
In this state, the machine is starting as a result of a START type command (local or remote). After completing this command, the machine will begin to EXECUTE. |
Acting |
IDLE |
This state maintains the machine conditions which were achieved during the RESETTING state. |
Wait |
SUSPENDING |
This state is a result of a command change from the EXECUTE state. This state is typically required prior to the SUSPENDED wait state, and prepares the machine by stopping active processes prior to the SUSPEND state. |
Acting |
SUSPENDED |
In this state, the machine may be running at the relevant set-point speed, and no product is being produced. This state is the result of an upstream or downstream machine condition or other external request, and it differs from HELD in that HELD is typically a result of a local operator request. |
Wait |
UNSUSPENDING |
This state is a result of a request from the SUSPENDED state to return to the EXECUTE state. The actions of this state may include: ramping up speeds, turning on vacuums, or re-engaging clutches. This state prepares the machine for the EXECUTE state. |
Acting |
EXECUTE |
In this state the machine is processing materials. The action depends on the current mode. If the machine is in the Production mode, then EXECUTE refers to the action of processing discrete parts on a continuous basis. Dual |
|
STOPPING |
This state executes the logic which brings the machine to a controlled and safe stop. |
Acting |
ABORTING |
In this state, the machine comes to a rapid, controlled, safe stop. Pressing the Emergency Stop button will cause the safety system to stop the machine, and it provides a signal to initiate the ABORTING state. |
Acting |
ABORTED |
This state maintains machine status information relevant to the ABORT condition. The STOP command will force transition to the STOPPED state. The ABORTED state can be entered at any time in response to the ABORT command or on the occurrence of a machine fault. |
Wait |
HOLDING |
When the machine is in the EXECUTE state, the HOLD command starts the HOLDING logic, which brings the machine to a controlled stop or to a state that represents HELD for the particular machine mode. |
Acting |
HELD |
In this state, the operator can temporarily hold the machine's operation while material blockages are cleared, or stop throughput while a downstream problem is resolved. |
Wait |
UNHOLDING |
In this state, the machine prepares to re-enter the EXECUTE state. The UNHOLDING state is typically a response to an operator command to resume EXECUTE state. |
Acting |
COMPLETING |
In this state, normal operation has run to completion. This state is typically an automatic response from the EXECUTE state. |
Acting |
COMPLETE |
In this state, the machine has finished the COMPLETING state and is waiting for a STOP command. |
Wait |
RESETTING |
In this state, the machine will typically generate an audible alert and energize components, awaiting a START command. This state is the result of a RESET command from the STOPPED state. |
Acting |
CLEARING |
In this state, the machine is clearing faults that may have occurred when ABORTING, and are present in the ABORTED state before proceeding to the STOPPED state. |
Acting |
An example state transition matrix is shown below.
NOTE: This image is not translated intentionally