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: | RE: ADPilatus |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | 'John Dobbins' <john.dobbins at cornell.edu> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 6 Oct 2020 15:49:32 +0000 |
Hi John, What ThresholdEnergy were you using when Energy was set to 20 keV? What happens if you set ThresholdEnergy=10 and Energy=20, does that generate a bad flat field? Prior to R2-3 ADPilatus does not send the energy to camserver, it only sends the ThresholdEnergy. However, in this case camserver is supposed to automatically set the energy to ThresholdEnergy*2. If you set ThresholdEnergy=10 camserver
should thus set energy to 20, which is equivalent to what I suggested above. Does that generate a bad flat field? In the newer version of ADPilatus if you set Energy=0 then the energy it sends to camserver is ThresholdEnergy*2. If you are getting bad flat fields with reasonable values of Energy and ThresholdEnergy then would seem to be a bug in camserver. Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of John Dobbins via Tech-talk For the record: The root of the problem appears to be that the new IOC contains a record (added in R2-7) for the x-ray energy, $(P)$(R)Energy which did not exist in the
previous IOC. The default value for this record is 20 KeV. This value is used by camserver to generate a flat field correction file. On this Pilatus at least, the value 20 KeV generates a bad flat field correction
file. Thanks to Mark Rivers for his help in debugging this. John Dobbins From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of John Dobbins via Tech-talk All, We have a number of DECTRIS PILATUS detectors for which I recently added an up-to date areaDetector installation. Previously these detectors were using areaDetector R1-9-1, EPICS Base R3.14.11 I added areaDetector R3-9, EPICS Base R3.15.8 These are the three detector and their tvx versions - note that the 100K tvx version is different. PIL 100K tvx-7.3.13.121212b PIL 200K tvx tvxe-7.4.01-130212 PIL 300K tvx tvxe-7.4.01-130212 The 200K and 300K are working fine with the new software, however the 100K is not. The image from the PIL 100K looks like this: The first 26 rows appear fine, i.e. pixels typically show tens of counts, then in row 27 pixels with very large numbers and pixels with zero start appearing. Neither the IOC nor camserver is reporting errors. The PILATUS 100K continues to work as expected with the old areaDetector installation. Any ideas on how to proceed? Regards, John Dobbins Research Support Specialist Cornell High Energy Synchrotron Source Cornell University |