OK... new log links are good. Took a look at them and unfortunately, there is no smoking gun...
[10/2/2016 9:05:49 PM] [DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 20.9606025756579 (20h57m38.17s) Dec: 78.6102766529858 (78°36'37.00")
Then, some 5 minutes later
[10/2/2016 9:11:12 PM] [DEBUG] [Main Thread] Centering: User abort...
Inferring a problem with what is not there vs what is, we expect to see this next:
Scope reports it is done with synchronous slew, verifying...
But we don't... we get no response from the mount after asking it to slew to that location. The only recourse at this time is to try and reproduce the error with SGPro 2.5.2.2 and submit that log along with the 10U ASCOM logs that cover that same period of time. We need to see what the mount is doing...
As a note, the above text applies only to the first log linked. The other log failed for a completely different set of reasons:
- Plate solve failed (maybe because location hint was not accurate enough after the flip)
- No fail-over blind solver was set up
- Flip was aborted and recovery was canceled.