| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: asynPortDriver Question |
| From: | Ralph Lange <[email protected]> |
| To: | EPICS Tech Talk <[email protected]> |
| Date: | Mon, 28 Mar 2011 10:29:22 +0200 |
On 27.03.2011 00:11 Mark Rivers wrote:
Hi Zen, I don't think you can do that. The first order problem is that there is no connection from the asyn driver to the AO:SC record, since it uses soft device support, not asyn device support. I don't think there is a way to propogate alarm status between records at the database level except by using the MS qualifier on input and output links. But I'm not a database programming expert, perhaps there is a way to do this.
You can point any unused input link of your "target" record to a field in your "source" record and make it "MS" to pull the severity from the "source". I know people that are regularly abusing the SIML input link to achieve this....
HTH, Ralph