The issue is that while the mount is flipping it is not reporting Slewing == true. This makes SGP think that the flip process is complete and SGP attempts to validate that is the case. This validation fails as the mount is still slewing and when SGP asks for the side of the pier it’s the same as pre-slew…therefore we make the assumption that no slew happened. This is solely because the slew did not block where it should have.
That is correct. Pointing state is nearly identical to Physical SideOfPier with one important distinction, when the gaze goes below the pole the side of pier flips. This is the model SGP expects. It is important to note that “pointing state” does NOT indicate the gaze of the scope, it (roughly) indicates the side of the pier the OTA is on.
This should be pierWest assuming you’re above the pole.
Passing the meridian should not change the SideOfPier.
Incorrect. SGP fails because the slew didn’t block and we IMMEDIATELY asked for the side of pier after checking if the slew is done.
The ASCOM document doesn’t really go into tracking through the meridian and says this:
EXCEPTIONS TO THE RULE
Flip margins, slew limits etc. are tools that mount designers provide to allow the observer to override the basic design principle that the telescope should choose the pointing state that puts the telescope above the counterweights at all times. Conform deliberately avoids testing in sky areas where these conveniences are frequently implemented. It chooses hour angles well away from the meridian and wherever possible chooses declinations that keep observation points away from the horizon and the pole
However I’ve never seen a mount that changed side of pier as it tracked through the meridian. And the Simulator (which should be considered a reference implementation) does not do this either.