Thanks @geehalel. Crikey re the potential for so many errors to creep in - certainly seems like a software solution would be great to mitigate for some of this. (I try to be quite careful about setting up, levelling etc, but clearly not enough). Will see what happens when we next get clear skies and I set up again & re-calibrate.
I'm hoping to set a permanent pier up so once that happens, then fingers crossed the alignment & mount meridian will be locked in (as long as the setup is done sufficiently accurately I guess - it would be a disaster if flips still didn't happen even after a fixed pier).
I see from another thread by @jabian that more meridian flip problems seem to be appearing so hopefully all the devs can agree something quickly (the strengths & weaknesses of open-source software approaches ).
Oh no sorry to hear you're facing similar challenges. Yes that same thing has been happening for me (both it saying a flip has happened but then nothing actually having happened, and what you describe as "Meridian flip planned..." & then nothing). Will follow this thread with interest.
@geehalel has been v helpful in the other thread - as he says, it seems like a software confab is perhaps called for among INDI developers!
Thanks @geehalel. Ok I see now the logic for the reliance on the mount meridian. I'm still a bit puzzled as to how the mount meridian could be so far off (20m) if I'm doing polar alignment through the polar scope in the mount axis, b/c if the mount was that far turned, presumably Polaris wouldn't even be visible for the polar alignment (I align visually first, and then use the EKOS PA tool for the fine adjustments). So if Polaris is at all visible in the polarscope then there must be an upper limit on how far the misalignment could be?
But nevertheless it is what it is - now that the models are purged, I will try to be even more careful in the polar alignment to try and get the mount meridian close to the celestial meridian. Fingers crossed that then the flip will happen before it would otherwise damage the scope.
Thanks again for your patience!
Thanks @geehalel - yes I tried what you suggested (manually issuing a goto for the same coordinates after the meridian had been passed) and the mount flipped. You're right that definitely seems a glitch on the mismatch between EKOS coordinates and mount driver coordinates (even when purged).
Do you think it is possible to fix this within EKOS? (For example through a routine that automatically issues a goto command - rather than a flip command - once the user-selected HA has passed beyond the celestial meridian. Sorry if that's naive, I'm not a programmer!). B/c otherwise this means that the user has to be physically around to manually issue a go-to command (which for example could be at 0200, 0300, 0400!) which would defeat the purpose of an automated imaging session software?
Thank you again for taking the time to help & explain.
Ok. I'm puzzled why that happens even after I've now cleared & purged everything. If a target is set just after meridian (say 1m), I guess its the mount driver that's processing that goto and orienting the mount a certain way? So if the mount driver knows this target is after the meridian & figures out which way it should move, why does the same driver not have the same alignment when trying to process a meridian flip?
(Unless its EKOS telling the mount driver to orient a certain way for the 1m object...but if its that and the EKOS driver prevails, why does the mount driver not listen to it in a meridian flip).
Most important Q I guess is how do I fix this?! Clearly purging the model hasn't worked, so do I need to set up a model and then cross my fingers? (In which case I can't dummy that indoors?)
Just to say I double checked that crazy thing. If I set a target east of the meridian, the mount goes west pointing east and starts tracking but does not flip (even after >0.10 HA). But if I set a target at say 1m after the meridian as a go-to, the mount goes east and points west in the correct way. So EKOS & the mount are figuring out correctly the goto, but for some reason if that object was being tracked across the meridian it would not flip. (All models had been cleared & purged before, and a power-cycle done too).
Thanks both @geehalel & @alacant.
I couldn't find AlignData.xml anywhere (searched for it on Terminal so it looked at the whole machine). Anyway, I just purged all the configurations, and tried again (dummy run indoors). The mount parks fine (pointing to celestial north), slews to a range of targets either side of the meridian & returns to park normally. But it still doesn't do the flipping meridian flip. Am uploading the log file from the dummy session (hopefully it will show whatever the mount driver is doing at initialisation).
The crazy thing is that if I set a target that's just the other side of the meridian (ie positive HA but still less than 0.10HA as a goto, the mount goes to it the "right way" (east pointing west) but if it had been tracking that object it wouldn't do that flip).
@alacant as you can see I came to the conclusion of trying from basics too (great minds ) but it's still no joy. I always bubble level before a session, & always park at the end of a session, & always polar align at the start (unless the mount has been left untouched from the night before).
@geehalel your last msg suggests that good operating practice would be to sync a mount model at the start of each session even if you've also done polar alignment, or am I misunderstanding that? (I had thought mount model tool was only needed if polar alignment was not possible?).
Anyway here is the latest log file from the dummy session - thank you again!
Hello, I just tried some more - just left it running on a dummy run indoors while watching the news. It got to +47mins and still no meridian flip. There seems to be something seriously wrong? The LST on the Mount tab is correct. Thank you.
PS the only PierSide property I can see in INDI Control Panel just says "West (pointing east)"? Thank you!
Thanks @geehalel. Do you know how I can correct the mount misalignment (does it need to purge the parking or something like that?)? I polar align (using the EKOS tool) at the start of every session, so should that not align the mount driver correctly too?
I've just done some dummy runs tonight, at 0.10 & 0.20 after HA, and the timer correctly shows when the flip should happen, the designated time passes, the status just changes to "Meridian flip planned..." & nothing more happens for a good few minutes after that (I stopped waiting after that). <This is a difference from the other night when it said the flip had actually happened>
The problem is that at 20 minutes of misalignment, the flip will happen too late & my main imaging scope will hit the pier and be useless for anything near the zenith. (I didn't use to have this problem so I'm also a bit confused on how the mount could misalign like this).
Thank you for any more help you can suggest!