<< Click to Display Table of Contents >> Navigation:  »No topics above this level« Centralized alarm management

mapp Services V5.16

Requirement

PET preforms are transported via conveyor belt through a furnace. Each of the conveyor belts is controlled with component MpAxisBasic. The application is responsible for regulating the temperature of the furnace. An alarm should be triggered if the temperature exceeds a certain value. Alarms for the axes and the alarm for overtemperature should be collected and displayed in the VC4-based HMI application.

For the sake of convenience, all alarms for this machine should be displayed in one VC4 alarm group, i.e. collected and displayed centrally.

Solution

•Component list

•MpAxisBasic (own MpLink): Controls the conveyor belts

•MpAlarmBasic (own MpLink): Centralized alarm management

•MpAlarmBasicUI (MpLink from MpAlarmBasic): Connects alarms centrally to Visual Components using an alarm image. Using the MpLink from MpAlarmBasic allows central alarm collection (with a certain mode) that is connected with an alarm group in VC4.

•MpAlarmSet (MpLink from MpAlarmBasic): Sets a user alarm

Connection diagram

Using the mapp components

The MpAlarmBasicUI component can be connected to the MpAlarmBasic component via the MpLink. 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 shown after the default alarms.

This means that an alarm group with all alarms must be created in Visual Components:

The size of the alarm group is the result of the number of alarms in the system. In this case:

The alarm group must have 130 elements, just like the size of the alarm and acknowledgment image must be 130.

Implicit order of alarms:

After creating new data for a CompactFlash card and the initial upload to the controller, the mapp alarms are ordered according to the enable sequence. If new mapp components are added, they are appended at the end of the existing list.

Explicit order of alarms:

Alternatively, the user can explicitly define the order of all alarms for the alarm array using the extended parameters of the MpAlarmBasic configuration:

Compared to a decentralized connection of MpAlarmBasicUI to individual mapp components (which would result in multiple alarm mappings), there are the following advantages and disadvantages.

•Advantages:

•Only one function block instance of MpAlarmBasicUI needed

•Only one alarm group in Visual Components Better overview of all machine alarms

•Disadvantages:

•Offset of user alarms shifted when adding new mapp components

•Additional work managing offsets in the configuration

Alternative: Separating mapp and user alarms

The index shift for user alarms can be achieved by separating the alarms and using two instances of MpAlarmBasicUI. One instance is used with mode mpALARM_UI_MODE_MAPP, while the other uses mpALARM_US_MODE_USER. An alarm group is then created in Visual Components for each MpAlarmBasicUI.