1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 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: asynPortDriver callbacks to I/O Intr, how to propagate an error? |
From: | "Heesterman, Peter J" <[email protected]> |
To: | "EPICS Tech-Talk ([email protected])" <[email protected]>, "'Mark Rivers'" <[email protected]> |
Date: | Fri, 30 Oct 2015 17:43:59 +0000 |
Hi Mark, I’m sorry to trouble you again, on a different subject. I refer to
http://www.aps.anl.gov/epics/tech-talk/2012/msg00924.php. I’m using setParamStatus, for an I/O Intr driven ‘Fault’ value, in my application, to signal alarm status. There seems to have been a behaviour change between Asyn 4-26 and Asyn 4-27. When using 4-27, the alarm status on ‘Fault.SEVR’ field is set to INVALID, but the ‘Fault.VAL’ field is not updated with the (non-zero) value that indicates the fault condition. But if I comment out the setParamStatus call, then Fault.VAL is set to the correct value. Both values were set as expected, while using 4-26. Many thanks, Peter. |