Well… there’s a lot of stuff going on here and I am not sure what issues are related to software (some might be related to hardware communication?).
First, before you have any issue with the telescope, there was an issue with the focuser:
[2/27/2015 9:30:01 PM] [DEBUG] [Main Thread] Failed to connect to focuser. : Exception has been thrown by the target of an invocation. (System.Exception: serial port error when connecting)
This may be a red herring… maybe the focuser was not powered on or something, but thought I would bring it up.
Next you connect successfully to the mount and then immediately lose connection. None of your ASCOM logs show this period so I cannot say why:
[2/27/2015 9:30:42 PM] [DEBUG] [Telescope Thread] Telescope: Implements MoveAxis...
[2/27/2015 9:30:42 PM] [DEBUG] [Telescope Thread] RA Move Rate Range: Min->0 Max->5
[2/27/2015 9:30:42 PM] [DEBUG] [Telescope Thread] DEC Move Rate Range: Min->0 Max->5
[2/27/2015 9:30:42 PM] [DEBUG] [Telescope Thread] Telescope: CanSetSideOfPier returned False
[2/27/2015 9:30:42 PM] [DEBUG] [Main Thread] ASCOM Telescope: Error in GetCurrentPos : Lost communications with mount.
Then it looks like you connect again (successfully):
[2/27/2015 9:31:21 PM] [DEBUG] [Telescope Thread] Telescope Dispatch loop: Received SGM_TELESCOPE_CONNECT...
[2/27/2015 9:31:24 PM] [DEBUG] [Telescope Thread] Telescope: Implements MoveAxis...
[2/27/2015 9:31:24 PM] [DEBUG] [Telescope Thread] RA Move Rate Range: Min->0 Max->5
[2/27/2015 9:31:24 PM] [DEBUG] [Telescope Thread] DEC Move Rate Range: Min->0 Max->5
[2/27/2015 9:31:24 PM] [DEBUG] [Telescope Thread] Telescope: CanSetSideOfPier returned False
But… the mount is no longer tracking. I am not qualified to fully interpret the ASCOM logs, but from the second attempt:
000031 2015-02-27 21:31:23.126: Inititialization: Info : Side of mount initilization complete!
000032 2015-02-27 21:31:23.137: User: Info : Stop tracking pressed
000033 2015-02-27 21:31:23.148: ASCOM: Info : SET Tracking = False
I am not sure why it indicates that the user stopped tracking. After this, the mount continually fails when SGPro tries to sync it because it thinks it is not tracking. When you use the nudge commands, we ensure that when the nudge is over, we send a Tracking = true to the mount (since we have seen some mounts stop tracking after nudge). This code, however, has been around for a long time (to include the older, probably less stable, code base you are using).