EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  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  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: caSnoop question
From: "Martin L. Smith" <[email protected]>
To: Doug Summers <[email protected]>
Cc: "'Jeff Hill'" <[email protected]>, [email protected]
Date: Tue, 23 Nov 2004 15:32:59 -0600
Doug,
	Looks like to me that you are using runCaSnooper instead
of caSnooper. runCaSnooper is basically a wrapper script for caSnooper.
The script file that you have looks like it came from APS since I
do recognize these PV names as being names for reverse PV gateways.
If you are going to run caSnooper using runCaSnooper you will need
to modify that script for your site. You will ant to at the very
least remove all references to rxxx.DESC as well as existTestRate
since these will not exist on your network. From the command line
I ran runCaSnooper and in all of the output there was a statement:

"StripTool will plot CaSnooper process variables and those of the
reverse Gateways if they are available."

Hope that this helps,
Marty Smith
ANL/APS Controls Group


Doug Summers wrote:
Hi Jeff/all,

I've been doing some disconnected channel analysis using caSnoop, and I'm
confused by a portion of the output I've been seeing.  I am getting
disconnected channel outputs in both the launching xterm and mixed in the
caSnoop stats that I think are not related to our network traffic problems.
It looks like caSnoop and/or the stripchart used for caSnoop are either not
configured correctly and/or are interjecting some problems of their own.
I'm not suggesting our problem is caSnoop...I am making good progress with
the tool, but want to understand what caSnoop is adding into the mix.  Can
anyone explain what's happening (and maybe tell me how to minimize/eliminate
these effects)?  Here's our caSnoop terminal output messages:

requestDescRecord: ca_search_and_connect: CaSnoop.DESC
requestDescRecord: ca_search_and_connect: CaSnoop.DESC
requestDescRecord: ca_search_and_connect: r431.DESC
requestDescRecord: ca_search_and_connect: r432.DESC
requestDescRecord: ca_search_and_connect: r433.DESC
requestDescRecord: ca_search_and_connect: r434.DESC
requestDescRecord: ca_search_and_connect: r435.DESC
requestDescRecord: ca_search_and_connect: r436.DESC
requestDescRecord: ca_search_and_connect: r438.DESC
Strip_go: waiting for connection...

StripDAQ connect_callback: IOC unavailable for CaSnoop.individualRate
CA.Client.Exception...............................................
    Warning: "Virtual circuit disconnect"
    Context: "kepuhi:51425"
    Source File: ../cac.cpp line 1147
    Current Time: Tue Nov 23 2004 08:40:42.970034702
..................................................................
StripDAQ connect_callback: IOC unavailable for CaSnoop.requestRate

Tue Nov 23 08:40:43 HST 2004
medmCAExceptionHandlerCb: Channel Access Exception:
  Channel Name: Unavailable
  Native Type: Unavailable
  Native Count: 0
  Access: Unavailable
  IOC: Unavailable
  Message: Virtual circuit disconnect
  Context: kepuhi:51425
  Requested Type: TYPENOTCONN
  Requested Count: 0
  Source File: ../cac.cpp
  Line number: 1147

StripDAQ_request_disconnect: ca_clear_channel: CaSnoop.requestRate
StripDAQ_request_disconnect: ca_clear_channel: CaSnoop.DESC
StripDAQ_request_disconnect: ca_clear_channel: CaSnoop.individualRate
StripDAQ_request_disconnect: ca_clear_channel: CaSnoop.DESC
StripDAQ_request_disconnect: ca_clear_channel: r431.existTestRate
StripDAQ_request_disconnect: ca_clear_channel: r431.DESC
StripDAQ_request_disconnect: ca_clear_channel: r432.existTestRate
StripDAQ_request_disconnect: ca_clear_channel: r432.DESC
StripDAQ_request_disconnect: ca_clear_channel: r433.existTestRate
StripDAQ_request_disconnect: ca_clear_channel: r433.DESC
StripDAQ_request_disconnect: ca_clear_channel: r434.existTestRate
StripDAQ_request_disconnect: ca_clear_channel: r434.DESC
StripDAQ_request_disconnect: ca_clear_channel: r435.existTestRate
StripDAQ_request_disconnect: ca_clear_channel: r435.DESC
StripDAQ_request_disconnect: ca_clear_channel: r436.existTestRate
StripDAQ_request_disconnect: ca_clear_channel: r436.DESC
StripDAQ_request_disconnect: ca_clear_channel: r438.existTestRate
StripDAQ_request_disconnect: ca_clear_channel: r438.DESC

When I look at the report stats from caSnoop (using the medm tool), I see
these channels reported as disconnected (intermixed with our application
channel stats).  Are these disconnected references somehow inherent in the
tool, or do we have a  caSnoop configuration problem?  Any advice would be
appreciated.

Thanks,
Doug Summers
W. M. Keck Observatory
808 885-7887



References:
caSnoop question Doug Summers

Navigate by Date:
Prev: RE: caSnoop question Jeff Hill
Next: Which EDM version should we use? Steven . Banks
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: caSnoop question Jeff Hill
Next: Which EDM version should we use? Steven . Banks
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  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 ·