In the current implementation of APCC it appears that APCC is basically intercepting the slew command when "CW up slews within West limits" box is checked, preventing the meridian flip from completing, and causing SGP to abort.
It doesn't work that way. The mount's flip point is controlled by the meridian delay set in the mount. The cause of the flip failure is probably a time discrepancy between the mount's meridian delay value and when SGPro thinks it is okay to flip. If there is even a split-second difference between the two times, that could prevent the pier flip from occurring if SGPro sends the slew command at the exact moment a flip should work. If SGPro delayed a few seconds, it might solve the problem. The new flip padding control in the 1.9.1.3 beta tries to address this timing issue.
-Ray
-----Original Message----- From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of steve.winston@gmail.com Sent: Monday, November 1, 2021 9:15 AM To: main@ap-gto.groups.io Subject: Re: [ap-gto] APCC Meridian Tracking Limits and Sequence Generator Pro
Hi Ray,
That's not going to work because you can't guarantee that SGPro won't issue a slew after the meridian.
That's fine as this is exactly the expected and documented behavior for SGP: If the mount is at or past SGP's configured meridian limit, then issuing a slew command should result in a meridian flip.
In the current implementation of APCC it appears that APCC is basically intercepting the slew command when "CW up slews within West limits" box is checked, preventing the meridian flip from completing, and causing SGP to abort.
Is there a way to configure APCC to ensure that when SGP reaches it's configured meridian limit and issues the slew command, the meridian flip can complete?
