Experimental Physics and
Industrial Control System

Hi again Kiman,

I wanted to let you know that the PVA gateway documentation was recently updated (within the hour prior to this message), at https://mdavidsaver.github.io/p4p/gw.html

 

SLAC

 

 

Hi Kiman,

The status PVs should be accessible as regular PVs using pvget or pvcall.

If you have the latest version of the p4p gateway, and the statusprefix is set to sts_server: as you’ve indicated, you could type:

pvget  sts_server:clients

pvget  sts_server:cache

and so forth.

The asTest PV is different because it uses RPC, so you could type:

                pvcall sts_server:asTest  pv=”my:pv:name”

(using one of your own PVs instead of my:pv:name)

 

I’m wondering if you have a previous version of the gateway because, for example mine doesn’t show a StatsTime PV.

Also you should be able to run the gateway in the background by typing “pvagw &”, at least for testing purposes.  Ideally, it would be run through something like systemd, depending on your host.

 

 

 

Hello All,

 

I am testing the PVA gateway and completing the installation of the PVXS and P4P modules.

In the first test, I can read/write device IOC PVs from a client, which means the pva gateway works fine.

In the next step, I’d like to monitor pvagateway provided server/clients status PVs; for example, read this PV “sts_server:StatsTime” from the client.

 

How do I read pvagateway internal PVs?

Would you like me to install p4p python packages?

 

I just run pvagw mytest.config, any more efficient way to run pvagw as background?

 

 

p4p]$ bin/linux-x86_64/pvagw mytest.conf

 

INFO:p4p.gw:Client theclient input config:

 

INFO:p4p.gw:Status PV: sts_server:StatsTime

INFO:p4p.gw:Status PV: sts_server:asDebug

INFO:p4p.gw:Status PV: sts_server:asTest

INFO:p4p.gw:Status PV: sts_server:cache

INFO:p4p.gw:Status PV: sts_server:clients

INFO:p4p.gw:Status PV: sts_server:ds:byhost:rx

INFO:p4p.gw:Status PV: sts_server:ds:byhost:tx

INFO:p4p.gw:Status PV: sts_server:ds:bypv:rx

INFO:p4p.gw:Status PV: sts_server:ds:bypv:tx

INFO:p4p.gw:Status PV: sts_server:poke

INFO:p4p.gw:Status PV: sts_server:refs

INFO:p4p.gw:Status PV: sts_server:stats

INFO:p4p.gw:Status PV: sts_server:threads

INFO:p4p.gw:Status PV: sts_server:us:byhost:rx

INFO:p4p.gw:Status PV: sts_server:us:byhost:tx

INFO:p4p.gw:Status PV: sts_server:us:bypv:rx

INFO:p4p.gw:Status PV: sts_server:us:bypv:tx

INFO:p4p.gw:Server effective config stserver_0 :

 

 

INFO:p4p.gw:Status PV: sts_client:StatsTime

INFO:p4p.gw:Status PV: sts_client:asDebug

INFO:p4p.gw:Status PV: sts_client:asTest

INFO:p4p.gw:Status PV: sts_client:cache

INFO:p4p.gw:Status PV: sts_client:clients

INFO:p4p.gw:Status PV: sts_client:ds:byhost:rx

INFO:p4p.gw:Status PV: sts_client:ds:byhost:tx

INFO:p4p.gw:Status PV: sts_client:ds:bypv:rx

INFO:p4p.gw:Status PV: sts_client:ds:bypv:tx

INFO:p4p.gw:Status PV: sts_client:poke

INFO:p4p.gw:Status PV: sts_client:refs

INFO:p4p.gw:Status PV: sts_client:stats

INFO:p4p.gw:Status PV: sts_client:threads

INFO:p4p.gw:Status PV: sts_client:us:byhost:rx

INFO:p4p.gw:Status PV: sts_client:us:byhost:tx

INFO:p4p.gw:Status PV: sts_client:us:bypv:rx

INFO:p4p.gw:Status PV: sts_client:us:bypv:tx

INFO:p4p.gw:Setup GW clients to ignore GW servers

 

 

Kiman