Not specifically the answer you're looking for but from what I read you are setting up an All-Sky camera, using Ekos and Indilib. You may be interested in a self contained All-Sky camera that does not use Ekos and Indi, such as the one presented by Thomas Jacquin on github.com/thomasjacquin/allsky .
His All-Sky can make use of diverse cameras such as: Raspberry Pi HQ camera, ASI120MC*, ASI120MM*, ASI120MC-S, ASI120MM-S, ASI224MC, ASI178MC, ASI185MC, ASI290MC, ASI1600MC, and are controlled by a Raspberry Pi. It may or may not satisfy your specific requirements but it may be worthwhile to take a look as it allows setting many operation parameters.
Gille, Looked at that link you sent. It is a very well done project. Congrats to the authors.
But, not for me at the present time. As I stated earlier, this project is a baby step before moving KStars/Ekos to the full imaging setup. If I can't do the most basic task of getting X number of exposures, I need not go further.
Thanks for your time! Might have to revisit that later.
Ok, while running a test with a different cable, the Ekos camera tab was reporting exposures being taken and stored, when in fact they were not. The fits viewer also froze at the actual last picture stored (about 248 out of 1000 target). The image folder on the thumb drive also reflected the 248 number.
Can only conclude there is coding issue/bug with the ZWO driver/Ekos since it fails:
- on 2 different pi's with old and latest updates respectively.
- 3 different USB drives and the OS SD card
- on local storage only, but works with remote storage.
- with two different ZWO cameras, 120 USB 2.X and 294 USB 3.X
Time to buy a mini-PC. Something I was hoping to avoid.
Thanks for all the inputs folks!