Pomidaq not connect to DAQ under linux

[Michael Graupner]

Hello, 

I managed to compile and install pomidaq on my laptop running Ubuntu 20.10 (Thinkpad X1 Carbon 6th Gen). pomidaq starts and works properly but the image displayed appears to be some random noise. Whether the DAQ is connected or not doesn't change the behavior of pomidaq (DAQ v3.3 with Miniscope V4). 

Which additional steps are required on linux to get pomidaq to connect to the DAQ? 

Thank you very much for your help in advance.

Cheers,

Michael 

[Richardson Leão]

Did you do a dmesg to see if the camera is connected? Try to use other software to acquire miniscope as a webcam (micromanager). Lsusb?

--
You received this message because you are subscribed to the Google Groups "Miniscope" group.
To unsubscribe from this group and stop receiving emails from it, send an email to miniscope+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/miniscope/2e7b4550-4627-415b-92e4-d388dcea24f7n%40googlegroups.com.

[Michael Graupner]

Dear Richardson, 

Thank you for your prompt reply.

Yes, the scope shows up in lsusb : 

 Bus 002 Device 007: ID 04b4:00f9 Cypress Semiconductor Corp. MINISCOPE

And indeed there seems to be an error in dmesg : 

[796596.953970] usb 2-1: new SuperSpeed Gen 1 USB device number 13 using xhci_hcd
[796596.978794] usb 2-1: LPM exit latency is zeroed, disabling LPM.
[796596.979066] usb 2-1: Int endpoint with wBytesPerInterval of 1024 in config 1 interface 0 altsetting 0 ep 130: setting to 64
[796596.979333] usb 2-1: New USB device found, idVendor=04b4, idProduct=00f9, bcdDevice= 0.00
[796596.979337] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[796596.979341] usb 2-1: Product: MINISCOPE
[796596.979344] usb 2-1: Manufacturer: Cypress
[796596.982401] uvcvideo: Found UVC 1.10 device MINISCOPE (04b4:00f9)
[796596.983185] uvcvideo: Failed to query (GET_INFO) UVC control 10 on unit 2: -32 (exp. 1).
[796596.983447] uvcvideo: Failed to query (GET_INFO) UVC control 12 on unit 2: -32 (exp. 1).
[796596.985934] input: MINISCOPE: MINISCOPE as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/input/input108

I am looking into this right now. Does anybody have by any chance an idea whether this error is the source of the problem and how to fix it? 

Thanks in advance. 

Best,
Michael 

[Matthias Klumpp]

Am Do., 4. Feb. 2021 um 16:19 Uhr schrieb Michael Graupner
<graupner...@gmail.com>:

>
> Dear Richardson,
>
> Thank you for your prompt reply.
>
> Yes, the scope shows up in lsusb :
> Bus 002 Device 007: ID 04b4:00f9 Cypress Semiconductor Corp. MINISCOPE
>
> And indeed there seems to be an error in dmesg :
> [796596.953970] usb 2-1: new SuperSpeed Gen 1 USB device number 13 using xhci_hcd
> [796596.978794] usb 2-1: LPM exit latency is zeroed, disabling LPM.
> [796596.979066] usb 2-1: Int endpoint with wBytesPerInterval of 1024 in config 1 interface 0 altsetting 0 ep 130: setting to 64
> [796596.979333] usb 2-1: New USB device found, idVendor=04b4, idProduct=00f9, bcdDevice= 0.00
> [796596.979337] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [796596.979341] usb 2-1: Product: MINISCOPE
> [796596.979344] usb 2-1: Manufacturer: Cypress
> [796596.982401] uvcvideo: Found UVC 1.10 device MINISCOPE (04b4:00f9)
> [796596.983185] uvcvideo: Failed to query (GET_INFO) UVC control 10 on unit 2: -32 (exp. 1).
> [796596.983447] uvcvideo: Failed to query (GET_INFO) UVC control 12 on unit 2: -32 (exp. 1).
> [796596.985934] input: MINISCOPE: MINISCOPE as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/input/input108
>
> I am looking into this right now. Does anybody have by any chance an idea whether this error is the source of the problem and how to fix it?

This looks fine. If this is the same issue as
https://github.com/bothlab/pomidaq/issues/6, looking into the PoMiDAQ
log data may give some clues.
Oh, also make sure to select the V4 Miniscope from the device dropdown
menu (but I guess you did that already ^^)

Cheers,
Matthias

--
I welcome VSRE emails. See http://vsre.info/

[Michael Graupner]

Thank you for your reply. 

Actually, I simply had to explore the Device IDs a bit further. The described behavior occurred with ID 0, and since ID 1 gave an error, I didn't explore further. I could connect with the miniscope using ID 4. Works great.

Cheers,
Michael