ask the driver author

Greg tried to shed some light on the GoToStar-to-ASCOM-to-SkyTools situation...

When SkyTools first connects to the telescope via ASCOM it sends an ASCOM message to set the observing location in the mount to the location that SkyTools is using.  Many mounts do not support this ability to set the location.  The ASCOM driver is supposed to try to communicate the location to the mount, and upon failure, it is supposed to send a non-fatal error message back to the calling program (SkyTools).  In the case of the iOptron mount, we discovered that there was a bug in the driver.  It mistakenly sent a fatal error back to SkyTools, which caused SkyTools to disconnect and shutdown.

What makes this issue appear to be unique to SkyTools is that other programs don't make the attempt to send the location to the mount unless the user asks it to.  Most never do, so the error goes undetected.

I was able to work with the author of the [iOptron] driver and he fixed the bug, resolving the problem.  My advice is to try the different drivers you have access to.  Sometimes the latest driver is only available via the author (often on his web site).  If that does not resolve the problem then try to get in touch with the author of the driver.  Provide him my explanation above.  Perhaps he can resolve the issue.

So it sounds like Greg talked to iOptron to resolve the matter. I just need to find the right (or a better) driver...