I have had a look at the driver and APCC logs and there seems to be some very odd pauses in responses from APCC. The responses are currently handled by the user interface thread, but background polling and incoming commands are handled by background threads. Background polling and received commands were expediently handled by APCC during the "response pauses", so APCC as a whole was still running. However, if the UI thread was hung up doing something this would likely cause the timeouts that are seen in your driver log file.
The solution I intend to pursue is to move the responses into a background thread, but that will be a bit of work. However, I would still like to find out what might be causing this. For instance, do you think you might have had the 3D Telescope view window open at this time? That particular window can take a lot of CPU time if the graphics card in your computer is not very powerful. Were there any other applications on your computer running at that time possibly doing a lot of graphical or CPU work? (BTW, what are the specs on your computer?)
That said, looking at the logs the mount did actually "flip", but SGPro could not read status from the driver because APCC's replies were stalled. Later, APCC sent out all the replies, causing the driver to clear it's buffers and resync communications. Then APCC and the driver were in sync again.
-Ray