All,

I seem to be having some INDI driver stability issues on the latest 3.5.0 version of Kstars when using a ZWO autoguider and a ZWO imaging camera at the same time. Sometimes my imaging camera will stop exposing in the middle of a job for some reason. Last night I left my rig unattended for 90 minutes, only to come out and find that it had only taken 8x 90sec exposures. When I attempted to resume capture, I got the following error:

Error: Image Capture failed after 3 attempts

There are two variations of how these INDI driver issues play out:
1. When I hit Capture, I’ll see the countdown timer count down to zero, but then it will abruptly reset. So if my capture time is 90 seconds, it will count down to zero, then go back to 90 seconds again without displaying the image. It will try this 3 times and then display the error shown above.
2. When I hit capture, the countdown timer will go down to zero, but then it will get stuck on “Downloading...”. I am directly connected to the camera via USB 3.0, so this is not a wireless bandwidth issue.

I can temporarily fix the problem by disconnecting and then reconnecting the camera in INDI control panel, but it always comes back. I tried to enable INDI logging by pressing the “Debug Enable” button in the control panel, but it immediately goes back to being disabled again.

When researching this problem, I found a thread that suggested that connecting the camera to an unpowered USB hub could be the cause of this. I purchased a powered hub, but this problem persists.

Any ideas?

Read More...