Good news, my test cases could reproduce the behavior that Sergio reported here. The explanation is the following:
If focusing is running when a meridian flip is ready to take place, the meridian flip starts and aborts focusing - that's how we expect it. Next, capturing aborts due to an aborted focusing - that might be right in other situations, in the case of a meridian flip that's wrong.
Subsequently, the scheduler obtains a capture failure and - depending on the error strategy, will react. Keep in mind, the meridian flip is still running. If the scheduler is configured to restart an aborted job, the first step is to slew to the target - which creates the error message that the meridian flip has failed.
The solution is quite easy: do not abort capture when focusing fails during a running meridian flip. It's already present in the merge request and needs to be tested thoroughly, but I'm quite confident that we could solve this case quite soon.
OK folks, this issue should be fixed with the merge requests
MR371
and
MR378
. For those who know how to build KStars from sources, check out the latest version from the repository.
The behavior now is as expected: if focusing is running when the mount is ready for a meridian flip, focusing will be interrupted, the focuser moves back to the initial position and the meridian flip takes place. As soon as the meridian flip is over, focusing will be restarted.