> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Brian McAllister
> Sent: Monday, January 30, 2006 1:17 PM
> To: EPICS tech-talk
> Subject: Re: enhanced seq record
>
>
> >>> On 1/30/2006 at 12:16:55 +0100, Luedeke Andreas wrote:
>
>> Of course the same can be done already with "calcout"
> chains. But a single record to control a sequence would simplify
matters.
>
> The calcout record is also one of the largest because it has
> all the calc code in it, thus being very inefficient if you don't
actually
> need to calc anything.
>
> I use seq or simple soft output records instead of calcout wherever
> possible for that reason.
But there is only one copy of the code for calcout in the entire IOC,
right? calcoutRecord.o is only 12kB on a vxWorks-ppc604, so it does not
seem very inefficient to me. The size of struct(calcoutRecord) is a
little bigger than struct(aoRecord), but not by a large amount.
Mark
- Replies:
- Re: enhanced seq record Brian McAllister
- Navigate by Date:
- Prev:
Re: enhanced seq record Brian McAllister
- Next:
Re: enhanced seq record Brian McAllister
- 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
- Navigate by Thread:
- Prev:
Re: enhanced seq record Tim Mooney
- Next:
Re: enhanced seq record Brian McAllister
- 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
|