Experimental Physics and
Industrial Control System

Jörn Dreyer via Tech-talk <[email protected]> · 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 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System