EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Going full PVA?
From: Stainer Tom via Tech-talk <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Wed, 9 Jun 2021 13:30:51 +0000

Dear Ralph,

 

 

Do you mean PVA to CA when writing through that IOC? That works when the QSRV mapping is done in the right way (which is not always trivial).

Or another IOC that maps a device speaking PVA into a flat CA control system namespace? Don't really know.

 

I meant the former. It is just entirely clear to me how you would implement this in practice.

Do you happen to know of any example code or associated documentation that I can use as a baseline on how to use QSRV to do this?

 

Kind regards,

Tom

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Ralph Lange via Tech-talk
Sent: Wednesday, June 9, 2021 1:40 PM
To: EPICS Tech Talk <tech-talk at aps.anl.gov>
Subject: Re: Going full PVA?

 

On Wed, 9 Jun 2021 at 12:15, Stainer Tom <Tom.Stainer at sckcen.be> wrote:

This is what I was thinking - the IOC is the “translator”. I am assuming in this scenario the IOC would be a soft IOC, as it would merely act as the gateway between CA and PVA, without any direct device support.

 

Correct.

 

The database would then handle this mapping between the two protocols.

 

Well, in a way, yes, nah, almost.

The database is the database. CA (client) to database mapping is handled by link support calling into the CA client library. Database to PVA mapping is done inside QSRV.

 

Can I assume that this would work both ways: CA to PVA *and* PVA to CA? I would assume so, but I just want to check I am not missing any nasty pitfalls.

 

Do you mean PVA to CA when writing through that IOC? That works when the QSRV mapping is done in the right way (which is not always trivial).

Or another IOC that maps a device speaking PVA into a flat CA control system namespace? Don't really know.

 

One thing I was thinking that would need to be handled would be mapping the structured data of PVA to the flat structure of CA. Is that what QSRV can do, or does it just go CA to PVA way?

 

That kind of mapping can be done in QSRV, where you can basically create a structure by pointing leaves to record fields in the database.

Again: you're mapping the elements of a PVA structure that QSRV serves up to fields of records in the EPICS database. CA is not involved on this end.

 

The fact that records can use CA to connect to other IOCs (or other devices running a CA server) is unrelated.

Your clients connect to a normal EPICS IOC using PVA, and you're effectively using CA as a field bus below the IOC, conceptually similar to Modbus, SCPI, EtherCAT, OPC UA, ...

 

Cheers,
~Ralph

 


Replies:
RE: Going full PVA? Stainer Tom via Tech-talk
Re: Going full PVA? Ralph Lange via Tech-talk
References:
Going full PVA? Stainer Tom via Tech-talk
Re: Going full PVA? Timo Korhonen via Tech-talk
RE: Going full PVA? Stainer Tom via Tech-talk
Re: Going full PVA? Timo Korhonen via Tech-talk
Re: Going full PVA? Ralph Lange via Tech-talk
RE: Going full PVA? Stainer Tom via Tech-talk
Re: Going full PVA? Ralph Lange via Tech-talk

Navigate by Date:
Prev: ADGenICam R1-8 available Mark Rivers via Tech-talk
Next: RE: Going full PVA? Stainer Tom 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  <20212022  2023  2024 
Navigate by Thread:
Prev: Re: Going full PVA? Ralph Lange via Tech-talk
Next: RE: Going full PVA? Stainer Tom 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  <20212022  2023  2024 
ANJ, 09 Jun 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·