Experimental Physics and
Industrial Control System
| 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 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: caSnooper output report question |
| From: | Andrew Johnson <[email protected]> |
| To: | Kevin Tsubota <[email protected]>, EPICS tech-talk <[email protected]> |
| Date: | Fri, 25 Jun 2004 10:22:11 -0500 |
Kevin Tsubota wrote:
- Why does the MEDM report output not have the "PP", "CPP" PVs until after I've run the command line report? I've verified this multiple times by stopping are restarting caSnooper and the GUIs but not the IOCs (EPICS R3.13.0Beta12) so the broadcasts are always there.
I note that those PVs come from a different client/IOC which doesn't show up at all in the other reports - are you certain that aocpu1 was running at the time? I'm not sure whether caSnooper generates beacon anomalies at startup - if it does it causes all disconnected channels to restart their searches, which isn't always what you want to happen.
- Why are the rates between the two report generation types different? Report 2 "PP" = 46hz, report 3 "PP" = 5hz.
You're running them at different times, so you're getting the results as seen at the time.
- Finally what is the "request rate" on the GUIs really telling me?
The rate in which it is being called by the CAS with a name to test. Since searching is a UDP operation and hence subject to packet loss there may be more searches going out over the network than any individual CAS can handle, but caSnooper isn't particularly slow so it seems to give pretty representative results.
If you want a second opinion on what's happening on your network, I've attached a simpler (command-line only) program I wrote which builds as an extension and performs roughly the same job as caSnooper, but is somewhat more flexible in what it reports. caClientMonitor -h prints help. There's no documentation other than the source code, but if anyone wants to write their own monitoring tool that does not present its results via a Channel Access server then this is probably a better place to start than caSnooper. The EPICS Open license applies to the attached code.
- Andrew -- Dear God, I didn't think orange went with purple until I saw the sunset you made last night. That was really cool. - Caro
Attachment:
cacm.tar.gz
Description: GNU Zip compressed data
- References:
- caSnooper output report question Kevin Tsubota
- Navigate by Date:
- Prev: caSnooper output report question Kevin Tsubota
- Next: MVME-5100 choices Steven Hartman
- 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: caSnooper output report question Kevin Tsubota
- Next: MVME-5100 choices Steven Hartman
- 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
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·