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: AAI/AAO database information |
From: | Till Straumann <[email protected]> |
To: | Andrew Johnson <[email protected]> |
Cc: | David Dudley <[email protected]>, [email protected] |
Date: | Mon, 06 Nov 2006 10:08:53 -0800 |
David Dudley wrote:FYI. WE do use them at SSRL/SLAC.I've seen references to AAI and AAO records someplace, which I assume are Array Analog Input and Output. Is support for that put in the device driver?
The aai and aao records are a bit of an anachronism; they're not really used very much,
there's no soft or test device support included in Base, and they're not documented anywhere either.The source is good enough.
I think they were contributed by one site a long time ago, and we just haven't got around to removing them yet (they'll be gone if R3.15 is ever released).Has there been a discussion about this? We would be in quite a bit of trouble if these are removed.
I have a condition working with the Multilin control relays, where I need to be able to generate a multiple register output sequence, where the entire sequence is done in a single record. This would fit that perfectly, I think.
Use a waveform record if you want device support where the whole array comes from a CA client. However if you're going to want to be able to set some individual elements from another record they you'll be much better off writing device support that takes the higher level parameters and combines them into the appropriate array/sequence internally.
- Andrew