I use the “Planning tools” funtion under “Target Settings” and is a really great tool. A couple of weeks back I set up a sequence whereby the first target was M83 and then I was going on to NGC 4603.
I decided to end the M83 sequence just before the meridian flip was due and to get straight onto NGC 4603.
The Planning Tools graphic said that the transit would occur at 10:15pm, so I set the M83 capture to end at 10:13pm. At 10:02:41, having just downloaded the previous frame, SGPro detemined that the next frame would be completed by 10:12:41 so that it should continue, however, it detemined that a meridian flip was required which was initiated at 10:02:42 . I was surprised when I saw the meridian flip underway so I stopped the sequence.
I checked the transit time on both TheSkyX and Stellarium and they both said it was at 22:02. Clearly Stellarium and TheSkyX were using the RA/ Dec coords for M83 from their databases and they were very similar. I checked the RA/Dec cordinates for my M83 target and these were virtually identical to those reported by the two planerarium programs. Therefore the exact positioning of my target is not a factor in the discrepancy.
Clearly since SGPro was receiving the hour angle information from The SkyX, when the need for the meridan flip was checked, it was past the Meridian and the flip was initiated.
This is a DropBox link to the pertinent files.
Included is the SGPro Logfile and a screenshot showing the projected transit time by SGPro versus TheSkyX and Stellarium.
So it appears that there is an issue with the accuracy of the projected transit time in the Planning Tools function.
The discrepancy can result in the sub optimal sequencing of targets as it did for me on this occasion.
Can you please check the information that is being used to determine transit times with a view to resolving the discrepancy.
Thanks & regards, Niall