EPICS Home

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  <20192020  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  <20192020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Channel Access and channel name weirdness
From: Michael Westfall via Tech-talk <[email protected]>
To: "Johnson, Andrew N." <[email protected]>
Cc: "[email protected] Talk" <[email protected]>
Date: Mon, 22 Jul 2019 14:27:03 -0400
Hi Andrew,

I've filtered for packets coming from a specific IP address, so I know which IOC is sending it.

I hadn't considered the possibility that the problem is in a sequencer program. A quick check of the relevant  sequencer programs shows that these channels are referenced there as well as in the main database file. So... I will do some further investigation...

On Fri, Jul 19, 2019 at 5:38 PM Johnson, Andrew N. <[email protected]> wrote:
Hi Mike,  How do you know what client is requesting those names? My guess is it may be a sequence program (or maybe a PV named in an access security file) running on the same IOC which hasn't been given the right prefix.

The 'dbcar' command lists the IOC's dbCa links, and can confirm or deny that it's a database link (use dbcar "*", 0/1/2 to see increasing amounts of info). You'll need to use the sequencer commands seqShow and seqChanShow to check for unconnected channels for your sequence programs, I forget what the arguments are to seqChanShow but I think you give it a program name and "-" to see only disconnected channels. There is also a similar 'ascar <level>' command for reporting CA connections if you're using access security.

HTH,

- Andrew

-- 
Complexity comes for free, Simplicity you have to work for.


--
Mike Westfall
Control Systems Software Engineer



References:
Channel Access and channel name weirdness Michael Westfall via Tech-talk
Re: Channel Access and channel name weirdness Johnson, Andrew N. via Tech-talk

Navigate by Date:
Prev: RE:Compress Record with input from partial Waveform GAGET Alexis via Tech-talk
Next: Start OPIs from command line interface Tong Zhang via Tech-talk
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  <20192020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Channel Access and channel name weirdness Johnson, Andrew N. via Tech-talk
Next: Compress Record with input from partial Waveform Bruno Martins via Tech-talk
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  <20192020  2021  2022  2023  2024