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: AreaDetector: Virtual camera selecting from different hardware cameras |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, "Blomley, Edmund (IBPT)" <edmund.blomley at kit.edu> |
Date: | Wed, 2 Aug 2023 12:16:46 +0000 |
Hi
Eddy,
Here are a couple of solutions that just switched where the plugins get their data. This requires that you run all 3 cameras in the same IOC.
If you want a separate virtual camera then the following will work with the 3 cameras in separate IOCs, each with its own set of plugins.
Mark
From: Tech-talk on behalf of Blomley, Edmund (IBPT) via Tech-talk Sent: Wednesday, August 2, 2023 5:36 AM To: tech-talk at aps.anl.gov Subject: AreaDetector: Virtual camera selecting from different hardware cameras Hey,
So let’s assume we have an injector with a couple of fluorescent screens which can be moved in and out of the beam path. Each screen has its own camera, integrated via AreaDetector: - CAM:SCREEN:01 - CAM:SCREEN:02 - CAM:SCREEN:03 - ... Now, as it only makes sense for a single screen to be „active“ at any given time, I wonder if it is possible to set up a virtual camera with AreaDetector which gets the datastream dynamically from one of the hardware cameras (depending on an external PV): - CAM:VIRTUAL: So that depending on which screen is active, CAM:VIRTUAL: will get the camera data from either CAM:SCREEN:01 or 02 or 03. Cheers Eddy |