On 11/11, Smith, Martin wrote:
> I think that this is happening because your PV name starts with a capital letter. At APS PVs that start with a
> capital letter are usually accelerator PVs so the PV gateway for your beamline lets that through. Although
> This should not be getting back through the reverse PV gateway but seems that it is. So the PV appears to be
> a duplicate I would guess because the PV gateway probably shows it has one and your IOC says that it has
> one.
Hi, Marty!
The PV name starting with a capital letter was Tejas's example, not
mine. In my case, the actual PV names start with a number, not a
capital letter.
Still, this is a PV naming restriction for beamlines at the APS
that I did not know about. Is it an official restriction, or are
you just wondering if it might be related to that due to a possible
misconfiguration in the APS-managed CA gateway that's on each sector's
"public" network?
Basically, I don't think there is a PV named the same as mine on the
APS accelerator side of things, so then I don't understand how the
APS-managed CA gateway could claim to have that PV.
> The thing I think that you would want to note is which CA server did it actually connect to and which got ignored.
Yes, and unfortunately, all I have is what it says in the
CA.Client.Exception messages, which is 0.0.0.1:5 and 0.0.0.2:5. Is
there some other way for me to tell which CA server it ultimately
connected to?
But on top of that, and I just included this in my reply to Tejas, but I
failed to include the following error message that appeared right after
the CA.Client.Exception messages, which might indicate that it didn't
connect to any CA server in this case:
----
Channel connect timed out: some PV(s) not found.
----
> At APS beamline PVs should start with either with a lower case letter or a number which will help prevent this
> sort of thing from happening.
OK, the actual PV names in this case started with a number, so I'm
thinking that means that's not the problem.
> If you want to have a private conversation about this I would be happy to look into this issue for you.
OK, thanks.
> As far as if you are getting strange IP addresses I'm not sure what that is about.
Yeah, me neither.
Thanks!
Lewis
- References:
- caget: Identical process variable names on multiple servers J. Lewis Muir via Tech-talk
- Re: caget: Identical process variable names on multiple servers Paul Sichta via Tech-talk
- Re: caget: Identical process variable names on multiple servers J. Lewis Muir via Tech-talk
- Re: caget: Identical process variable names on multiple servers Guruswamy, Tejas via Tech-talk
- Re: caget: Identical process variable names on multiple servers Smith, Martin via Tech-talk
- Navigate by Date:
- Prev:
Re: caget: Identical process variable names on multiple servers J. Lewis Muir via Tech-talk
- Next:
Re: caget: Identical process variable names on multiple servers Michael Davidsaver 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
2019
2020
2021
2022
2023
2024
<2025>
2026
- Navigate by Thread:
- Prev:
Re: caget: Identical process variable names on multiple servers Smith, Martin via Tech-talk
- Next:
Re: caget: Identical process variable names on multiple servers Michael Davidsaver 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
2019
2020
2021
2022
2023
2024
<2025>
2026
|