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: Channel Access and channel name weirdness |
From: | "Johnson, Andrew N. via Tech-talk" <[email protected]> |
To: | Michael Westfall <[email protected]>, "[email protected] Talk" <[email protected]> |
Date: | Fri, 19 Jul 2019 21:38:20 +0000 |
Hi Mike, On 7/19/19 3:01 PM, Michael Westfall via Tech-talk wrote:
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. |