Experimental Physics and
Industrial Control System

"Mark Rivers" <[email protected]> · Wed, 3 Nov 2004 07:41:38 -0600

Hi Geoff,

> How do I access the user parameters at the end of the INP or OUT
string
> allowed in devEpics in my driver?

To expand Marty's answer for release 3-3:

- Driver must implement the asynDrvUser interface
- Device support calls pasynDriver->create() with the user parameter
string
- Driver puts information in pasynUser->drvUser, which is a void *.

Note that the contents of void *drvUser is only understood by the
driver, and sometimes by device support.

In the next release (3-4 or 4-1), we added a new int field,
pasynUser->reason.  If the user parameter just translates to an enum or
int, then in drvUser->create() the driver should use pasynUser->reason,
rather than pasynUser->drvUser.  pasynUser->reason used by the interrupt
support in the new Base interfaces for each of the standard interfaces
(asynInt32, asynUInt32Digital, etc.).

Mark

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System