|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
16 May 2024, Konstantin Olchanski, Bug Report, midas alarm borked condition evaluation
|
17 May 2024, Stefan Ritt, Bug Report, midas alarm borked condition evaluation
|
17 May 2024, Konstantin Olchanski, Bug Report, midas alarm borked condition evaluation
|
17 May 2024, Konstantin Olchanski, Bug Report, midas alarm borked condition evaluation
|
18 May 2024, Stefan Ritt, Bug Report, midas alarm borked condition evaluation
|
|
Message ID: 2771
Entry time: 17 May 2024
In reply to: 2769
Reply to this: 2772
2773
|
Author: |
Konstantin Olchanski |
Topic: |
Bug Report |
Subject: |
midas alarm borked condition evaluation |
|
|
>
> And I think I know what caused the original problem in IRIS experiment, I think the list of EPICS variables got truncated from 30 to 20 and EPICS
> values 29 and 30 used in the alarm conditions have become lost.
>
> So the next step is to fix feepics to not truncate the list of variables (right now it is hardwired to 20 variables) and restore
> the lost variable definition from a saved odb dump.
for the record, I restored the old ODB settings from feepics, my EPICS variables now have the correct size and the alarm now works correctly.
I also updated the example feepics to read the number of EPICS variables from ODB instead of always truncating them to 20 (IRIS MIDAS had a local change
setting number of variables to 40).
I think I will make no more changes to the alarms, leave well enough alone.
K.O. |