<< Click to Display Table of Contents >> Navigation:  »No topics above this level« Decentralized alarm management for 2 axes

mapp Services V5.16

Requirement

A simple synchronous trimmer should be implemented with 2 MpAxisBasic components. The first MpAxisBasic is for the conveyor belt, and the second is for the synchronized movement of the trimming assembly.

The alarms from both axes should be collected and displayed in the HMI application using VC4 alarm management for current and past alarms.

Solution

•Component list

•MpAxisBasic (own MpLink): Controls the conveyor belt and cutting axis

•MpAlarmBasic (own MpLink): 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.

Connection diagram

Using the mapp components

Each instance of MpAlarmBasicUI is connected via the MpLink to the respective MpAxisBasic component. In mpALARM_UI_MODE_MAPP mode, therefore, only the mapp alarms will be included in the alarm image.

This means that in Visual Components an alarm group must be created with the MpAxisBasic standard alarms for each axis:

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

Each alarm group (2, one per axis) thus must have 15 elements, just like the size of the two alarm and acknowledgment images must be 15. When using MpAlarm decentrally, only the alarms of the mapp component connected to MpAlarmBasicUI are taken into account.

Compared to a centralized structure, i.e. 1 MpAlarmBasicUI connected directly to MpAlarmBasic, this variant has the following advantages and disadvantages:

•Advantage:

•No shifting of the alarm index in the alarm mapping if additional mapp components are added later

•Disadvantage:

•More MpAlarmBasicUI instances and UIConnect structures required