On 4/19/21 2:25 AM, Дмитрий Прощенко wrote:
> Hello, Michael!
>
> CA woks. I've tested softIocPVA and that is what happened:
> epics> pvasr
> pvAccess Server v7.1.0
> Active configuration (w/ defaults)
> EPICS_PVAS_INTF_ADDR_LIST = 0.0.0.0:5075
> EPICS_PVAS_BEACON_ADDR_LIST = 127.255.255.255
Unfortunately the 127.255.255.255 "trick" does not work for the pvAccess Server implementation.
Is there some reason you don't use 192.168.122.255?
fyi. maybe relevant. On my personal Linux laptop I create a "dummy" software
bridge interface (cf. "man brctl" or "man ip-link") with no associated physical
or logical interfaces to work around this limitation.
> EPICS_PVAS_AUTO_BEACON_ADDR_LIST = NO
> EPICS_PVAS_BEACON_PERIOD = 15
> EPICS_PVAS_BROADCAST_PORT = 5076
> EPICS_PVAS_SERVER_PORT = 5075
> EPICS_PVAS_PROVIDER_NAMES = QSRV
>
> pvget -d cnt
Please also test "caget cnt". This will help to rule out some possible issues.
> 2021-04-19T10:59:32.552 Creating datagram socket from: 0.0.0.0:46421.
> 2021-04-19T10:59:32.552 Broadcast address #0: 127.255.255.255:5076. (unicast)
> 2021-04-19T10:59:32.552 Setting up UDP for interface 192.168.1.145/255.255.255.0, broadcast 192.168.1.255, dest <none>.
> 2021-04-19T10:59:32.552 Creating datagram socket from: 192.168.1.145:5076.
> 2021-04-19T10:59:32.552 Creating datagram socket from: 192.168.1.255:5076.
> 2021-04-19T10:59:32.553 Setting up UDP for interface 192.168.122.1/255.255.255.0, broadcast 192.168.122.255, dest <none>.
> 2021-04-19T10:59:32.553 Creating datagram socket from: 192.168.122.1:5076.
> 2021-04-19T10:59:32.553 Creating datagram socket from: 192.168.122.255:5076.
> 2021-04-19T10:59:32.553 Creating datagram socket from: 224.0.0.128:5076.
> 2021-04-19T10:59:32.553 Local multicast enabled on 127.0.0.1/224.0.0.128:5076.
> 2021-04-19T10:59:32.553 Sending 49 bytes 0.0.0.0:46421 -> 127.255.255.255:5076.
> Waiting...
> 2021-04-19T10:59:32.793 Sending 49 bytes 0.0.0.0:46421 -> 127.255.255.255:5076.
> 2021-04-19T10:59:33.272 Sending 49 bytes 0.0.0.0:46421 -> 127.255.255.255:5076.
> 2021-04-19T10:59:34.230 Sending 49 bytes 0.0.0.0:46421 -> 127.255.255.255:5076.
> 2021-04-19T10:59:36.146 Sending 49 bytes 0.0.0.0:46421 -> 127.255.255.255:5076.
> Timeout
> ..............
>
> As far as I understand address 127.255.255.255:5076 is right to broadcast. But in my other OS and in your example IP is defined (e.g. 192.168.18.190). Problems is able to receive message due to network setting?
>
> 19.04.2021, 00:57, "Michael Davidsaver" <mdavidsaver at gmail.com>:
>
> On 4/18/21 10:07 AM, Дмитрий Прощенко via Tech-talk wrote:
>
> Hi all!
>
> Im writting cpp program to drive a power supply. Use pv Access for connection. Also I created an IOC using makeBaseApp.pl on my Kubuntu and created bd for testing. And all is well. But using other OS whit IOC I found that my program is not working. pvget isnt working too. I was able tofind information on the need to use qsrv:
> myioc_LIBS += qsrv
> myioc_LIBS += pvAccessIOC
> myioc_DBD += PVASeerverRegister.dbd
> myioc_DBD += qsrv.dbd
>
> executing pvasr on other OS:
> EPICS_PVAS_INTF_ADDR_LIST = 0.0.0.0:5075
> EPICS_PVAS_BEACON_ADDR_LIST = 127.255.255.255
> EPICS_PVAS_AUTO_BEACON_ADDR_LIST = NO
> ....
>
>
> This looks correct.
>
>
> And pvget or pvput is not working anyway. I used pva2pva (QSRV / pvAccess Gateway) to know about qsrc. What documants shout I pay attention to? What should I fix to keep it working? I would like to use several IOCs, do I need to configure my addresses go them for correct operation?
>
>
> Can you test with the softIocPVA executable and a simple database?
> This should confirm if this is a network issue.
>
> Also, can you confirm that caget also works?
>
>
>
> cat <<EOF > tick.db
> record(calc, "$(P=)cnt") {
> field(INPA, "$(P=)cnt")
> field(CALC, "A+1")
> field(SCAN, "1 second")
> }
> EOF
>
>
>
>
> $ softIocPVA -d tick.db
> ...
>
>
>
>
> $ pvget -d cnt
> 2021-04-18T10:55:41.653 Creating datagram socket from: 0.0.0.0:45045.
> 2021-04-18T10:55:41.653 Broadcast address #0: 192.168.1.255:5076. (not unicast)
> 2021-04-18T10:55:41.653 Broadcast address #1: 192.168.210.255:5076. (not unicast)
> 2021-04-18T10:55:41.653 Setting up UDP for interface 192.168.1.68/255.255.255.0, broadcast 192.168.1.255, dest <none>.
> 2021-04-18T10:55:41.653 Creating datagram socket from: 192.168.1.68:5076.
> 2021-04-18T10:55:41.653 Creating datagram socket from: 192.168.1.255:5076.
> 2021-04-18T10:55:41.653 Setting up UDP for interface 192.168.210.1/255.255.255.0, broadcast 192.168.210.255, dest <none>.
> 2021-04-18T10:55:41.653 Creating datagram socket from: 192.168.210.1:5076.
> 2021-04-18T10:55:41.653 Creating datagram socket from: 192.168.210.255:5076.
> 2021-04-18T10:55:41.653 Creating datagram socket from: 224.0.0.128:5076.
> 2021-04-18T10:55:41.653 Local multicast enabled on 127.0.0.1/224.0.0.128:5076.
> 2021-04-18T10:55:41.653 Sending 49 bytes 0.0.0.0:45045 -> 192.168.1.255:5076.
> 2021-04-18T10:55:41.653 Socket sendto to 192.168.1.255:5076 error: Operation not permitted.
> 2021-04-18T10:55:41.653 Sending 49 bytes 0.0.0.0:45045 -> 192.168.210.255:5076.
> 2021-04-18T10:55:41.653 UDP Client Rx (49) 192.168.210.255:5076 <- 192.168.210.1:45045
> Waiting...
> 2021-04-18T10:55:41.654 UDP Client Rx (53) 0.0.0.0:45045 <- 192.168.210.1:58034
> 2021-04-18T10:55:41.654 Connecting to PVA server: 192.168.210.1:41685.
> 2021-04-18T10:55:41.654 Opening socket to PVA server 192.168.210.1:41685, attempt 1.
> 2021-04-18T10:55:41.654 Socket connected to PVA server: 192.168.210.1:41685.
> 2021-04-18T10:55:41.654 Acquiring transport to 192.168.210.1:41685.
> 2021-04-18T10:55:41.655 Connected to PVA server: 192.168.210.1:41685.
> cnt 2021-04-18 10:55:40.828 38
> 2021-04-18T10:55:41.655 Releasing TCP transport to 192.168.210.1:41685.
> 2021-04-18T10:55:41.655 TCP socket to 192.168.210.1:41685 is to be closed.
> 2021-04-18T10:55:41.655 UDP socket 0.0.0.0:0 closed.
> 2021-04-18T10:55:41.655 UDP Client Rx (0) 0.0.0.0:45045 <- 192.168.210.1:58034
> 2021-04-18T10:55:41.655 UDP socket 192.168.1.68:5076 closed.
> 2021-04-18T10:55:41.655 UDP Client Rx (0) 192.168.1.68:5076 <- <Ukn Addr Type>
> 2021-04-18T10:55:41.655 UDP socket 192.168.1.255:5076 closed.
> 2021-04-18T10:55:41.655 UDP Client Rx (0) 192.168.1.255:5076 <- <Ukn Addr Type>
> 2021-04-18T10:55:41.655 UDP socket 192.168.210.1:5076 closed.
> 2021-04-18T10:55:41.655 UDP Client Rx (0) 192.168.210.1:5076 <- <Ukn Addr Type>
> 2021-04-18T10:55:41.655 UDP socket 192.168.210.255:5076 closed.
> 2021-04-18T10:55:41.655 UDP Client Rx (0) 192.168.210.255:5076 <- 192.168.210.1:45045
> 2021-04-18T10:55:41.655 UDP socket 224.0.0.128:5076 closed.
> 2021-04-18T10:55:41.655 UDP Client Rx (0) 224.0.0.128:5076 <- <Ukn Addr Type>
> Done
>
>
>
- References:
- pv Access setup Дмитрий Прощенко via Tech-talk
- Re: pv Access setup Michael Davidsaver via Tech-talk
- Re: pv Access setup Дмитрий Прощенко via Tech-talk
- Navigate by Date:
- Prev:
Re: pv Access setup Michael Davidsaver via Tech-talk
- Next:
Re: pv Access setup Дмитрий Прощенко 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
- Navigate by Thread:
- Prev:
Re: pv Access setup montis via Tech-talk
- Next:
display builder questions Geoffrey Savage 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·