I'm wondering if the following is expected behavior or if it's a bug (v10.2.1, v10.1.6, v10.1 CU10).
The main element has a PSU table which exports parameters to the PSU DVE's. The main element has an alarm template which only alarms this exported PSU table, the DVE's do not have an alarm template.
The alarms can be seen in the table, but the bubble up is on the DVE's itself, the main element remains gray (alarm state = undefined):
So is it expected behavior that alarms on an exported table go to the DVE's and don't remain on the main element?
(fyi, alarming the non-exported parameters of the main element result in an alarmed main element)
Hi Alberto, this is something I haven’t encountered yet. I’ll keep an eye on this behavior! Thx 🙂
This is indeed the expected behavior, alarms on exported parameters only influence the element state of the DVE child elements. This is done to avoid duplicate alarms in the alarm console on both elements. If there would be an alarmed parameter in the protocol that is not exported, this would be expected to affect the alarm state of the DVE parent element, but not the child elements.
Is it possible to reflect this in the GUI?
I mean, from what I read I understand that the Alarm Template is associated to the MAIN element: in that case, as a user, I’d expect the main element isn’t grey, but showing some severity.
On the other hand, if the Alarm Template is associated to the DVE (not to the main) then, the colours in Robin’s screenshot would be expcted
Robin, does the colour stay grey even after a few days?
I remember seeing someting similar in the past where the main element kept the “undefined” colour state simply because no alarms had occurred yet – but eventually would become green once at least one severity had been retrieved.
In other post I learned timeouts may need to be handled separately:
https://community.dataminer.services/question/timeout-indication-on-dves/