Hello,
I'm currently setting up a system that uses a PrincetonImaging PIXIS camera.
As these cameras use an USB interface I have to use the latest version of the
PICAM library (5.1.2) from Princeton.
With this library the driver connects at startup but looses the camera during
the initialization phase. In the hardware setup routine the driver registers a
callback function for the PICAM_Discovery mechanism. This function seems to
loos the communication over USB with the connected camera if another thread
talks to the camera.
Has anybody else observed this behavior? I could get around this problem if I
comment out the calls to the PICAM_AdvancedRegisterForDiscovery function.
But then the driver is only able to use the first detected camera. If I would
connect two, I can not select the one I want to use.
Regards
Jörn
- Replies:
- Re: ADPicam problem Engbretson, Mark S.
- Navigate by Date:
- Prev:
RE: Stream device does not recognize a custom record type Abdalla Ahmad
- Next:
Re: Stream device does not recognize a custom record type Dirk Zimoch
- 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
- Navigate by Thread:
- Prev:
CSDataQuick 1.1 Release Wang Xiaoqiang (PSI)
- Next:
Re: ADPicam problem Engbretson, Mark S.
- 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
|