I had a flawless run last night with one exception. Poor guide star loss recovery. After losing the guide star, to some stray cloud coverage for a few minutes, EKOS hunted around for a new guide star until the stars reappeared. The result was that at my 2000mm focal length the object was now in the upper right corner of the frame, and guiding resumed. 2/3 of an entire nights images were now off center.
My feature request is that guide star loss should trigger a slew/solve to the object, and once centered, guiding should resume, and then imaging should resume. If cloud coverage still exists, slew/solve will continue until it gets confirmation of a centered object.
Oh good, Glad I'm not the only one. This has happened to me several times. There's supposed to be some light clouds come in tonight around 2am. Hope I can successfully get past them...If they're thin enough, I can guide through it. But if the guide star disappears, then I'll lose all the frames.
Not wanting to disappoint you Steve, it's probably not your English (Louisiana? ...), but universally short attention span.
That request is actually being made every few months. I had done so as well some time last year, I think, and as I recall Eric did respond along the same lines as Jasem did: This is very hard to do the way the scheduler is currently structured.
But this would also be my number 1 request.
When I brought that up with Wolfgang a while back, he suggested programming repeated scheduler jobs with short image sequences for the same target. That way, realignment would happen multiple times during the night. Unfortunately, also when not required, which beats the purpose as well.
I guess the problem lies in realigning upon guide star loss and then NOT restarting, but resuming the interrupted image sequence.
PS: But what I am wondering whether that might be possible is to include an option that terminates the scheduler upon guide star loss, but then immediately restarts it. If in the scheduler the option 'Sequence completion' is checked, then the scheduler should just resume where it stopped previously. I mean, I can manually do the same thing, all I need to do is click the Stop button in the scheduler and then restart it. Can this option not be included in the code?
Atlas Pro AZ-EQ, ASI1600MM-Pro, ASI120MM-S, ES102ED, WO-Z61, Nikon D3300, ASI-EFW, ZWO LRGB,Ha,O3,S2 filter set
Is this a new feature you highlighted? I only see restart alignment on guiding calibration failure. When a guide star is lost does the system attempt to restart guiding calibration? Is that why the mounts moves the object off alignment? Maybe I just need to enable this existing feature?
Thanks for clarifying. I only assumed that upon guiding failure, calibration did not restart again, and that the system just aimlessly searched for a new star until it found a suitable one to resume guiding.
please be patient, no, it's not available currently, but I'm working on it.
Currently there is only an option available to re-align when an error occurs during guiding calibration. I.e. if you select the option "Restart Alignment on Guiding Calibration Failure" and guiding calibration fails, it repeats the alignment before re-starting the guiding calibration.
What I am working on is a more general version. The intention is, if guiding aborts and the new option is selected, a re-alignment is issued before re-starting the guiding.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10
Yes, I think it is -even more- important to realign after guiding failure. If not, you can often find your image is displaced a hundred pixels or more as e.g. a cloud has passed and another guide star has been chosen with drift in between.
Please don't hesitate to throw anything this way should you need code testing in the field.
Cheers and clear skies,