I’m using the current 2.4 and things seem to have changed but not improved.
I tried the experiment I described - Use M52 and start about 16:00 I was a bit late and m52 had passed the meridian so I had to do a slew to something on the east and then use the HC to move past the meridian. I left the time to flip (TTF) at about 20 minutes.
This is what happened:
This was about 16:10:06
After a few minutes noticed that the TTF was now 23:59:00
This was about 16:20:16
The TTF continued to reduce but no flip was done, even though the hour angle indicated that the mount was well past the flip limit.
Left the sequence to complete and saw no flip
17:06 sequence finished.
Did a slew to Navi, just east of the Meridian, and started another sequence
Set up Sequence 12 * 5m frames
17:12 Start sequence
17:12 Time to flip 00:45:00
17:13 Increase number of frames to 14
17:18 TTF 00:38:40
17:22 TTF 00:34:30
17:27 TTF 00:29:45
17:46 TTF 00:10:27
17:56 TTF 00:00:38
17:57 TTF -00:00:10
17:59 new frame started
17:59 TTF NA
18:00 reduce frames to 10
18:04 finished, close down.
The log files look similar to what Chris W posted a month ago except that the hour angle of -349 degrees or less does NOT trigger a flip.
I started a new sequence for another object and that behaved as expected. The TTF counted down, went to a small negative value and the flip was done.
I’m running with an AVX mount, running StarSense, connected to TSX using the ASCOM driver then using the TSX ASCOM driver. I don’t think that using a Paramount would make any difference.
It looks as if there’s some bug in SGP that affects flipping but it only happens when an object with a Ra of around 23.5 has crossed the meridian. It’s an edge case, I’m not sure how big it is, maybe with 10 degrees past the meridian it will be about 40 minutes.
I have log files but don’t have a dropbox account. If the old Yahoo group is still extant I could post them there, otherwise let me know how to get them to you. The zip file is about 170 kb in size.