Basic principle

mapp Services V5.16

This section explains the basic principle of mapp PackML.

mapp PackML can be used in two different ways. In standalone and synchronized mode.

The mode is selected via the MpPackMLCore configuration under "Unit operation".

packml_unitoperationmode

All functions/function blocks of mapp PackML are listed in this section together with the information about whether they can be used in synchronized mode or standalone mode.

Supported starting with	Name	Description	Mode
5.0.0	MpPackMLAbort	This function triggers a PackML ABORT command.	Standalone, synchronized
5.0.0	MpPackMLBasicUI	This function block creates a connection to Visual Components 4 HMI applications in order to display and check the mode and state diagram.	Standalone
5.0.0	MpPackMLCore	This function block forms the core of PackML logic and can be used to manage all modes.	Standalone
5.0.0	MpPackMLMode	This function block manages a PackML mode.	Standalone
5.0.0	MpPackMLModeCurrent	This function returns the current mode as an ID.	Standalone, synchronized
5.0.0	MpPackMLModeIsActive	This function indicates whether the selected mode is active.	Standalone, synchronized
5.0.0	MpPackMLStateComplete	This function triggers a PackML STATE COMPLETE command.	Standalone, synchronized
5.0.0	MpPackMLStateCurrent	This function returns the current state.	Standalone, synchronized
5.0.0	MpPackMLStateIsActive	This function indicates whether the selected state is active.	Standalone, synchronized
5.0.0	MpPackMLStatisticsUI	This function block creates a connection to Visual Components 4 HMI applications in order to visualize statistical data regarding the usage of modes and states.	Standalone
5.10.0	MpPackMLModule	MpPackMLModule can be used to control a module of the machine.	Synchronized
5.10.0	MpPackMLChangeMode	Function MpPackMLChangeMode can be used to change the mode of the machine unit. If the function is called, all modules in the specified hierarchy change mode.	Synchronized
5.15.0	MpPackMLModeChangeIsAllowed	Function MpPackMLModeChangeIsAllowed can be used to check whether it is permitted to change the mode of the machine unit.	Synchronized

Synchronized

When selecting the synchronized mode, the machine complies with the OMAC PackML ISA-88 model. The machine is divided into modules. Each module complies with the OMAC PackML state diagram:

logo_getting_started

For information about how to use synchronized mode, see "Getting started" tutorial mapp PackML in synchronized mode.

packml_synchronizedmode2

For the synchronized mode, the modules are hierarchically structured. Thus the modules are linked to each other and exchange commands and information. Commands can be started and thus state changes can be implemented for the machine.

As a result, the entire machine application can be developed according to the OMAC PackML standard. The following information can thus be made available quickly and easily:

•The type and state of the modules that are available in the machine

•Whether there are problems with passing on products from one module to the next

•Which module must currently be waited for after a state change

•Which module triggered an abort command and the state it was in at the time

The points mentioned above are explained step by step in section Synchronized mode.

Standalone

If mapp PackML works in mode "Standalone", the entire machine is represented by a PackML state diagram. Since the machine is not divided into different modules, there is only one module to work with.

logo_getting_started

For information about how mapp PackML can be used in standalone mode, see "Getting started" tutorial Implementing the OMAC PackML standard.

packml_standalonemode

The aim of mode "Standalone" is to display the machine in a line via the PackML state diagram. The state of the line is thus displayed uniformly. The application only complies with the PackML standard on the highest level, whereas the rest of the application is compiled arbitrarily. Mode "Standalone" can also be used for upgrading brownfield machines to display them via the PackML state diagram.