I’m writing a new ASCOM driver for a GEM mount and at present the side of pier information is not available.
I’m testing with SGP and find that when I start a sequence that crosses the meridian I get the warning “This telescope is not capable of performing a meridian flip!” and during the sequence the mount keeps going past the meridian.
The mount will do a meridian flip, once it’s tracked past the meridian a slew will do this.
It seems to me that this flip handling is a little too restrictive. Simply waiting until the mount has tracked past the meridian - as set by the flip position - and doing a slew will do the flip. I don’t know of a reason this would be harmful while not doing the flip could be because it leaves the mount tracking past the meridian, heading for a stop - hopefully a soft one.
Can I suggest this is changed as follows:
- Change the warning message to say that the Meridian flip state is
unknown and that a flip will be attempted at the flip position
- Ignore the PropertyNotImplementedException errors that attempting to
read the SideOfPier throws.
- When the flip position is reached do the flip by slewing to the
current position as you do now.
This will, I think, make SGP more reliable and able to handle a wider range of mounts. I doubt this one is the only one where the pointing state isn’t available.