Yes this is actually the work around I have used until I can
figure out a way to speed up the frame grabs.
Len
Leo Dalesio wrote:
>
> The fact that the record was processed, causes it to queue all the event
> that the array changed. You are not really receiving all of them - you are
> receiving copies of the most recent one. The array space required to queue
> was deemed too much to copy the data into the queue. To ingest these at the
> highest rate, some synchronization with the channel access client would be
> worthwhile. An option:
> make the image record scann Passive,
> have the channel access client put a 1 to the PROC field to cause it to
> process every time a new image is received.
>
> It seems that it is a little unfair to send multiple copies of the same
> array. Perhaps the default behavoir for arrays should be to cache the array.
>
> Needless to say, it is a bad thing to take up more than 100% of the
> processor.
>
> Bob
--
____________________________________________________
Leonard J. Reder
Jet Propulsion Laboratory
Interferometry Systems and Technology Section 383
Email: [email protected]
Phone (Voice): 818-354-3639
____________________________________________________
- References:
- scan tasks and monitors??? Leonard J. Reder
- Re: scan tasks and monitors??? Leo Dalesio
- Navigate by Date:
- Prev:
Re: scan tasks and monitors??? Leo Dalesio
- Next:
medm icon Paul Sichta
- 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: scan tasks and monitors??? Leo Dalesio
- Next:
medm icon Paul Sichta
- 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
|