In mappView, I linked the AlarmXCore from the root program to the Alarm List widget. However, I can only see the errors that occur in the root program,
but not those from the application module.
Does anyone have a soloution for this or had a similar problem?
unfortunately I can’t answer it in detail, as my knowledge there is already some years old and was not updated since then.
But as I remember, I think each alarm that should be reported to a parent instance of an alarm core additionally needs an escalation setup in the alarm mapping (alarm action = “escalate”, or if you just want / need combined alarms in the parent instance then “aggregate and escalate”).
Here’s the link to the online help about escalation: B&R Online Help
I know that some users here in the Community are using it and therefore know very well about how to combine different alarm cores - so I hope they will have the possibility to answer your post and give you some more concrete advise or insights then I can.
the term application module triggered something in the back of my head.
Since application modules seperate the variable space it might makes sense to have the application module name in the linking of the groups.
Meaning:
The ComGroup from the AppModule must be specified in the Framework ComGroup as follows:
Hi,
I had a similar error a while back that I was able to fix.
To resolve the error message in the mapp Hierarchy, you must specify a parent in the AlarmXCore configuration of the application module without the “AppModule::” prefix, as shown in the screenshot for “gAlarmXCore2.”
As mentioned earlier, the action in the alarm mapping should be set to “Escalate Alarm” so that the alarms are forwarded to the higher-level instance.
With these settings, it should work.
I hope this helps you.
Hi,
I’m not sure about it but just try to delete the parent of your Root AlarmXCore.
For me it also didn’t work when the root ComGroup was selected here.
