EPICS Home

Experimental Physics and Industrial Control System


 
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
<== Date ==> <== Thread ==>

Subject: Error (511,511)
From: Mark Rivers via Core-talk <core-talk at aps.anl.gov>
To: "'core-talk at aps.anl.gov'" <core-talk at aps.anl.gov>
Date: Sun, 22 Mar 2020 15:37:36 +0000
Folks,


I am having a problem with the ADSpinnaker driver when I write to PVs rapidly from a client.  Here is what I see with all asynTrace enabled.  The camera is currently acquiring in "free-run" mode at about 110 frames/s.  The client stops acquisition (sets ADAcquire=0) and then configures the trigger mode PVs for a triggered acquisition.



 *****************************

2020/03/22 10:16:30.681 13BMDPG1:cam1:ArrayCounter_RBV devAsynInt32::getCallbackValue from ringBuffer value=7065
2020/03/22 10:16:30.681 13BMDPG1:cam1:DetectorState_RBV devAsynInt32::interruptCallbackInput new value=7
2020/03/22 10:16:30.681 13BMDPG1:cam1:NumImagesCounter_RBV devAsynInt32::getCallbackValue from ringBuffer value=7065
2020/03/22 10:16:30.681 13BMDPG1:cam1:AcquireBusyCB devAsynInt32::interruptCallbackInput new value=0
2020/03/22 10:16:30.681 13BMDPG1:cam1:Acquire devAsynInt32::interruptCallbackOutput new value=0
2020/03/22 10:16:30.681 13BMDPG1:cam1:Acquire_RBV devAsynInt32::interruptCallbackInput new value=0
2020/03/22 10:16:30.682 asynNDArrayDriver:writeInt32: function=8, paramName=ACQUIRE, value=0
2020/03/22 10:16:30.682 ADDriver:writeInt32: function=8, paramName=ACQUIRE, value=0
2020/03/22 10:16:30.682 13BMDPG1:cam1:DetectorState_RBV devAsynInt32::getCallbackValue from ringBuffer value=7
2020/03/22 10:16:30.682 13BMDPG1:cam1:DetectorState_RBV devAsynInt32::interruptCallbackInput new value=0
2020/03/22 10:16:30.682 ADSpinnaker::imageGrabTask waiting for acquire to start
2020/03/22 10:16:30.682 13BMDPG1:cam1:AcquireBusyCB devAsynInt32::getCallbackValue from ringBuffer value=0
2020/03/22 10:16:30.682 13BMDPG1:cam1:Acquire_RBV devAsynInt32::getCallbackValue from ringBuffer value=0
2020/03/22 10:16:30.682 13BMDPG1:cam1:DetectorState_RBV devAsynInt32::getCallbackValue from ringBuffer value=0
2020/03/22 10:16:30.682 13BMDPG1:cam1:NumQueuedArrays devAsynInt32::interruptCallbackInput new value=2
2020/03/22 10:16:30.682 13BMDPG1:cam1:NumQueuedArrays devAsynInt32::interruptCallbackInput new value=1
2020/03/22 10:16:30.683 13BMDPG1:cam1:NumQueuedArrays devAsynInt32::getCallbackValue from ringBuffer value=2
2020/03/22 10:16:30.683 13BMDPG1:cam1:NumQueuedArrays devAsynInt32::getCallbackValue from ringBuffer value=1
2020/03/22 10:16:30.683 13BMDPG1:cam1:NumQueuedArrays devAsynInt32::interruptCallbackInput new value=0
2020/03/22 10:16:30.683 13BMDPG1:cam1:NumQueuedArrays devAsynInt32::getCallbackValue from ringBuffer value=0
2020/03/22 10:16:30.777 PG1 addr -1 queueRequest priority 0 not lockHolder
2020/03/22 10:16:30.777 PG1 addr -1 queueRequest priority 0 not lockHolder
2020/03/22 10:16:30.777 PG1 addr -1 queueRequest priority 0 not lockHolder
Error (511,511) PV: 13BMDPG1:cam1:TriggerOverlap ReadOut

2020/03/22 10:16:30.777 PG1 addr -1 queueRequest priority 0 not lockHolder
Error (511,511) PV: 13BMDPG1:cam1:TriggerOverlap ReadOut
*****************************

The detector is hung up at that point and I need to restart the IOC.

My question is what does this error mean and where does it come from?  I always see the message twice.

Error (511,511) PV: 13BMDPG1:cam1:TriggerOverlap ReadOut

I don't think it comes from areaDetector or asyn because those messages are all done with asynPrint and have timestamps.  It cannot be from the vendor library because it knows about the PV name.  So I am guessing it must come from base (7.0.3.1)?

This problem only happens when I am running the detector fast, 100 frames/s or more.  It does not happen at 50 frames/s.

Thanks,
Mark



Replies:
Re: Error (511,511) Michael Davidsaver via Core-talk

Navigate by Date:
Prev: Re: write to a single element of an array field Ben Franksen via Core-talk
Next: Re: Error (511,511) Michael Davidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
Navigate by Thread:
Prev: Build completed: EPICS Base base-3.15-562 AppVeyor via Core-talk
Next: Re: Error (511,511) Michael Davidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020