| 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 <2025> | 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 <2025> |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: Writing array data in an AreaDetector application |
| From: | Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Ralph Lange <ralph.lange at gmx.de>, EPICS Tech Talk <tech-talk at aps.anl.gov> |
| Date: | Thu, 1 May 2025 17:48:21 +0000 |
|
I do see a message I had overlooked before: devAsynFloat64Array::initCommon, 13PIL1:cam1:PADDigiCorr find asynFloat64Array interface failed I think I have the function names and signatures right, from looking at file asynPortDriver.h, if that is what you mean. From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Ralph Lange via Tech-talk Hi Iain, Looking at the documentation [1] and your record, it all seems fine. The waveform record type was created as an input - that's why the configuration field is INP. Unrelated to your problem. It's most probably a code issue. Is your additional method properly declared in the class declaration, so that the default implementation of the method is overridden? Cheers, Click
here to report this email as spam. This message has been scanned for malware by Forcepoint. www.forcepoint.com |