mapp Services V5.16
Command "Abort" is enabled on function block MpPackMLModule. Command "Abort" can be triggered in the machine unit if the emergency stop switch has been enabled.
By default, command "Abort" is automatically forwarded to the module above and all modules below it. This applies to the complete hierarchy, so command "Abort" can be issued anywhere and received by all modules.
For information about which module triggered an "Abort", see process variable "Aborted by module" in the MpPackMLCore configuration.
If multiple modules trigger command "Abort", the signal that was triggered in the task with the highest priority wins. The "Aborted" command that occurred first writes the module information in process variable "Aborted by module". If further "Aborted" commands occur, the information on the process variable will not be updated. The information on the process variable is not updated until "Abort" in the module is no longer valid or has been reset and a new "Abort" command has been triggered.
If the respective module contains modules that are still below it, the module that is at the bottom of the hierarchy is displayed.
In the following example, the machine unit is currently in state "Execute":
If a problem occurs in a module and causes the currently executed state in the machine unit to be aborted, command "Abort" can be triggered in the module. The module will then change to state "Aborting".
The complete machine now changes to state "Aborting".
The command is sent from the respective module to the higher-level module. After the main module has received the command, it sends command "Abort" to all other subordinate modules:
All modules are now in state "Aborting". In order to change to state "Aborted", command "StateComplete" must be started on the respective modules.
The machine has now been successfully stopped.
