Packaging Machine State

The “Packaging Machine State” function blocks have a common interface to the existing “PackML Machine State Model” versions.

It is expected that application-specific logic such as state transitions are programmed in external function blocks and that the “Packaging Machine State” function block takes over the central logic of the state machine and the state display. For that reason there is a recommendation for this function block with regard to how it can be combined with other logic.

The state transition in a machine application is always application-specific. To simplify standardization, it is best to implement methods linked to the PackML State Machine V3 in your function blocks. To do this, you can use the interfaces provided within this library and then program the methods for the specific application. The “acting” methods acquire application-specific signals and represent the transition logic to adjacent states (see PackML state model below). The "Waiting" methods provide feedback to the higher-level, higher-order PackML State Machine V3, enabling a standard state machine and state message. The methods contain the machine execution code and the application-specific transition logic.

The available methods are listed below and are programmed in a way that preserves the integrity and functionality of the PackML state machine.

Names of the "PackML State Machine V3" Acting methods:

• M_Starting
• M_Completing
• M_Resetting
• M_Holding
• M_UnHolding
• M_Suspending
• M_UnSuspending
• M_Clearing
• M_Stopping
• M_Aborting
• M_Execute

Names of the "PackML State Machine V3" Waiting methods:

• M_Completed
• M_Idle
• M_Held
• M_Suspended
• M_Stopped
• M_Aborted