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  2016  2017  2018  <2019 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
<== Date ==> <== Thread ==>

Subject: ADPICam driver observations on Linux
From: Jörn Dreyer via Tech-talk <tech-talk@aps.anl.gov>
To: tech-talk@aps.anl.gov
Date: Wed, 10 Apr 2019 14:19:30 +0200
Hi ,

I just made some observations concerning the ADPICam driver under Linux. After 
PrincetonInstruments came up with a Linux version that supports the USB based 
PIXIS cameras (version > 5.x.x) I ported the ADPICam driver to Linux to read 
out a PIXIS 256E camera.  Here is what I observed:

1) If the camera is connected the driver detects it at startup via 
Picam_OpenFirsCamera(). Then it sets up the auto discovery functionality of 
the Picam library. This leads to two calls to the piHandleCameraDiscovery 
function, once with action 1 (Found) with camera Id 0 -> "Pixis Series" and 
another time with action 2 (Lost) with camera Id 28 -> "Pixis 256E".  That 
leaves the list of availableCameras with an entry of 0 ("Pixis series") which 
is unusable.

2) If I unplug the camera from the USB bus and plug it in again, it is 
detected correctly and can be used!

3) If the camera is connected to an USB 3.0 bus it is not detected at all.

4) It I remove from the ADPICam constructor the complete block that opens the 
first camera or a demo camera, everything is working properly. Event if the 
camera is connected to an USB 3.0 bus!

I'm in contact with the tech support at PrincetonInstruments and they are 
looking into the problem. Has something similar been observed under Windows? I 
do not have such a system for development and tests available.  
PrincetonInstruments would be interested to know if the same problem occurs 
also under windows. If someone could do a test and report I would forward the 
information to PrincetonInstruments.

Regards,

Jörn 




Navigate by Date:
Prev: Re: limit switch fields in the motor record Davis, Mark via Tech-talk
Next: Sequencer segfaults when using put completion with no access to PV Konrad, Martin via Tech-talk
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
Navigate by Thread:
Prev: Data logging VASU PADSUMBIA via Tech-talk
Next: Sequencer segfaults when using put completion with no access to PV Konrad, Martin via Tech-talk
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
ANJ, 10 Apr 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·