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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Asyn driver access to PV fields. |
From: | Marty Kraimer <[email protected]> |
To: | Mark Rivers <[email protected]> |
Cc: | tech talk <[email protected]> |
Date: | Thu, 19 Feb 2009 17:00:39 -0500 |
Mark Rivers wrote:
Hi Brian, The asyn driver does not have access to the record. The driver only talks to device support, and the device support talks to the record. I don't think you can do what you want using standard asyn device support. But if you wrote your own device support for the mbbo record(based on the mbbo support in devAsyn/devAsynInt32.c for example) could use the asynOctet interface to query the driver for the enumstring values during initRecord, and set those enum string values in the record. Mark -
What about adding a new method to asynUInt32Digital? Then change devAsynUInt32Digital so that it supports the new method.Also change asynUInt32DigitalBase so that it implements the new method by returning failure. Thus no existing driver will fail.
Marty