
Originally Posted by
Bob Denny
The tracking is really coming on at the end of the process (it stays off throughout the flat process incluuding when the flat script ends). The physical cause is within the AP Driver - If the client changes the RightAscensionRate (the offset from sidereal rate) to zero (Telescope.RightAscensionRate = 0), two or so seconds later the Tracking comes on spontaneously. ACP itself, internally, sets the tracking offsets to 0 at the end of a script. It then turns tracking off but only if the script was run by a web user. This also fails with the AP driver because the tracking spontaneously comes on a couple of seconds later.
I will discuss this with the AP driver developer, but there is probably an argument to be made that changing the tracking rate implies that it should be tracking. Right? The other point if view is that setting the offset rate is telling the mount the speed at which to track whenever it is tracking (... or not). Turning tracking on and off should be via the Tracking property only.
Apparently this isn't the case with other mounts. If AP convinces me of the error of my ways, I'll do something in 7.2.