mapp Services V5.16
Events for these components can be recorded using MpAudit. For more information about how to create an entry, see section Defining the event text.
The following events can occur for these mapp components:
This section lists the different OMAC PackML events:
OMAC PackML mode change
This event type allows a MpPackML mode change to be tracked. The event type can be used in synchronized mode and standalone mode.
Option "Auditing" must be enabled in the MpPackMLCore configuration in order to record events:
Event ID 64 |
Components |
Events |
|
ev |
Event ID |
idx |
Returns the index of the currently generated event. The value is incremented on each new event. The first generated event in the event list thus has value 1; the 50th event has index 50 and the 100th has index 100. |
old |
Old PackML mode |
new |
New PackML mode |
resp |
Source of the PackML mode or state change (e.g. "MpPackMLBasicUI", "MpPackMLMode", "PackML tag structure") |
state |
Current state |
op |
Name of the user who was logged in when the event occurred |
Table: MpPackML mode change
For information about how to specify the event text, see section Using the new format.
Example of the new format:
•"PackML mode: Old: [&old], New: [&new]" evaluated: "PackML mode: Old: Manual, New: Production", which means that the PackML mode changed from "Manual" to "Production".
Example of the old format:
•"PackML mode: Old: [%old], New: [%new]" evaluated: "PackML mode: Old: Manual, New: Production", which means that the PackML mode changed from "Manual" to "Production".
OMAC PackML state change
This event type allows a MpPackML state change to be tracked. The event type can be used in synchronized mode and standalone mode.
Option "Auditing" must be enabled in the MpPackMLCore configuration in order to record events:
Event ID 65 |
Components |
Events |
|
ev |
Event ID |
idx |
Returns the index of the currently generated event. The value is incremented on each new event. The first generated event in the event list thus has value 1; the 50th event has index 50 and the 100th has index 100. |
old |
Old PackML state |
resp |
Source of the PackML mode or state change (e.g. "MpPackMLBasicUI", "MpPackMLMode", "PackML tag structure") If mapp PackML is used in synchronized mode, "resp" returns the module that triggered the state change. |
new |
New PackML state |
mode |
Currently active mode |
info |
This parameter can only be used in mode "Synchronous". Passes on the additional description of the current state of a module. |
op |
Name of the user who was logged in when the event occurred |
Table: MpPackML state change
For information about how to specify the event text, see section Using the new format.
Example of the new format:
•"Event: {&ev}, Old: {&old}, New: {&new}" evaluated: "Event: 65, Old: Idle, New: Starting", which means that the PackML state changed from "Idle" to "Starting".
Example of the old format:
•"Event: [%ev] Old: [%old], New: [%new]" evaluated: "Event: 65 Old: Idle, New: Starting", which means that the PackML state changed from "Idle" to "Starting".
OMAC PackML module change
This event type can only be used if mapp PackML is working in synchronized mode.
This event type can be used to determine whether state changes and substate changes in a module should be recorded.
Option "Auditing" must be enabled in the MpPackMLModule configuration in order to record events:
In addition, option "Auditing" must be enabled in the MpPackMLCore configuration!
If a module now triggers a state change, an "OMAC PackML state change" event is automatically triggered that contains the old and new state of the module.
Event ID 66 |
Components |
Events |
|
ev |
Event ID |
idx |
Returns the index of the currently generated event. The value is incremented on each new event. The first generated event in the event list thus has value 1; the 50th event has index 50 and the 100th has index 100. |
old |
Previous substate |
new |
New substate |
resp |
Name of the module |
info |
Specifies the additional description of the synchronous mode. Defined via "StateInfo" on MpPackMLModule. |
op |
Name of the user who was logged in when the event occurred |
Table: MpPackML substate change
For information about how to specify the event text, see section Using the new format.
Example of the new format:
•"Old substate: {&old}, New substate: {&new}, Module: {&resp}, Info: {&info}" evaluated: "Old substate: 2, New substate: 3, Module: Infeed, Info: Axis reference completed", which means that the substate on module "Infeed" has changed. The axis homing was completed.
Example of the old format:
•"Old substate: [%old], New substate: [%new], Module: [%resp], Info: [%info]" evaluated: "Old substate: 2", New substate: 3, Module: Infeed, Info: Axis reference completed", which means that the substate on module "Infeed" has changed. The axis homing was completed.