Reading custom fields using alarm properties does not work.

KANG over 5 years ago

Hello. I'm KANG.

I'm using the alarm property to show the ability to read or write a value. Most are using analog alarms.

For example, if the name of analog alarm tag is 'AT0001', the setting value of High High can be read or written as 'AT0001.HighHigh'.

I registered a custom field among them.
However, if I try to read the value as 'AT0001.custom1', an empty string is returned.

What if I want to return the value entered in the custom field?

Version : Citect SCADA 2016 (Update Aug 13, 2019)

Olivier over 5 years ago

Hi KANG ,
This looks like a bug to me. It should return the custom value defined in the alarm tag configuration.
As a work around, you could use the alarm browse function, then the get field functions, but it might not meet your needs.
I'd recommend you reach out to Citect Support and get a bug raised for this issue to get it fixed.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Roger over 5 years ago

Hi KANG / Olivier,

This is a "feature" [I agree, it's a bug https://softwareforums.aveva.com/cfs-file/__key/system/emoji/1f642.svg]

A possible workaround is to use [Alarm]UseConfigLimits=1 to force using the RDB rather than the database. You should then be able to read and write to the custom fields with no problems ?

Edit: I should add that I've only used this in 2018 but suspect it's the same in 2016 !?!

Cheers,

Roger.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Patrick over 5 years ago

It's by design indeed. If you don't set the parameter that Roger mentioned, you have to delete the alarm database after every change of your alarm configuration.
Just be aware of the fact that if you do set the parameter, then every write to the alarm properties also gets written to the DBF and RDB files of your running project. Some might consider this as unwanted application behaviour (modifying its own source code).

Regards,
Patrick
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel