Experimental Physics and
Industrial Control System
| 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: | asynInt32SyncIO readOnce |
| From: | Geoff Savage <[email protected]> |
| To: | EPICS Tech-Talk <[email protected]> |
| Date: | Thu, 04 Nov 2004 07:21:27 -0600 |
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
- Navigate by Date:
- Prev: Re: async driver Marty Kraimer
- Next: RE: asynInt32SyncIO readOnce Mark Rivers
- 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: Reminder: EPICS meeting in ASIA, December 2004. registration Noboru Yamamoto
- Next: RE: asynInt32SyncIO readOnce Mark Rivers
- 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
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·