Experimental Physics and
Industrial Control System

.. As you can see from the -d output, I have EPICS_PVA_ADDR_LIST set to 10.0.2.15, the IP of the VM, which is fine for pvget.
.. Pvinfo never shows anything for the other IP or broadcast addresses:

$ EPICS_PVA_ADDR_LIST=192.168.122.255 pvinfo training:ai1
training:ai1 Error: channel destroyed
$ EPICS_PVA_ADDR_LIST=192.168.122.1 pvinfo training:ai1
training:ai1 Error: channel destroyed
$ EPICS_PVA_ADDR_LIST=10.0.2.15 pvinfo training:ai1
training:ai1 Error: channel destroyed
$ EPICS_PVA_ADDR_LIST=10.0.2.255 pvinfo training:ai1
training:ai1 Error: channel destroyed

Replies:

Re: pvget -m timeout after first value Michael Davidsaver

References:

pvget -m timeout after first value Kasemir, Kay via Core-talk

Re: pvget -m timeout after first value Michael Davidsaver

Re: pvget -m timeout after first value Kasemir, Kay via Core-talk

Re: pvget -m timeout after first value Michael Davidsaver

Re: pvget -m timeout after first value Kasemir, Kay via Core-talk

Re: pvget -m timeout after first value Michael Davidsaver

Re: pvget -m timeout after first value Kasemir, Kay via Core-talk

Re: pvget -m timeout after first value Michael Davidsaver

Re: pvget -m timeout after first value Kasemir, Kay via Core-talk

Re: pvget -m timeout after first value Michael Davidsaver

Re: pvget -m timeout after first value Kasemir, Kay via Core-talk

Navigate by Date:

Prev: Re: pvget -m timeout after first value Kasemir, Kay via Core-talk

Next: Re: pvget -m timeout after first value Michael Davidsaver

Index: 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: Re: pvget -m timeout after first value Kasemir, Kay via Core-talk

Next: Re: pvget -m timeout after first value Michael Davidsaver

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <2018>  2019  2020  2021  2022  2023  2024