We have a lot of R&S DVMS and sometimes they return NAN on an OID that was supposed to be a number which dataminer displays as NaN
I added exception to the protocol
Whilst my exception gets picked up in the element - it never goes into alarm.
I then looked at the Others\Other Tags
https://docs.dataminer.services/develop/schemadoc/Protocol/Protocol.Params.Param.Interprete.Others.html
So setup a parameter 3312 of string "NAN" and to replace it with value -3 which I can set an alarm template on and it does alarm, however despite most of the time getting real numbers on the stream viewer the parameter is now permanently stuck with the "other" display value.
What am I missing here to get the alarm to generate?
Hi Sam,
You should be on the right path, the "others" tag is indeed what you need.
I'm not entirely sure about the exact cause of your issues, but the following things caught my eye. Please try to make these changes and let me know if that would resolve your problems:
- Your "Other" NAN parameter (3312) currently has the length type "next param". You can make this "Fixed": See the following example (your length should be 3 instead of 4 in my case):
- Your Exception for parameter 3313 is still present. You can/should remove that one as the types of the "values" of that exception don't have the right type (the string NaN vs the number -1)
I hope this helps!
Kind regards,