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: [EXTERNAL] Re: Monitored PV limit? |
From: | Aaron Brown via Tech-talk <[email protected]> |
To: | Ralph Lange <[email protected]>, EPICS Tech Talk <[email protected]> |
Date: | Fri, 8 Nov 2019 18:22:29 +0000 |
Hi Ralph,
That was exactly the limit I was experiencing. Changing that limit fixed the problem.
Ultimately I would create a different client to monitor a large number of PVs (I am currently working on creating a large scale data logger), but for now I just wanted to get a better understanding of how the client works and make sure that the client I set
up worked the way I wanted it to.
Thanks for the quick answer!
Aaron Brown
Detector Support Group
Jefferson Lab
From: Ralph Lange <[email protected]>
Sent: Friday, November 8, 2019 11:22 AM To: EPICS Tech Talk <[email protected]> Cc: Aaron Brown <[email protected]> Subject: [EXTERNAL] Re: Monitored PV limit? Hi Aaron,
Assuming you refer to the caMonitor example code that comes with Base: this is an example for how to use the CA client library. In its sources it sets (line 27)
#define
MAX_PV
1000
which is most probably the limit you are experiencing.
For monitoring 5000 values, a command line client does not sound like a reasonable tool. If you can give some more details on your use case, there might be better ways to get it done.
Cheers,
~Ralph On Fri, 8 Nov 2019 at 17:09, Aaron Brown via Tech-talk <[email protected]> wrote:
|