Decentralized user alarm management

<< Click to Display Table of Contents >>

Navigation:  »No topics above this level«

Decentralized user alarm management

mapp Services V5.16

Requirement

A machine consists of 100 conveyor belts. Each conveyor belt is controlled by an MpAxisBasic component. The transport belts are synchronized by the machine's application program.

Each conveyor belt should have 2 additional alarms along with the MpAxisBasic standard alarms:

"Motor temperature above warning limit"

"Conveyor belt not synchronized"

The alarms from all conveyor belts should be collected and displayed in the HMI application using VC4 alarm management for current and past alarms. The alarms for the individual conveyor belts must also each be represented in their own VC alarm group. A clear division of alarms for each conveyor belt should be achieved with this decentralized approach.

Solution

Component list

MpAxisBasic (own MpLink): Controls the conveyor belts

MpAlarmBasic (own MpLink): Centralized alarm management

MpAlarmBasicUI (MpLink from MpAxisBasic): Connects alarms decentrally to Visual Components using multiple alarm images. For "decentralized" alarm management connected to the MpLink from MpAxisBasic so that each mapp component has its own alarm group in VC4.

MpAlarmSet (MpLink from MpAxisBasic): Sets a user alarm

MpAlarmRegUser (MpLink from MpAxisBasic): Registration of additional alarms for a mapp component

Connection diagram

mpalarmusecase_3

 

 

Using the mapp components

Each instance of MpAlarmBasicUI is connected via the MpLink to the respective MpAxisBasic component. In mpALARM_UI_MODE_ALL mode, therefore, the mapp alarms and user alarms will be included in the same alarm image. The user alarms will always be attached after the default alarms. By default, each mapp component has enough space for its own alarms. In order to add user alarms, they must be registered using MpAlarmRegUser. This means the alarms can already be configured in the configuration, but enough space must be allotted for the new alarms using MpAlarmRegUser.

The properties of the additional user alarms must be specified in the MpAxisBasic configuration:

mpalarmusecase_3_reguser_config

 

 

In Visual Components, an alarm group must be created with the MpAxisBasic default alarms and the additional user alarms for each conveyor belt:

mpalarmusecase_3_reguser_alarmgroups

 

 

The size of the alarm group is a result of the number of alarms from the mapp component connected to MpAlarmBasicUI. In this case:

 

ImageSize = MpAxisBasic alarms + User alarms

 

 

17 alarms = 15 alarms + 2 alarms

 

The alarm group must have 17 elements, just like the size of the alarm and acknowledgment image must be 17. When using MpAlarm decentrally, only the alarms of the mapp component connected to MpAlarmBasicUI are taken into account.