EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: a technicality ?
From: Benjamin Franksen <[email protected]>
To: [email protected]
Date: Tue, 14 Aug 2007 14:36:38 +0200
On Tuesday 14 August 2007 12:59, Heinrich du Toit wrote:
> What is the relationship between:
> a record
> a pv (process variable)
> and a record field

A PV is something a CA (Channel Access) client can try to connect to and 
then communicate with. Thus it is the atomic unit of (remote) 
communication. A CA server knows about a certain number of PVs and ansers 
requests to (only) these PVs.

An EPICS IOC contains a CA server; however, it does not serve the PVs as a 
flat list. Instead they are structured using records. Most record fields 
are accessible, at least for reading, as a PV. Details of when and if a 
record field is accessable depend on the record type and CA Security 
configuration. For instance, field with type DBF_NOACCESS are not 
accessible.

> Plus - Why does so many of the docs/presentations has so much on about
> channel access? I know it's important to epics internally... but for the
> most part it actually invisible to the "user" ?

The protocol itself is normally invisible (i.e. as long as everything works 
as planned). However, some of CA's concepts need to be understood, mainly 
the idea of a process variable, which basic operations are supported for 
them (name lookup/connect, get, put, monitor). Also users should be able to 
help themselves with low-level command line tools like cainfo, caget, caput 
etc.

Cheers
Ben

References:
a technicality ? Heinrich du Toit

Navigate by Date:
Prev: RE: dm2k not compiling :( Heinrich du Toit
Next: RE: dm2k not compiling :( guobao shen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: a technicality ? Heinrich du Toit
Next: Re: a technicality ? Kay-Uwe Kasemir
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  <20072008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Nov 2011 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·