EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  <20002001  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  <20002001  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: aao record behaviour
From: Korhonen Timo <[email protected]>
To: Marty Kraimer <[email protected]>
Cc: [email protected]
Date: Fri, 28 Apr 2000 17:21:58 +0200 (MEST)
On Fri, 28 Apr 2000, Marty Kraimer wrote:

> At aps we have not used the aai or aao records. Thus I fear making changes. If
> You and Eric can agree on changes (starting with the 3.13.2 version) I will put
> the new version in the next release.

Eric (Bjorklund), if you see this please comment! 

I could use the waveform record (or genSub record) to achieve what
I need (sending a waveform to an arbitrary waveform generator), but
I took a look at the aao record because a) waveform record is obviously
intended mainly for input and b) the aao record was there.

However, I am willing to implement the changes and test them. It is
not so nice to have things in the distribution which are obviously broken.
 
> Here is another problem for  aai and aao.
> 
> The init_record looks like
> 
>     if (pass==0){
>         if(paai->nelm<=0) paai->nelm=1;
>         return(0);
>     }
> 
> And then it waits for device support to allocate space for the array during pass
> = 1. This can lead to severe problems since storage MUST be allocated during
> pass 0. If another record has a link to the array and this record gets
> initialized before thye array record bad things will happen. If you and Eric
> decide to fix the problem I have an idea that may work. It dose mean, however,
> that associate device support also needs to be modified.

For me it is easy to modify what I have now, because it is in the
beginnings. Could people who are using aai/aao comment on the implications
of changing the record support code?

Timo


Timo Korhonen  PSI (Paul Scherrer Institut), SLS 
               CH-5232 Villigen PSI 
               tel + 41- 56 3103262  fax + 41 - 56 310 3151 
e-mail:	       [email protected]





References:
Re: aao record behaviour Marty Kraimer

Navigate by Date:
Prev: Re: aao record behaviour Marty Kraimer
Next: EPICS training at Los Alamos week of June 5th Leo Dalesio
Index: 1994  1995  1996  1997  1998  1999  <20002001  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: aao record behaviour Marty Kraimer
Next: Re: aao record behaviour Eric Bjorklund
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·