Last night kstars crashed during an acquisition session
I restarted it, fired up EKOS and connected again (it is set up to use web manager on a remote machine). All devices came up still in proper state, i.e., the CCDs had their cooling point active, the mount had proper coordinates and was tracking. So I started guiding, and then continued the capture sequence (after setting it up again - this is only capture, not via scheduler). Everything worked nicely, until:
some 50 minutes later, a filter change was on schedule. The system is set up to do an AF run on filter change. That did
not happen. It only applied the specified filter offset, without running AF. I aborted the capture, and manually triggered the AF. Then I continued.
On the next filter change, the AF run was done automatically.
Question: Does the automatic AF on filter change only happen if the
current instance of EKOS had done an AF run before? If so, is this intentional, and why?
Next problem occurred later in the night when the meridian flip was supposed to take place. It did not happen, although it was activated in the mount tab (6 minutes after crossing). So instead, the mounts 'safety limit' setting did the flip 20 minutes later. Of course this aborted the guiding (and thus the whole acquisition).
Question: Does the MF only happen if the current instance had done a plate solve before? Or are there other reasons why MF wasn't done?