Alarm List Widget – No alarms displayed after migration AS4 -> AS6.5

Ask Questions B&R Software & Runtime
,
1

Hi everyone,
I’m currently continuing the migration of a project from Automation Studio 4 to Automation Studio 6.5.

After:

I bound the Alarm List widget to the root AlarmCore (GroupMain), which acts as the parent for all other alarm groups.

However, no alarms are displayed in the visualization, even though the alarms are active.
The same issue occurs with the Alarm History widget, which also remains empty.

I’m wondering whether:

  • a different binding is required (e.g. binding to a specific AlarmCore instead of the root),

  • some additional configuration or parameter is needed in AS 6.5 compared to AS4,

  • or if alarm group handling with mpComGroup works differently in the newer version.

Has anyone experienced a similar issue or can suggest what I should check?

Thanks in advance.

2

Hello

MpServer Library is present in the project (and also on the target, check CPU.sw)?

Do you have any logger entries?

Bindings Widget <> MpLink are working, can you check with mapp View Diagnostic Page?

Lg Michael

3

Hi Michael,

yes, the MpServer library is present in the project and I also verified that it is available on the target (CPU.sw).

I checked the mapp View Diagnostic Page as well, and all Widget ↔ MpLink bindings seem to be OK. I don’t see any particular errors or warnings there.

There are no relevant logger entries either.
It almost looks as if no alarms exist at all, even though they are defined and should be active.

Thanks for your support.

4

Hi,

A lot has changed in mappAlarmX with AS6. :grinning_face:
I assume you are familiar with this page:
Migrating from mapp Services 5.x to mapp Services 6.0

My first guess:

AS4 had the default action “Escalate Alarm”.

As4.12
As4.121346×303 23.2 KB

This has been removed in AS6.
As6
As6623×677 42.1 KB

In our case, we work with severities, and all alarms are escalated (green)

Best regards,
Simon

2 Likes
5

Hi Simon,

thanks a lot for the hint.
I had followed the migration guidelines, but I completely missed this specific point.

After applying your suggestion, I can finally see the alarms correctly.

Thanks again for the support!

Best regards,