2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Definition (or not) of alarm limits |
From: | Timo Korhonen via Core-talk <core-talk at aps.anl.gov> |
To: | Ralph Lange <ralph.lange at gmx.de>, EPICS Core Talk <core-talk at aps.anl.gov> |
Date: | Tue, 8 Mar 2022 16:06:31 +0000 |
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> On Tue, 8 Mar 2022 at 09:39, Timo Korhonen via Core-talk <core-talk at aps.anl.gov> wrote:
Hmm... Isn't that part of the Normative Types spec the definition of alarm limits in pvAccess? This range thing seems to be a 'VType' problem. Cheers, |