EPICS Controls Argonne National Laboratory

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  <20162017  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  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Andor SDK3 issue - AT_WaitBuffer fails
From: "Pearson, Matthew R." <[email protected]>
To: Mark Rivers <[email protected]>
Cc: "[email protected] list" <[email protected]>
Date: Fri, 23 Sep 2016 13:47:43 +0000
> 
> If you restart the IOC does it start working, or so you need to power-cycle the camera?

Hi Mark,

Yes, an IOC restart fixes it (don’t need to power cycle the camera).

Cheers,
Matt
> 
> ________________________________________
> From: [email protected] [[email protected]] on behalf of Pearson, Matthew R. [[email protected]]
> Sent: Friday, September 23, 2016 7:54 AM
> To: [email protected] list
> Subject: Andor SDK3 issue - AT_WaitBuffer fails
> 
> Hi,
> 
> We have an Andor sCMOS Zyla camera and we use the Andor3 support in areaDetector. This uses the Andor SDK3 API to control the camera and read out data. Sometimes we see the Andor3 driver get into a state because the:
> 
> status = AT_WaitBuffer(handle_, &image, &size, AT_INFINITE);
> 
> function always immediately returns with error code 11 (which means AT_ERR_NODATA). The Andor3 driver ends up then calling AT_WaitBuffer repeatedly in a tight loop, causing giant log files, until we exit the IOC.
> 
> The function should block until there is a data frame to read from the SDK, but it doesn’t, which is a problem. I’ve contacted Andor about this (and they asked me to update my SDK version from 3.9 to the latest version).
> 
> Has anyone else also seen this problem?
> 
> When I get chance I’ll try to reproduce it, and also update the SDK. I’m not sure if we can easily recover from this state, without restarting the IOC, but perhaps the Andor3 driver could detect this problem and set the ADStatus error flag. I’ll experiment with that if I can reproduce the problem.
> 
> A bit suspiciously we also see an uncaught exception when we exit the IOC:
> 
> 2016/09/22 19:46:04.402 andor3:imageTask: AT_WaitBuffer, error=11
> 2016/09/22 19:46:04.402 andor3:imageTask: AT_WaitBuffer, error=11
> 2016[Thu Sep 22 19:46:07 2016] /09/22 19:46:04.402 andor3:imageTask: AT_WaitBuffer, error=11
> terminate called after throwing an instance of '[Thu Sep 22 19:46:07 2016] TSDK3Exception'
> [Thu Sep 22 19:46:07 2016]   what():  TDualCLLogicalControl: Error - Sensor halves are not running in unison
> 
> Cheers,
> Matt
> 
> 



Replies:
Re: Andor SDK3 issue - AT_WaitBuffer fails Pearson, Matthew R.
References:
Andor SDK3 issue - AT_WaitBuffer fails Pearson, Matthew R.
RE: Andor SDK3 issue - AT_WaitBuffer fails Mark Rivers

Navigate by Date:
Prev: Re: Andor SDK3 issue - AT_WaitBuffer fails Pearson, Matthew R.
Next: Re: libCAS: variable size array Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Andor SDK3 issue - AT_WaitBuffer fails Pearson, Matthew R.
Next: Re: Andor SDK3 issue - AT_WaitBuffer fails Pearson, Matthew R.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 19 Oct 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·