EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
<== Date ==> <== Thread ==>

Subject: Re: recDynLink.c for R3.14.1 ?
From: Tim Mooney <mooney@aps.anl.gov>
To: Kate Feng <feng1@bnl.gov>
Cc: tech-talk@aps.anl.gov, mrk@aps.anl.gov
Date: Mon, 14 Apr 2003 18:53:33 -0500
re...,
Kate Feng wrote:
> 
> Hi,
> 
> I  could not find recDynLink.c in the R3.14.1 release.
> It was in R3.13.5.   Is  the function of recDynLink.c replaced
> by something else  in the R3.14.1 rellease ?   If not,  I
> will go ahead and add an OSI over recDynLink.c for
> my device drivers.

Jens Eden converted recDynLink to EPICS 3.14, and I've made a
few trivial modifications from the code he sent me.  I don't know
on what platform(s) the code has been run, or even if it has been
run.  I'm converting most of synApps (which includes recDynLink with
modifications to support ca_put_callback links), but I haven't tested
anything yet.

For the record, recDynLink was the original implementation (by Marty
Kraimer) of retargetable links.  Now that all EPICS links are retargetable,
it's probably preferable to use standard links, unless you want a
(putNotify) callback when the execution your link started completes.
Note that the version of recDynLink in base has never had this
capability, so if you've been using the version from base, you
can switch to standard links.  We still need recDynLink for the sscan and
swait records, because they must wait for processing they start to finish,
and I plan to write a version of the seq record with the option of waiting
until processing started by one link has finished before firing the next link
in the sequence.  We've been doing this with sequences of swait records often
enough to know that the capability will get used.

In any case, I'm sending you the recDynLink code in a separate
email.  (I don't think the whole list needs a copy of this code
right this minute.  It will be included in the first 3.14-compatible
version of synApps.)

-- 
Tim Mooney (mooney@aps.anl.gov; 630-252-5417)
Advanced Photon Source
APS Operations Division
Beamline Controls & Data Acquisition Group

References:
recDynLink.c for R3.14.1 ? Kate Feng

Navigate by Date:
Prev: Channel Access disconnect/reconnect Nick Rees
Next: RE: Channel Access disconnect/reconnect Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020 
Navigate by Thread:
Prev: recDynLink.c for R3.14.1 ? Kate Feng
Next: RE: recDynLink.c for R3.14.1 ? Feng, Shuchen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <20032004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020