Hi Kay,
In the example you pointed out, where is the alarm configuration for PV ‘test_alarm’? I cannot see this information.
For the case I reported, the alarm PV is defined as an unlatched alarm, with 2 second delay. I’m not sure if such configuration may has anything to do with what had observed.
Thanks,
Tong
From: Kay Kasemir <kasemirk at ornl.gov>
Sent: Wednesday, June 22, 2022 12:30
To: Zhang, Tong <ZhangT at frib.msu.edu>; tech-talk at aps.anl.gov
Cc: Ashwarya, Tanvi <ashwarya at frib.msu.edu>
Subject: Re: Phoebus alarm does not honor filter
[EXTERNAL] This email originated from outside of FRIB
>..we're using the default Phoebus alarm server configuration (my understand is org.phoebus.pv.ca/monitor_mask=VALUE).
> I was trying to export the full configurations from Phoebus to confirm the monitor_mask value, but it seems it only print out the ones that maintained in /etc/phoebus_settings.ini.
If you don't see org.phoebus.pv.ca/monitor_mask in the preferences, it's using the default, which is VALUE.
I agree that it's unfortunate that you can't see all available settings in the Help, About, .. preference listing.
Way back when we started phoebus I had suggested a way of using the java preferences in a way to give us all settings, no matter if they're at the default or changed,
https://github.com/ControlSystemStudio/phoebus/issues/4, but we ended up doing it such that the running instance can only list changes, for a complete listing you have to go to the online
help.
> Can you offer any approach for further investigation?
Try to come up with a reproducible example.
I've described one based on the demo.db and opi that are included in the alarm examples, and that looks fine when I run that here.
---
Well, I can't reproduce this.
I'm running a softIoc with that demo.db, add the test_alarm PV with enabling filter "test_enable>0" to the alarm tree, and then use the demo.bob display for the following:
1) Set test_alarm = 10, it shows up as MAJOR alarm in alarm table and tree
2) Set test_enable to 0. test_alarm is shown in gray with "(disabled)" in alarm tree, and not at all in alarm table
3) Set test_enable back to 1, and test_alarm shows back up as it looked in step 1