In fact I was _about_ to suggest the same thing, it seems flashing them with the "compatible" firmware solves the problem somehow.

You still deserve a big "Thank You" for the suggestion

I just noticed this on ASIs website:
*Notes 1: Our USB2.0 camera is not compatible very well with Mac OSX & Linux. USB3.0 cameras is recommended for Mac & Linux users and fully compatible with USB2.0 host.this thread may help you if you want to try our USB2.0 cameras on Mac OSX.

Maybe this have something to do with the problems we are experiencing...

They state on Zwo foruns : "there is some computer can't install the driver properly.
so no image can be shown. then need to flash the compitable firmware if such problem happen."
Has I could understand it has something to do with USB bus type/speed.
It seems the "compatible" firmware reduces the frame size resulting in slower USB2 transfer.

I have two ZWO cameras ASI120MC-S and ASI034MC, the ASI120MC-S works fine but ASI034MC exposure goes in loop.

I am using Kstars bleeding on Fedora 25 x86_64

Cheers!

Did you update the firmware with the -compatible firmware?!

I use ZWO ASI120MM camera and have the same problem with exposure looping (even though I flashed it with compatible firmware).

When I was using it (or trying to use it actually) recently I noticed that the issue is directly related to sharing USB connection with other devices.

If you connect a camera only it works without problem. If you connect a camera while other devices are connected it loops indefinitely. In my case it is my mount (eqmod) connected to USB with FTDI converter that does not let the camera finish capturing an image. When I disconnect the mount (not physically, it's enough to disconnect a mount in indi driver tab) while in the loop, the camera leaves the loop and finishes capturing the image. When I reconnect the mount the camera gets back into the loop.

I tested it on Banana Pi and Raspberry Pi - both have USB ports connected to internal USB hub. Using external powered USB hub does not change anything.

Interesting part of this experiment is the fact that just disconnecting a mount by software (indi driver tab) changes the camera behaviour. It would suggest that the root cause might be sitting inside indiserver or asi driver that gets into a conflict with other _active_ devices connected to USB.

Could anybody confirm that disconnecting other devices (especially mount) let a camera leave the loop and capture images?

I haven't upgraded the firmware yet, will give it a go tonight.

Thanks

My looping exposures was fixed by flashing with the compatible firmware. I had to do this even for a camera which worked 6 months ago with the original firmware.

My ASI keeps crashing my RPi so I need to power cycle, Now I have tried to disconnect all other devices and the RPi have not crashed since! It does, however, still have problems with short exposures but it does not seem to crash the Pi completely as when my Meade DSI is also connected (but not loaded in indi!). It could this time be fixed by restarting indi.

There seems to be something seriously wrong with either my setup, the RPis USB management or the asi driver. A google will show that others are having trouble with the Pi's and usb devices

Upgrading firmware with -compatible worked

Thank you

Started happening me again just now this evening. First clear night in ages and this happens.
I've already flashed with the 'compatible' firmware a couple of months ago....
I'm ready to put this ASI junk in the bin !!!

UPDATE: I plugged in and out the USB cable from the camera a few times to clean any possible dirt on the contacts.
After doing this I was able to take 1 image with just the ASI driver connected. So I connected all other drivers to start work and bang, the looping started again...

I wonder if this is hardware issue or software. Does it work under Windows? or same issue?

I'll do some testing over the weekend when I'm back home at the observatory. The desktop PC its plugged into is not running windows but I'll see what I can discover with a windows 10 laptop connected. Will also try different cables.

One change that I did make since I last used the observatory was that I changed the USB plug that the scope is plugged into...
On this PC (HP elite desktop) there are 4xUSB2 at the front and 5or6xUSB3 at the back. The ASI is plugged into the front of the PC's (USB2).
The scope was plugged into the back of the PC but now is plugged into the front, sharing the internal hub with the ASI.
I'm *guessing* here but I think the ASI does not like to share a hub with anything... I'll see what I can find.

D