In my case, when a cloud hides the guiding star for seconds and not appear again, the systems continues guiding sending pulses as much the value in Maximum pulse. This cause that the telescope move out the field, and then I need to stop the schedule (or the plan) and run the platesolver to center it again, or restart the Scheduler
I was not attending EKOS when this happened with the images from 20-25 as given by example, but I have seen the guide totally stop and resume again trying to find a guide star. To be sure, I have attached the log file generated and clipped it only to the events between generation of img020 till img025.
Thank you. Capture was never aborted. The guide module was trying hard not to fail so it kept waiting for stars to show up. When they did, it ended up picking another star and therefore the whole target was off. At least, that's my theory. I suggested to the devs that in such situation when the scheduler is running, it should elect to stop the whole process and restart alignment/guiding/capturing flow to ensure all is in order.
Thanks @jasem, I think you are right in your theory. Below are my findings that match yours. The question is when we can get this update (when losing guide star go to plate solving and restart guiding)?
C9.25 f/10, HEQ5, MyFocuserPro2, OAG, ASI174MC guide, ASI533MC Pro
@Mohamed: Thanks for that analysis. I believe you are correct that there is a bug here in the guider, your annotations help, and I have a theory about what is happening. Let me look into it a bit more, and I'll get back.
@Alessandro: I think it is changing guide stars on the fly, but I believe the problem is that it is not communicating that well to the guider.
In any event, it's best that I look more carefully into it without guessing and get back to you.
I had added a draft merge request that may fix this. invent.kde.org/education/kstars/-/merge_requests/507
This is pretty raw, and I can't test until skies clear up. Tomorrow night is possible,
but I'm not sure. Weather has been pretty marginal around here for a while.
@Mohamed (or others who are also capable): if you want to test, that would be great, but you need to be comfortable with git and compiling KStars.
It is not submitted, so you'd need to get it from my forked repo, doing something like this:
In a new directory, if you are good at getting code off of git repos, and want to test this, then
"git clone invent.kde.org/murveit/kstars.git
and go to the guider-fix15 branch (git checkout guider-fix15), and setup compilation using cmake and compile that and run the new KStars binary.
This code is at the current KStars HEAD plus my new changes.
You would just run SEP MultiStar guiding the way you've been doing.
The new code probably won't trigger unless the skies are poor, like the ones you've been testing with.
Here is your new code from the git yesterday. I'm not sure how I'd test, it but here's the log anyway: drive.google.com/file/d/1BAUAv4ItJ-mWO0Y...DT-/view?usp=sharing
All goes well until right at the end where indi closed the session. I had to go back to the stable version to finish it but I don't think it's the guider which caused the shutdown...
Oh, and MANY congratulations to whoever smoothed the guiding plot in the guide tab from those dreadful square waves:)