After the last updates my ASI120mm enters an exposure loop and never ends the actual exposure.
As it reaches 0.25s it loops again and I cant get an image. Anyone suffering from the same issue?

I have just found the solution:

indilib.org/forum/ccds-dslrs/1482-asi120...tus-failed.html#9961

Flashed the Compatible Firmware and it's working again. Thanks Adam.

Hello,

i was using the asi120MM for several months without any problems. But now after an update of Kstars, Ekos and libindi as well as all 3rd party drivers I get the same loop problem. The funny thing is that the problem only appears with local connection to my laptop and my desktop computer both running Kubuntu 16.04. But the problem does not show up with remote connection to raspi (v1B+) where the camera is directly connected to the raspi without any USB hub. I also have to mention that I built libindi and the 3rd party drivers from source on the different devices respectively.

I already tried changing the firmware to "compatible" but the problem is still present.

Anyone got an idea of how to fix this?

I think ZWO latest SDK broke the driver on x86.. I too don't have problems on Raspberry PI but it would loop on my x86_64 machine.

I tried flashing my asi120 as per indilib.org/forum/ccds-dslrs/1482-asi120...tus-failed.html#9961 and it worked for a while.
However I have since seen in instance of this looping.
For me rebooting the main PC that the camera is connected to and starting everything again seems to fix it. It s a real pain in the .....

There is an updated SDK, I will test it today and if OK I'll commit it.

Hi!

Have this been fixed yet? Just got a new ASI 120MC and PixInsight seems to go into a loop of exposures and never gets an image. The ASI is connected to a Raspberry Pi 2. The camera works fine in windows.

Another "funny" thing... If I start indiserver and indi_asi_ccd and do the following on the RPi

pi@observatory ~ $ indi_setprop "ZWO CCD ASI120MC.CONNECTION.CONNECT=On"
pi@observatory ~ $ indi_setprop "ZWO CCD ASI120MC.UPLOAD_MODE.UPLOAD_LOCAL=On"
pi@observatory ~ $ indi_setprop "ZWO CCD ASI120MC.CCD_EXPOSURE.CCD_EXPOSURE_VALUE=0.1"

then the RPi changes IP address! WT* The RPi is set to use a static address, but the above commands makes the RPi aquire a new address from the DHCP server of the router!

Best Regards,
Søren

I have an ASI120MM and It worked fine yesterday after the last update, but I have it connected to an Atom x86_64 PC, not an RPi.

Thanks for the reply. My "old" ASI120MM does the same thing, PI never gets an image. This camera worked fine with the RPi 4 months or so ago while the 120MC is brand new...

I informed ZWO about this issue so let's see what they can do.

hummmm I remember having some problems with it too when I had it connected to my RPi B+.
Maybe it's only an arm driver issue. Do you have it directly connected to the RPi or an HUB?

Hi again!

It seems that it is working now. I flashed both cameras (the 120MM and 120MC) with the "compatible" firmwares from the ASI website and now they both work fine it seems. Also the RPi keeps its IP address when I run the above commands. Extremely strange, but great that it seems to be working now. Maybe this should be put in a FAQ somewhere?

Best Regards,
Søren