Latest Kstars - When mount fails to autofocuss in EKOS it hangs and seems to prevent a scheduled meridian flip from occurring. The result is scope keeps tracking until it hits the mount We need something that always prioritises the meridian flip over another module completing something first.
I concur, though that happened to me with the manual cover pop-up mechanism. We must find a way to keep the capture state idle until an exposure really starts, because meridian flip is not prioritary over that state. Or add operational timeouts at multiple levels. Or consider meridian flip like an observatory weather emergency : after all, not flipping is a safety concern.
That last idea seems best to me: the mount module should report the need for a flip, then past a second HA limit notify a forced flip, eventually aborting whatever procedure is running elsewhere. This does not fix the reported issue indeed, but takes care of the induced safety issue. Opinion?
I am in favour of the last option you mentioned. I would add a configurable timeout to the mount tab and an option to enforce a meridian flip after a certain delay. With this we leave it to the user whether a meridian flip might be executed even at the price of lost images.
I also favour the last option except for one situation in the "eventually aborting whatever procedure is running elsewhere" case: currently taking an image should NOT be aborted and the meridian flip should be done as soon as the image is done
Currently, re-focussing is part of imaging. That‘s why this case slipped through. But you will get the option enabling a forced meridian flip. In your case I would recommend not selecting it.
Sorry i know we should supply logs but none were enabled, but needed to bring to your attention. I will enable logging as it will likely happen in the next few nights again. I should note that indi is on a raspberry pi4 using raspbian buster compiled from sources from only 4 days ago and ekos is on a remote computer using ubuntu ppa.