Experimental Physics and Industrial Control System
Hello, I am facing problem in I/O Interrupt for waveform record in the asyn. If the value of waveform record change very fast then some of the samples missing or same sample repeat twice even if before p_interruptInt32Array->callback () function the value is scanned properly by driver. But i think the read value is pushed to the callback but it is not handle that much fast in the callback.
I checked the code for interruptCallbackInput in devAsynXXXArray.h.
In devAsynXXXArray.c dbScanUnlock has been used before scanIoRequest(). Can it create problem for repeating same value?
My assumption is as dbScanUnlock and before scanIoRequest() execute, value change and second time triggers interrupt. This result same value for both interrupts.
I checked interrupt callback code in devAsynInt32.c where epicsMutexUnlock has been used after scanIoRequest().
Thank you
Vishnu
![]()
Get your own FREE website, FREE domain & FREE mobile app with Company email. | Know More > |
- Replies:
- RE: Waveform record I/O interrupt. asyn Dalesio, Leo
- RE: Waveform record I/O interrupt. asyn Mark Rivers
- RE: Waveform record I/O interrupt. asyn Mark Rivers
- Navigate by Date:
- Prev:
Re: Epics/Raspberry Pi data acquisition Steve Shoaf
- Next:
RE: Epics/Raspberry Pi data acquisition Emmanuel Mayssat
- 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: Running Linux commands inside 'st.cmd' Andrew Johnson
- Next:
RE: Waveform record I/O interrupt. asyn Dalesio, Leo
- 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