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  <20102011  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  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Analog output device support design
From: Angus Gratton <[email protected]>
To: Mark Rivers <[email protected]>
Cc: EPICS tech-talk <[email protected]>
Date: Thu, 29 Jul 2010 10:10:11 +1000
Hi Mark & Ralph,

On Wed, 2010-07-28 at 11:38 -0500, Mark Rivers wrote:
> I generally agree with Ralph that if you are just supporting the ao
> record with your DAC that asyn may be overkill.
> 
> On the other hand, my asyn driver for the Industry Pack dac128V is only
> 161 lines of code total (the source is appended).  It uses the
> asynPortDriver C++ base class.  I think it may be a challenge to write
> device support for your new DAC in only 161 lines of code.

Thanks for the detailed explanations, and thanks for the source - that's
very useful.

I've actually now moved on to implementing support for our ADC
(XVME-500), where I'll probably use asyn, and when I'm done there I may
look into going back and refactoring the DAC support.

Our current requirements are not particularly onerous in terms of
frequency or performance. The non-EPICS system that I'm replacing
currently does very straightforward I/O, synchronous even for ADC
conversions (20uSec)(*), with no particularly tight timing constraints. 

So in this rewrite I'm mostly trying to maximise code simplicity and
readability over any other metrics (which it seems can be achieved with
asyn as well.)

- Angus

(*) So, actually, if I correctly followed the explanation in one of the
lecture videos, 20uSec ADC conversions are probably fast enough that I
could implement this device support synchronously as well, instead of
using asyn. Although I'm probably going to use asyn.


References:
Analog output device support design Angus Gratton
Re: Analog output device support design Ralph Lange
Re: Analog output device support design Angus Gratton
Re: Analog output device support design Eric Norum
RE: Analog output device support design Mark Rivers
Re: Analog output device support design Ralph Lange
RE: Analog output device support design Mark Rivers

Navigate by Date:
Prev: Re: Tech-talk archives excluded from indexing? Angus Gratton
Next: Support for vxWorks 6.6 through 6.8 Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Analog output device support design Mark Rivers
Next: Re: Analog output device support design Luedeke Andreas
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  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 ·