Major INDI Library release v1.9.0 bring significant internal changes championed by @pawel-soja to modernize core INDI Library drivers and clients. New drivers for DeepSkyDad Flat Panel & Pegasus devices plus further improvements to PCM8 drivers.
I'm currently using an Atik 414 for science imaging and an ASI-290MM for guiding.
However the FOV is very small and the astrometry rarely solves.
So I want to add an ASI-120MM-S attached to a 50mm scope for astrometry solving.
That means 3 cameras in the setup (although 1 only used for astrometry). Will this work with Ekos/INDI?
I would like to run two cameras simultaneously and have the third for guiding. Connection is ok, I can talk to all cameras, set sequences and get pictures. But how to run two sequences in parallel?
Sorry, if this is obvious and I am just too blind to see But I could not find a reference to this.
I have actually managed to do exactly run two DSLRs (450D AND 550D) simultaneously as suggested by Jasem using two instances of Kstars locally on a machine.
The first instance has the mount, guider and 450D on my Skywatcher 120ED and the 2nd instance just runs the one device (550D).
I uncheck guiding deviations on the second instance and it essentially runs the same schedule as the first instance. I have tried 5 seconds delay between subs and haven't seen any noticeable degradation with the camera shutters firing at different times.
The next session I am going to run dithering with more delay between subs to allow the first instance to do it's thing and then by the time it's done the second slave instance should be firing in time to allow capture without any movements since that has been accomplished by the first instance. Hope that makes sense.
I am using an ACER r3710 dual core pc and it can handle all processing with two cameras simultaneously. A true testament to the work everyone has put i INDI because in the past i tried two instances of AstroPhotographtTool (APT) programs and my i7 laptop struggled controlling two the two cameras.
Also, I don't have the fits previews running because i don't want to burden the slow ACER nettop too much.
Thanks for your experience. As a quick test, I just launched a second instance of KStars on my Pi3B and it worked, although not yet doing guiding or even connected to a scope/mount. But it worked at least in this test with an ASI1600 and a 183 without any problem, all frames were saved. Can't wait to test it under real conditions
if dithering is active, does the sequencer wait for settling after dithering between exposures or must this be done by delay time?
Or is the guidemodule sending some "dithering performed and settled" signal for the sequencer is listening to? Is it like this with external guiders?
If one session of ekos is mastering the guider and scope and other sessions just listen to that guider saying "dithering ok", than the sessions would be synced and multicamera operation was easy.