wagenadl / vscope

VScope is a package for acquisition and analysis of voltage-sensitive dye recordings along with electrophysiology.
Other
2 stars 1 forks source link

Error: Could not open camera (Photometrics Prime95B) #1

Open Trende opened 6 years ago

Trende commented 6 years ago

Hello,

I am trying to setup our Prime95B camera with your software. I installed the newest pvcam driver and the camera is correctly installed (we can aquire images with Micro Manager). Unfortunately I get the following error message, when I try to start Vscope.

errorvscope

I installed the 'vscope-1.0.0-x86-setup.exe' and right know I just want to setup one camera. I read in the changelog that you tried/used vscope for the QuantEM and Evolve so far, which use the same pvcam driver. Could you give me a hint which part of the vscope code I have to change to make it work for our camera?

Best regards,

Alexander Trende

wagenadl commented 6 years ago

Hi Alexander,

First of all, thank you for your interest in VScope. I appreciate the error report. The error message is generated in line 34 of "pvpCamera.cpp":

pvpCamera::pvpCamera(QString camname): camname(camname) { pvpSystem(); // ensure system is initialized

int16 hcam; if (!pl_cam_open(camname.toUtf8().data(), &hcam, OPEN_EXCLUSIVE)) throw pvpException("pvpCamera: Could not open camera",camname); camh = hcam; It could mean that some other application is simultaneously trying to access the camera. If that is not the case, it is likely a configuration problem. Can you send me the following:

That should be a good start for finding a solution. I don't expect it will be necessary to change the source code.

Best wishes,

Daniel Wagenaar

On 08/28/2017 03:08 AM, Alexander wrote:

Hello,

I am trying to setup our Prime95B camera with your software. I installed the newest pvcam driver and the camera is correctly installed (we can aquire images with Micro Manager). Unfortunately I get the following error message, when I try to start Vscope.

errorvscope https://user-images.githubusercontent.com/22173860/29767216-ecbca4e2-8be1-11e7-96be-66b8a6f21d70.PNG

I installed the 'vscope-1.0.0-x86-setup.exe' and right know I just want to setup one camera. I read in the changelog that you tried/used vscope for the QuantEM and Evolve so far, which use the same pvcam driver. Could you give me a hint which part of the vscope code I have to change to make it work for our camera?

Best regards,

Alexander Trende

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/wagenadl/vscope/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/ALJ5e1uzA5uLJv77TxjQ2Sq-_SYJA3V0ks5scpG4gaJpZM4PEVB6.

--

Daniel A. Wagenaar, PhD

/Research Professor and Director, Neurotechnology Center/ California Institute of Technology, Pasadena CA, USA

+1 (626) 395-8567 | www.danielwagenaar.net http://www.danielwagenaar.net

Trende commented 6 years ago

Hello Daniel,

thank you for your quick reply. As a side note a bit of background: I'm a PhD student at Jutta Kretzbergs lab at the University of Oldenburg and as you may know we are also doing VSD in leeches. Until now we have used the QuantEM and an older version of Vscope (maybe 0.4...?). It would be cool to test all the new functions in Vscope (e.g. ROI annotation).

Right now Vscope was installed via the the "vscope-1.0.0-x86-setup.exe" from zenodo on a Win10 machine. I can start Vscope correctly if the camera is turned off. Unfortunatley I just see the GUI and no terminal. If it helps I can install cygwin and run the Linux version (or install Linux on the pc).

The RSconfig shows the camera (right now we just have the Prime95b installed)

rsconfig - pmusbcam00

I also attached the _connections.xml. The AD-converter (USB-6229 - the same you are using in your lab?) is detected correctly in Vscope. So far we have just change the serial number and the number of pixels of the camera in the connections.xml (as described in the userguide.pdf). We want to configure the shutter/trigger later after the camera is working.

_connectionsXMLzipped.zip

wagenadl commented 6 years ago

Hi Alexander,

[I thought I had sent this message yesterday, but it doesn't appear on github, so here it is again.]

The problem is likely in this stanza in the connections file:

<camera id="Cc" serno="A17G203011" role="donor" xpix="1200" ypix="1200" lamp="LED" shutter="" focusexpose="200 ms">

<camera id="Ox" serno="A17G203011" role="donor" xpix="512" ypix="512" lamp="LED" shutter="" focusexpose="3 ms">

You are trying to open the same camera twice. If I understand correctly that you are only using one camera, you could simply replace the section with something like:

<camera id="Cc" serno="A17G203011" role="donor" xpix="1200" ypix="1200" lamp="LED" shutter="" focusexpose="200 ms">

(You can name your camera something other than "Cc", of course.

The other critical parts of the file are:

where you are telling VScope that you will connect the "expose out" line from the "Cc" camera to DIO pin 29; and

where you are telling VScope that you will connect the "trigger" line to the "Cc" camera to DIO pin 31, and that DIO pin 7 will activate a lamp to illuminate the sample. (You can make it activate a shutter instead, it makes no real difference.)

Let me know if that helps,

Daniel