Experimental Physics and
Industrial Control System

"Mark Rivers" <[email protected]> · Thu, 4 Nov 2004 07:31:52 -0600

Hi Geoff,

I found that same problem last week and fixed it for the next release.
It has been fixed by passing userParam as an additional parameter to the
asyn*SyncIO->connect() and asyn*SyncIO->*Once functions.

We are working hard on getting the next release out ASAP.  The main
feature in the new release is the addition of driver callbacks to device
support for interrupts.

Right now we are working on improving EOS handling.  Once that is done
testing and documentation are all that is planned before the next
release.
Maybe next week?

Mark

> -----Original Message-----
> From: Geoff Savage [mailto:[email protected]]
> Sent: Thursday, November 04, 2004 7:21 AM
> To: EPICS Tech-Talk
> Subject: asynInt32SyncIO readOnce
> 
> Hi,
> 
> I have encountered a feature with asynInt32SyncIO function readOnce.
It
> does not use the asynUser data structure from the record.  The driver
> expects a user specified address passed from the end of the INP field
of
> the record.  The readOnce function creates a new asynUser so there is
no
> address available.  I'm wondering why the interface was designed this
way?
> 
> We are using EPICS 3.14.6 with asyn3-3.
> 
> Geoff

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System