<< Click to Display Table of Contents >> Navigation: »No topics above this level« MpPackMLModule configuration |
mapp Services V5.16
For information about how the configuration can be adjusted at runtime, see here in section "Changing the configuration at runtime".
•Show advanced parameter
Name |
||||||||
Module |
||||||||
Name |
||||||||
Has parent |
||||||||
Parent module |
||||||||
Module activation |
||||||||
Activation PV |
||||||||
Unit |
||||||||
Module activation |
||||||||
Activation PV |
||||||||
Auditing |
||||||||
Auditing module state description |
A unique name must be specified for the module under "Name".
Creating a hierarchy:
"Has parent" is used to define whether or not the module has a higher-level module.
If "Yes" is specified, the module has a higher-level module. The higher-level module must be specified under "Parent module". The MpLink from a MpPackMLModule configuration is used.
If "No" is specified, there is no higher-level module. This option is used for the main module. The main module is linked to the machine unit. This means that the MpLink from a MpPackMLCore configuration is specified. For more information, see section Creating a hierarchy.
Enabling the modules:
"Module activation" determines the enabling condition. In addition to the enabling condition, command "StateComplete" is required on the module. For more information about module enabling and its effects, see here. There are the following enabling conditions:
•Automatic: The module is enabled automatically.
•By parent: The module is enabled by the higher-level module. As soon as it is active, the subordinate module is enabled.
•By PV: A module is enabled via a defined PV ("Activation PV").
Recording events:
Whether events in the mapp Audit module should be recorded or not can be defined under "Auditing". The (sub-)state information can be recorded.
For more information, see section Auditing in mapp PackML.