Hello Chris, your video is exactly what I tried to do for my next hosted dual setup project. Do you have a link to download your templates? Thanks so much for this video. Joseph
Easy, if you use a separate guidescope, they do not impact each other.... but if you use an OAG, then the AF routine can affect tracking and you may lose a sub on the other system... a small price to pay
I tried this last night and it failed miserably. Both sequences (2 instances of NINA) simply ignored all "synchronized wait." If I started the "leader" first it would not stop anywhere until I stopped it when it starting the imaging sequence. If I started the "follower" first. It wanted to plate solve and couldn't even find ASTAP. I tried with the same target defined in both sequences and also tried with no target specified (except an angle if rotation) in the "follower" sequence. I followed your step by step approach in your video. I am at a lost.
Hi Chris - in your MAIN and SECONDARY instances I see you have an AF after Temp Change in BOTH under triggers - how does that work for you as they are not wrapped in any sync? Do you find that when the AF is triggered that both instances know? - I am trying to use AF after HFR increase but really can't see how it would work ...thanks for any advise
An Af takes about a minute. They are independent. The sync command waits for them to catch up for the next round of exposures after dither. Small price to pay overall. I get about 90% efficiency with the second system in practice
Naïve question: It waits for the moon angle on both instances of NINA with, as you say, identical parameters. But would it be enough to wait on moon angle on either one, since you have a synchronized wait at the top of the instructions for both instances?
There is a timeout in the plugin setting for the sync wait. I prefer to play it safe so that both sequences mimic each other so there is less chance of a timeout occurring for some random delay on one side. In the case of the moon angle, it might pile into image in say RGB on one side but skip it on the other.
Sorry missed this one. The moon angle is not a wait, more like a decision on what will be imaged. The NB and RHB filters use different parameters and find useful to tie up with what is being imaged
That is a lot of synchronized wait commands? I was under the impression that one synchronized weight will do the job for all of them ? For example, how would you manage a triggered auto focus function? Those can happen individually and at anytime ? I’m about to start my synchronized dithering journey
Yes. I do it all the time. The registration process in PixInsighr manages it. Just choose a single reference and run the WBPP script on all your lights.
Fantastic Chris, thanks so much for putting this together!
Terrific, thanks Chris
Hello Chris, your video is exactly what I tried to do for my next hosted dual setup project. Do you have a link to download your templates? Thanks so much for this video. Joseph
When 'Center after drift' kicks in, how do you stop the slave? Mine just keeps imaging, obviously with trailed results.
yep - that is the one gotcha. A small price to pay for almost doubling up imaging hours.
@@astroshed Ah ok, so no workaround for that one then. Oh well, I'm running 3 lenses, so I guess I can afford to lose a frame here and there! 😁
Can you set them up so that the eaf routine doesn't interfere with one another?
Easy, if you use a separate guidescope, they do not impact each other.... but if you use an OAG, then the AF routine can affect tracking and you may lose a sub on the other system... a small price to pay
I tried this last night and it failed miserably. Both sequences (2 instances of NINA) simply ignored all "synchronized wait." If I started the "leader" first it would not stop anywhere until I stopped it when it starting the imaging sequence. If I started the "follower" first. It wanted to plate solve and couldn't even find ASTAP. I tried with the same target defined in both sequences and also tried with no target specified (except an angle if rotation) in the "follower" sequence. I followed your step by step approach in your video. I am at a lost.
There may be several things at play here - best to post your sequences on the Discord forum where we can take a closer look
I did. Look me up under Tempus Fugit in sequencer2-discussion discussion. Thank you!
Hi Chris - in your MAIN and SECONDARY instances I see you have an AF after Temp Change in BOTH under triggers - how does that work for you as they are not wrapped in any sync? Do you find that when the AF is triggered that both instances know? - I am trying to use AF after HFR increase but really can't see how it would work ...thanks for any advise
An Af takes about a minute. They are independent. The sync command waits for them to catch up for the next round of exposures after dither. Small price to pay overall. I get about 90% efficiency with the second system in practice
Naïve question: It waits for the moon angle on both instances of NINA with, as you say, identical parameters. But would it be enough to wait on moon angle on either one, since you have a synchronized wait at the top of the instructions for both instances?
There is a timeout in the plugin setting for the sync wait. I prefer to play it safe so that both sequences mimic each other so there is less chance of a timeout occurring for some random delay on one side. In the case of the moon angle, it might pile into image in say RGB on one side but skip it on the other.
Sorry missed this one. The moon angle is not a wait, more like a decision on what will be imaged. The NB and RHB filters use different parameters and find useful to tie up with what is being imaged
That is a lot of synchronized wait commands?
I was under the impression that one synchronized weight will do the job for all of them ?
For example, how would you manage a triggered auto focus function?
Those can happen individually and at anytime ?
I’m about to start my synchronized dithering journey
Can you combine the data from both cameras , even they have different pixel size an?d image scale
Yes. I do it all the time. The registration process in PixInsighr manages it. Just choose a single reference and run the WBPP script on all your lights.