Experimental Physics and Industrial Control System
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
- Navigate by Date:
- Prev:
Re: asynDriver, devEpics user parameter access Marty Kraimer
- Next:
Re: Channel Access Protocol Specification Benjamin Franksen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: asynDriver, devEpics user parameter access Marty Kraimer
- Next:
async driver john sinclair
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024