SUMMARY There are two modules where it is possible to set the meridian flip : in the Mount Module and in the CCD Module. I find bizarre that when I set a value in one module it's not reflected in the other. I wonder why the increment is 1 hour in one module and 0.1 hour in the other STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: 10.14 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Wolfgang, can you please take a look at this?
In addition to this thread : The meridian flip button in the Mount Module indicates the remaining time before the flip. This is neat. But when the target crosses the meridian, it says "Meridian flip waiting ..." without starting the flip (my setting was "flip = 0.00 hour"). What is the function of the meridian flip button in the Mount Module ? In my hands, I could only use the meridian flip button in the CCD Module.
Jean-Claude, could you please be a little more specific, what the problem is? Here some background how it is built: the meridian flip is controlled by the Mount module. At the same time, in a capture schedule considering a meridian flip can be defined. When values are set in a capture schedule, the values are transferred to the Mount tab as soon as the capture plan has been startet - but not immediately when defining the values in the capture schedule. When a capture schedule is executed, the Mount module takes into account whether a capture is running a soon as the meridian flip limit has been reached. If this is the case, it waits until the next frame has been captured - that's why it signals "Meridian flip waiting ..." So in case you see this message, it behaves as planned - as long as a capture is running. Or wasn't this the case? The only thing what seems to be a bug are the different increments in the two models. Wolfgang
Wolfgang, I will repeat again the test to-morrow morning to provide a clear answer.
I did some tests and here are the results. A capture sequence of exp = 1 min x 1000 was initiated each time. I did the tests with my real equipment connected. 1/ CCD = flip OFF, Mount = flip OFF : result = no flip 2/ CCD = flip OFF, Mount = flip ON : result = no flip (note that flip occurs immediately after stopping the capture sequence) 3/ CCD = flip ON, Mount = flip ON : result = flip Thus - you were right - everything is working as it should ! Yesterday, when Ekos displays : "Meridian flip waiting ...", the scope simulator was doing its job but I couldn't see it because I used the simulator. What I find a bit misleading is that -NOW- the two meridian flip buttons (in the Mount Module and in the CCD Module) behave independently while they should reflect the same thing. What do you think ? Besten Dank für deine Bemühung, Wolfgang !
Well I forgot to test a fourth case : 4/ CCD = flip ON, Mount = flip ON : result = FLIP ONLY if a capture sequence is running ! As I said, I operated these tests in real conditions and I could see that my observatory dome receives the flip signal while the scope doesn't. Thus, when no capture sequence is running and the target crosses the meridian, the scope doesn't flip and the dome flips ... but comes back to its initial position because it is slaved to the scope which didn't flip. I hope this helps.
Oha, OK, never heard that observatories execute a meridian flip :) I will give it a try with a simulator setup, since I do not have an observatory at hand to test it in real life.
I did a lot of testing today with my real equipment and with the simulator. Conclusion : - The meridian flip occurs as expected with the KStars simulator. No problem. - There is a problem though with my mount which is commanded by a Nexstar hand control. When the target crosses the meridian, the mount receives a signal (the scope slews again briefly on the target) but doesn't execute a flip. I tried to check the influence of the 4 Meridian Flip possibilities of the hand control: - Disabled - Favor current - Favor West - Favor East but this didn't really help. I must try again.
A possible explanation is that the time of your mount and that of the device running Ekos are not in sync. The meridian flip relies on the ability of the mount slewing to a point that is meanwhile beyond the meridian, it changes the pier side. When your mount clock is behind, it might think meridian has not been crossed yet.
I checked that my computer and the mount are synchronized. But I think that I found a good track pointing the culprit and you can check it with the KStars simulator. Conditions : - CCD Module : no flip, no capture - Mount Module : flip Select a star on the East of the meridian and slew the mount. Select the Summary Module (IMPORTANT !) When the target passes the meridian, he Capture / Status will change from "Idle" to "Meridian flip" (normal) but doesn't return to "Idle" after. This is not normal, and might be an indication of the bug. In the same time, the Mount & Alignment / Status behaves normally. I hope this will help. Regards
Created attachment 118797 [details] Meridian flip
I must add this : Wait 30 sec after the target has crossed the meridian, and take a Preview in the Capture Module. Select the Summary Module : you will see that NOW the Capture / Status has changed from "Meridian flip" to "Idle" - just because you took that photo ! Might be something wrong in the Capture Module ...
OK, right, I could reproduce it. The meridian flip is executed normally, but the status in the summary tab is not correct. It remains on "Status: Meridian Flip".
While testing the fix to the status message, I found a more severe one: - set "Meridian Flip..." in the mount module NOT ticked - start a capturing session close to the meridian with "Meridian Flip..." NOT ticked in the capture module - wait until the mount passes the meridian - tick ""Meridian Flip..." in the mount module Result: the mount module shows "meridian flip waiting...", but it does not start as soon as the current frame is captured. Instead, capturing new frames continues.
I could also reproduce the bug you described. I think that the first step is to solve the bug(s) in the simulator. But if you need to have real tests done, please tell me. Regards
Bug fix posted here: https://phabricator.kde.org/D19794
Good job Wolfgang ! Thank you. (https://phabricator.kde.org/D19794 : the first time I put my nose into the code ! Whauuu !)
Wolfgang, did you correct that bug ? I'm running v.3.2.3 and my mount Celestron CGE Pro doesn't flip when the target crosses the meridian. My mount uses a Nexstar+ hand control; I tried all possible settings in the Meridian menu to no avail.
Yepp, the fix is part of the 3.2.0 release. So maybe you are facing another problem. Please report your problem to the INDI forum https://indilib.org/forum/ - Wolfgang