Created attachment 106238 [details] KStars log This is in KStars 2.7.8 for Windows. While testing meridian flip, I observed Ekos initiating an exposure while the mount was still slewing. (timestamps kept in UTC) Scenario is: - Track alpha Coma Berenices, RA=13.1804 DE=17.4407, starting at 18:53 - At that moment, alpha Coma Berenices is 6 minutes from the meridian - Setup 8 exposures using the Ekos Scheduler, uncheck Track, Focus, Align, Guide, Alt and Twilight, using prepared sequence of 1x120s exposure, meridian flip if HA>0. - Start scheduler, and wait for the meridian flip to occur and check Ekos behavior Observed: - 19:00:33 At the end of the second exposure, Ekos sends new coords to mount because the HA exceeds 0 (0.02h) - 19:00:37 Ekos restarts exposure, but mount is not done slewing (exposure is therefore being corrupted) - 19:01:31 Mount finishes meridian flip - 19:02:37 At the end of the third exposure, Ekos sends again new coords to mount because the HA exceeds 0 (0.05h), apparently the previous meridian flip wasn't taken into account - 19:02:38 Mount is done slewing - 19:02:41 Ekos restarts exposure To summarize, first flip request is not waited for, and an unexpected second flip request occurs, which is waited for.
Created attachment 106239 [details] EQMod mount log
Created attachment 106240 [details] Ekos console log
On hold since much has changed in INDI/Ekos during that year. I'll provide more information later on.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Considering reported, to be kept.
Is this issue resolved with 3.0.0?
Probably not. I'll test this during January if weather agrees.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!