Meridian Flip Configuration
Good news, folks, we are starting to work on it. It will make the meridian flip more robust - hopefully - but the code complexity will grow again. Since there are mounts that now their pier side, others not, some can be forced into a meridian flip, others not etc.
The flip process should also be managed using the Pier Side property when this is available. At present this isn't used, it uses hour angle. As a result there's a lot of scope for confusion where a mount does a flip earlier than expected and the flip process does another one or, worse, the flip process does one too early. The system now thinks that a flip has happened but it hasn't and it tracks into a hard stop.
That's really strange, but maybe it's simply an edge case. Your mount does not take 2 minutes to slew? Or maybe you were not fast enough checking the hour angle?
The target is at +0h 2' + and the mount is on the west side pointing east
The question that I always ask in such situations: are you really sure that date, time and location match 100% between the mount and KStars? Is KStars setup in such a way that it propagates its settings to the mount?
If not, that is a typical source for unexpected behaviour.
I did have to effectively reset the mount model after the initial test. The mount pointed so far from the first target that plate solving was going through several astrometry files trying to find where it was actually pointed. I stopped the plate solving and slewed to a point nearer the NCP which plate solved well. The following slew was also good with the target in the frame (2 deg x 1.5 deg).
I'll do a similar check later today.
You can the values in the handset of your mount.
I don't know if the mount has any information not from KStars.
Where do I check that KStars propagates to the mount?
In the INDI settings of KStars:
I was working on M42 and did a solve and slew at HA ~+1minute. The mount was on the west pointing east at the start of the solve and moved to the east side. However, it would only slew to Alnitak or Alnilam at this point in time (consistent with the display in KStars). After playing around on the Horsehead Nebula (not sure how long), I could successfully move to M42.
Later after another trip (yeah, I'm getting old)... I saw in my yard cam that the rig did do the flip. Plus that message said Status: Inactive
My thoughts are, as long as that count-down message is running, it will flip.
Here's the simulator showing the same thing:
All that the pier flip process does is wait until the flip condition is reached, then does a slew to the current coordinates.
The capture and slew and, if I recall correctly, a load and slew did not go to M42 at that point in time. Several minutes later (didn't make note of the actual hour angle), it finally would go to the target.
GPDX+EQMOD, CEM60EC, ASI1600+EFW+EAF+ASI290 mini
As Der Pit says pointing errors may make your mount point differently when the pier side is changed. Ekos will usually do a solve and sync after a pier flip, at least when it's imaging.
As I said before I don't think there's anything in Ekos to manage hour angle limits, at least at present.
i'm not sure how much we can help though, we can't see your mount and so can't see much of what is needed to help you work out what is going on. A few lines of social media posting doesn't give us much. The result is confusion, misunderstanding and misinformation.