There are a couple of reports on the Facebook page of tracking turning off unexpectedly (sorry, I don't use Facebook, so I am posting this comment to this forum).
Other than possible bugs in ASIAIR, the mount itself can also turn off tracking.
Most mounts have a Horizon Limit and a Meridian Limit that are user settable. When the mount coordinates hit one of those limits, the mount will turn tracking off.
ASIAIR monitors the tracking state in the Mount, and reports it in the Mount Setup window. (It would be nice if ASIAIR were to display an alert notification on the screen when the mount unexpectedly turns off tracking.)
Incidentally, most (if not all) mounts will automatically turn on tracking after a GOTO completes. In addition to the limits above, mounts will turn off tracking after a Home, and if commanded by the command protocols to stop tracking. Those are normal changes.
If tracking appears to go off inexplicably, check your mount's coordinates (RA, declination, longitude, latitude) and time (Local Time, UTC and Daylight Saving Time offset) to see if one of these limits has been reached. A planetarium program like Safari can help with this. Some hand controllers will also display an alert that one of the limits has been breached.
This is especially true this week, since the USA has just switched to Daylight Saving Time. The mount could have reached the Meridian Limit, for example, before ASIAIR thinks a star has reached the meridian. Time discrepancies also causes the horizon to "rotate" around the polar axes, and also capable of causing a horizon limit to be reached when the star is still above the horizon.
Chen
