Is anybody using successfully an ASI120MM on linux?
I have a Raspberry Pi 3 with Raspbian Jessie, kernel 4.9.13-v7+, INDI 1.4.1 (compiled from github, sha id 32d5623332dad10a64c6db206c4d7d787cd04da1), which includes the SDK v.0.6.0110 into the indi-asi driver.
Running indiserver on the RPi3 with indi-asi, and performing a simple test like hitting "Framing" in Focus tab (just a sequence of images), Exp=1s, Bin 1x1, the camera seems to work well for a few minutes, then got stuck (waiting forever at 'StartExposure->setexp : 1.000s' as seen in indi-asi driver debug log). In dmesg, I see these messages:
[27070.448662] usb 1-1.4: new high-speed USB device number 5 using dwc_otg
[27070.699494] usb 1-1.4: New USB device found, idVendor=03c3, idProduct=120a
[27070.699506] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27070.699514] usb 1-1.4: Product: ASI120MM
[27070.699522] usb 1-1.4: Manufacturer: ZWOptical company
[27070.699529] usb 1-1.4: SerialNumber: 00000
[48180.056128] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg
[48181.566120] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg
[48183.306141] usb 1-1.4: reset high-speed USB device number 5 using dwc_otg
... ("reset" message repeats on each exposure)
To recover, I need to pull out the USB cable and reconnect again.
Interestingly, if I roll back the SDK embedded in indi-asi driver from v0.6.0110 to v0.4.0929 (replacing the libASICamera2 library embedded in indi-asi with the one extracted fromhttp://astronomy-imaging-camera.com ... 4.0929.tar
), the "reset" dmesg messages are gone, and the camera operates for a longer period, but sadly (after say 1 hour, sometimes more), it also gets stuck. The SDK versions in between behaves like 0.6.0110 ("reset" messages on dmesg).
On a laptop with Kubuntu 16.04.4 (x64) running indiserver, I can connect to the indi_asi driver with Ekos, but exposures always fail no matter the version of the SDK, showing "ASIGetExpStatus failed (0). Restarting exposure... " and then "Exposure failed after 3 attempts".
The camera has been tested on SharpCap in Windows and seems to be ok, so I'm discarding hardware failures.
Anyone got this working? If so, can you report your exact versions (OS/platform, kernel, INDI, etc)?
As I can see in the forum, ZWO is recommending the USB3.0 (-S suffix versions). Any report of these working on a RPi3?
ZWO: I see you blame the hw performance of the USB2.0 cameras to explain why these won't work reliably on Linux (viewtopic.php?f=17&t=6668#p11640
). Then why do they work on Windows? (same camera, same computer). It would be great if you fix the linux SDK.
Thanks in advance