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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Mako G-234B (6408) - Prosilica Area Detector question |
From: | Mark Rivers <[email protected]> |
To: | "'[email protected]'" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Fri, 9 Mar 2018 18:07:11 +0000 |
Hi Mark, I have never seen that problem. It seems strange that with PixelFormat=Mono8 it would be reading in 12-bit mode. Can you set that to 8-bits with their Windows GUI software?
And if so does it revert to 12 bits when you power-cycle the camera? It would probably be a good idea to expose the SensorReadoutMode feature in the EPICS driver. It would also be a good idea to write a new driver based on their Vimba SDK, rather than old PvAPI SDK we are currently using
J Mark From: Mark Engbretson [mailto:[email protected]] Mark, I recently deployed a GigE camera Mako G-234B from Allied Vision with the Prosilica Area Detector but noticed a bit of oddness with the expected frame rate. The camera data sheet lists 41.2 FPS as the readout rate,10-bit sensor readout
but the Xml file from the camera shows feature(s) of <Feature Name="AcquisitionFrameRateAbs" Type="Float" Access="R/W">31.872511</Feature> <Feature Name="PixelFormat" Type="Enumeration" Access="R/W">Mono8</Feature> <Feature Name="SensorReadoutMode" Type="Enumeration" Access="R/W">Readout12Bits</Feature> Which is the frame rate which Area Detector seems to acquiring at. I am assuming that I would have to implement “SensorReadoutMode” to be able to get the expected FPS, or am I missing an existing parameter that might already do this? Me |