Experimental Physics and
Industrial Control System

Tim Mooney <[email protected]> · Thu, 17 Apr 2003 23:30:27 -0500

Benjamin Franksen wrote:
> 
> Hello,
> 
> maybe this is connected to the issue at hand. I am in the process of
> developing a "soft asynchronous" device support for output records. It
> utilises dbPutNotify (on which ca_put_callback is built). Record
> configuration interface is DTYP="Asyn Soft Channel", OUT="@name-of-pv"
> (link type INST_IO). Support for additional record types will be easy
> due to generic implementation with a very simple interface for record
> specific device supports.

Now this is interesting!  The reason I went with ca_put_callback was
partly the possibility that "name-of-pv" names a PV in a different crate,
in which case putNotify won't be able to do the job.  (Partly it was
laziness that lead me to ca_put_callback: I was working from recDynLink,
which was already doing ca_put's.)

The thing I hated to give up was the possibility of cancelling the
putNotify that my ca_put_callback had started.  If you start with
ca_put_callback, the only way I know of to get putNotifyCancel called is
to clear the CA channel.  I understand there would be enough pain involved
in plumbing support for a ca_put_callback_oops_never mind() function that
the idea goes on the list of maybe-someday enhancements, along with other,
more urgent requests.

Anyway, I for one would like to stay tuned to your efforts (though I'll be
out of email range for a while).  Please post updates.

-- 
Tim Mooney ([email protected]; 630-252-5417)
Advanced Photon Source
APS Operations Division
Beamline Controls & Data Acquisition Group

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System