Hi,
I’m using the following type attribute | DataMiner Docs to enable the smart baseline functionality for a given parameter.
<Alarm type="relative:NOMINAL_VALUE_PID,FACTOR_PID">
Now when checking the information events, I see quite some being generated for the parameter used as the ‘nominal value’. Is there any possibility to get this disabled?
Thank you!
When using a parameter for filling in the ‘nominal value’ for the baseline, then we can look to the trend of this parameter. This way we can analyze the calculated baseline and verify the alarms being generated.
Jarno,
The smart base line manager generates those parameter sets and indeed as Laurens points out the reason the information event is generated is due to how the parameter is configured.
A task has been created on our backlog to avoid generating these information events. For now there is no real workaround available I’m afraid.
task ref: DCP208213
Hi Jarno,
I’m afraid that is not possible (yet). The problem is that the new baseline value enters through a set on a write parameter, just like any other normal set from a user would enter. As that write parameter has RTDisplay true, it will generate an information event.
The solution to avoid the information event would be to set RTDisplay false, but then the smart baseline will not know the id of the parameter anymore to perform the set on as non displayed parameters are not known, so that’s also not a valid solution :/ .
Regards,
Hi Jarno, is there any specific use case why you need to define the alarming type in the connector instead of the alarm template only?