Experimental Physics and
Industrial Control System

This is not a pvAccess issue…The alarm status and severity is set by the record, right?

I just used pvget to check the status of the record; caget tells exactly the same thing.

 

The description in the NT specification is there for reference and not a specification for the implementation, would be in a totally wrong place there. Right?

 

There is one issue in VTypes as well but the IOC behavior does seem to have an issue on its own that has to be solved, or explained if I (and Kay) have understood it wrong.

 

Timo

 

From: Core-talk <core-talk-bounces at aps.anl.gov> on behalf of EPICS Core Talk <core-talk at aps.anl.gov>
Reply to: Ralph Lange <ralph.lange at gmx.de>
Date: Tuesday, 8 March 2022 at 16:51
To: EPICS Core Talk <core-talk at aps.anl.gov>
Subject: Re: Definition (or not) of alarm limits

 

On Tue, 8 Mar 2022 at 09:39, Timo Korhonen via Core-talk <core-talk at aps.anl.gov> wrote:

Hi all,

 

We noticed recently that if for instance the lower alarm limits are not explicitly defined in the EPICS database, CS-Studio reports all limits to be NaN. See here https://github.com/ControlSystemStudio/cs-studio/issues/2716 for a description and a following discussion.

 

Kay pointed out that even when the limits are explicitly defined as 0, the IOC reports them as NaN. Now this starts to smell like a bug. But before I submit a bug report, I wanted to ask if there is a reason behind this behavior? Maybe it is a feature and not a bug?

 

There is another interesting case, described by Kay in the above issue report, when only one HIGH and not HIHI is defined. How should this case be interpreted? The “Process Database Concepts” documentation ( https://docs.epics-controls.org/en/latest/guides/EPICS_Process_Database_Concepts.html#alarm-conditions-configured-in-the-database ) indicates that the alarm limits express a range, however not very explicitly. But this is not consistent with this case.

 

Any thoughts?

 

Hmm...

 

Isn't that part of the Normative Types spec the definition of alarm limits in pvAccess?

https://github.com/epics-base/normativeTypesCPP/wiki/Normative+Types+Specification#alarmlimit_t

 

This range thing seems to be a 'VType' problem.

 

Cheers,
~Ralph

 

-- 
Complexity is free, it's Simplicity that takes work.

References:

Definition (or not) of alarm limits Timo Korhonen via Core-talk

Re: Definition (or not) of alarm limits Ralph Lange via Core-talk

Re: Definition (or not) of alarm limits Timo Korhonen via Core-talk

Navigate by Date:

Prev: Re: Definition (or not) of alarm limits Timo Korhonen via Core-talk

Next: Re: Definition (or not) of alarm limits Michael Davidsaver via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024 

Navigate by Thread:

Prev: Re: Definition (or not) of alarm limits Timo Korhonen via Core-talk

Next: Re: Definition (or not) of alarm limits Michael Davidsaver via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <2022>  2023  2024