mapp Services V5.16
This mapp component's task is to establish an interface between the alarms and the HMI application. An MpAlarmBasic instance must be active. The MpLink being used for MpAlarmBasicUI determines where the information (alarms) comes from. This mapp component should only be enabled ("Active" = TRUE) if the component for which the alarms should be displayed is active. In addition, MpAlarmBasic must be active in order to use MpAlarmBasicUI. Example: The alarms of an axis should be displayed using MpAlarmBasicUI. The order in which the mapp components should be enabled is as follows:
•MpAlarmBasic (own MpLink)
•MpAxisBasic (own MpLink)
•MpAlarmBasicUI (MpLink of axis)
If only user alarms from MpAlarmBasic should be collected and displayed via the HMI application using MpAlarmBasicUI, then the same mapp Link is specified for both MpAlarmBasicUI and MpAlarmBasic. In order to have user alarms displayed, it is important that only one instance of MpAlarmBasicUI is used.
Mode
Input "Mode" is used to decide which alarms should be filtered and prepared for the HMI application.
•mpALARM_BASIC_UI_MODE_MAPP: The default alarms of a mapp component
•mpALARM_BASIC_UI_MODE_USER: Only user-defined alarms (only used if component MpAlarmBasicUI is directly connected to component MpAlarmBasicUI)
•mpALARM_BASIC_UI_MODE_ALL: All alarms (standard components and user alarms)
UISetup
The size of the alarm and acknowledgment arrays is specified in this structure. The size of the two arrays must be defined in the application (depends on the number of alarms of the component connected to MpAlarmBasicUI).
If this is connected to MpAlarmBasic, then the size of the array must be defined in relation to input "Mode".
•mpALARM_BASIC_UI_MODE_MAPP: The size of the array is the result of adding the default alarms of all components that are active (see "Complete alarm list" in the WebXs - Without user alarms).
•mpALARM_BASIC_UI_MODE_USER: The size of the array is the result of the maximum number of user alarms [0..99].
•mpALARM_BASIC_UI_MODE_ALL: The size of the array is the result of adding all standard component alarms and the number of user alarms (see "Complete alarm list" in the WebXs).
If MpAlarmBasicUI is connected with another mapp component, then the size of the array is determined by the number of default alarms of this component.
Parameters "AddInfo" and "AddInfoStringSize" are also available in structure "UISetup". These parameters are used solely to enable user alarms. If a user alarm is enabled with the MpAlarmSet function, then an additional informational text can be appended to the alarm.
•AddInfo: Passed as a STRING array. The size of the array is the result of the maximum number of user alarms [0..99].
•AddInfoStringSize: Length of the string
After a user alarm is enabled, the additional information is entered in this STRING array and can be used as a text snippet for the HMI application, for example.
Predefined UIConnect structures
Two predefined structures are available via MpAlarm that already include parameters "AlarmImage", "AcknowledgeImage" and "AddInfo":
•MpAlarmBasicUIConnect20Type: Structure for 20 alarms
•MpAlarmBasicUIConnect100Type: Structure for 100 alarms (perfect for MpAlarmBasic user alarms)
This means that MpAlarmBasicUIConnect20Type can be used for MpAxisBasic, for example. You simply have to pass the address of the individual parameters ("AlarmImage", "AcknowledgeImage" and "AddInfo") to the UISetup structure of MpAlarmBasicUI.
A variable is created for the alarms of an axis. The predefined type is used. |
The variable is connected to the UISetup structure via MpAlarmBasicUI. |
Text snippets are created for all alarms. |
Alarm image, acknowledgment image and text snippets are connected with the VC4 alarm group. |
Centralized or decentralized alarm management
All alarms are collected by MpAlarmBasic. The same MpLink is used for MpAlarmBasicUI as for MpAlarm. This creates a list of all alarms that can be mapped using an alarm group in VC4. In this way, the alarms are managed and displayed in one location. More information about how alarms are arranged in this list is provided in section Alarm assignment.
Decentralized
Decentralized alarm management is also possible. This means that the alarms are still managed centrally by MpAlarmBasic, but that their display is handled decentrally. An alarm group is created in VC4 for each mapp component whose alarms should be displayed. Alarms are therefore assigned to the respective component, and a different priority can be defined per component / alarm group.
Mixing centralized and decentralized alarm management is not possible, i.e. each alarm is only permitted to appear in one alarm image or acknowledgment image.
Example (Alarm handling for MpDelta3Axis):
If the default alarms of a component should be integrated into the HMI application's alarm system, then an MpAlarmBasicUI instance must be appended to this component (same MpLink). An alarm group with the standard component alarms must be created in the HMI application for each component to be integrated in the alarm system.
|
|
|
Standard alarms for the MpDelta3Axis component (can be seen in the Automation Studio configuration of the delta robot or in the WebXs):
|
|
|
|
|
|
Creating an alarm group in the HMI application:
|
|
|
Configuring MpAlarmBasicUI:
MpLink: MpLink of component MpDelta3Axis
Mode: mpALARM_BASIC_UI_MODE_MAPP
UISetup:
•AlarmImage[0..6]
•AcknowledgeImage[0..6]
•ImageSize = 7