EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  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  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: record/device support general style question
From: Rok Sabjan <[email protected]>
To: "Owens, PH (Peter)" <[email protected]>
Cc: Jens Rekow <[email protected]>, [email protected]
Date: Mon, 21 Nov 2005 13:47:53 +0100
There is also an additional advantage in what Peter is suggesting.

If you distribute the values in the database it is easier and more transparent how you distribute alarms, which can be very important when maintaining your database.

Rok


Owens, PH (Peter) wrote:
There is no need to have the device support distributing the values.

It is simpler to do this via database processing
and have the other records extract the values for themselves from the original input record.


Pete


-----Original Message-----
From: Jens Rekow [mailto:[email protected]]
Sent: 17 November 2005 15:38
To: [email protected]
Subject: record/device support general style question


My way so far is another: There is one AsynDriver-powered record
(stringin) which retrieves and holds the status string. That value is read
by a longin record via dbGetField() in a standard device support, which
extracts the information and distributes to all the other relevant records
via dbPutField(). Thus these other records don't need any device/record
support implementation themselves but are set remotely. Unfortunately this
complicates handling the alarm/invalid states of these records.


So the question is:
Would it be better to have already my AsynDriver-powered record, which
reads the status bytes, distributing the values to the different records
via dbPutField()?
Alternatively I like the idea of only one device support implementation
for several records which is flexible using the INP field as a
parameter...



Any suggestions? What could be more 'stylish'?

Thanks in advance,
Jens







--
_____________________   _   _   _   _   ____________________
                     |_| |_| |_| |_| |_|
Rok Sabjan                                         Cosylab
Head of EPICS Section               http://www.cosylab.com
Email: [email protected]             Teslova ulica 30
Phone: +386 (1) 4776-767                 SI-1000 Ljubljana
Cell:  +386 (41) 796-666                          Slovenia
__   _   _   _   _   __________________   _   _   _   _   __
  |_| |_| |_| |_| |_|                  |_| |_| |_| |_| |_|

References:
RE: record/device support general style question Owens, PH (Peter)

Navigate by Date:
Prev: infrastructure questions rolf
Next: RE: Writing to PVs Liyu, Andrei
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: record/device support general style question Owens, PH (Peter)
Next: Getting CA data with VC Xu HuiJuan
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <20052006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·