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: | camserver/NDStdArray latency mystery |
From: | John Dobbins via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 10 Mar 2020 16:38:25 +0000 |
First, apologies because this is about two old versions of areaDetector.
We have two Pilatus IOCs. One is areaDetector R1-9, Base 3.14.8 and one is R2-2 Base 3.14.12.4
Taking single images on the R2-2 version there is a latency of one image in the NDStdArray which is sent to Channel Access. The image is also being written to a file and that receives the latest image however the file is being written by camserver (tvx-7.3.13-121212).
Note that these are manually triggered images, rate is not an issue.
It is possible that the IOC is received a delayed image from camserver.
How can I determine if the latency is between camserver/IOC or within IOC?
John Dobbins
Research Support Specialist
Cornell High Energy Synchrotron Source
Cornell University
www.chess.cornell.edu
|