Um, sure, yeah...I thought that answer was a bit tone deaf, I think it was lost in translation mostly. I've certainly read the manual and basically after I ran into my issue suggested there was a work around to fix the issue.

For posterity's sake, so that I may hopefully help someone who runs across this issue in the future, I'll publish this:

I have an Orion Sirius Pro, which is an EQ5 mount copy. Sky safari and the Synscan controller do not naturally get along together. I have found a work around for this.

Issue:

Sky Safari does not like you're absurdly "off" plate solves that confuse it and it assumes they're wrong ("too far" or something like that). This apparently unique to the Synscan controller.

Work Around:

1. Do not yet connect ASIAIR (I mean to the hand controller, but may as well keep the power off too).

2. Complete you're normal setup with the hand controller, to the point of at least a 1 star align (assuming you have a good polar alignment).

3. NOW connect ASIAIR to the hand controller, and startup your ASIAIR software (Ipad, IOS, whatever). Do not select what may be your default "ST4oncamera," but, rather, use Orion Atlas as your mount.

4. Now connect SkySafari using the default IP 1.0.0.10 or whatever it is. Use Skysafari to select your new target, slew, plate solve. If it says "sync failed"- go back to SkySafari and reconnect the mount. SkySafari seems to disconnect too easily if it's in the background, but switching between the apps relatively quickly makes sure that they are both working at the same time. Hopefully you're SkySafari will be updated, so you may reselect your target and then calibrate your guiding and start your sequence.

Caveats:

It may only update your SkySafari for that particular mount. The next time you select a target, it'll probably be far off again, and you'll have to repeat the process. Evidently it's not updating SkySafari/Synscan's entire sky model, so you have to platesolve before each new target. No big deal when it takes 5 seconds.

EDIT:

OG Post was around September 2018. As of the latest firmware update (October 2018/1.22?) this "cheat" no longer works. However, you can now use SynScan to some extent even with just 1 star align- just make sure you're alignment is close (I.e., if 1 star align, use a GOOD polar scope or Polemaster camera). Using the other Orion (Orion Atlas) en lieu of the Orion Sirius Pro (EQ5), no longer works because auto guiding will send your mount upside down. So you must use Synscan as a mount (or even ST4 on camera) to guide (even if that means using Orion Atlas to plate solve and then "switching" telescopes). But Synscan as a default works much easier so it's win.

Hello,

I have experienced much of the same problems. In addition my Synscan handcontroller for HEQ5 seems to have the longitude reset to "E" from "W".

Is there any estimation as to when these fixes are coming?

dgaspar wrote:

Hello,

I have experienced much of the same problems. In addition my Synscan handcontroller for HEQ5 seems to have the longitude reset to "E" from "W".

Is there any estimation as to when these fixes are coming?

Hello guys, we have confirmed this bug of SynScan driver and the fixed version is under testing.

For current usage, just ignore it.

What do you mean by ignore? Without proper latitude the telescopes thinks its in a completely different part of the world and will not point to the object in fact it could damage the equipment by striking the tripod. Please clarify your response.

dgaspar wrote:

What do you mean by ignore? Without proper latitude the telescopes thinks its in a completely different part of the world and will not point to the object in fact it could damage the equipment by striking the tripod. Please clarify your response.

Please check the location info under the section, if they are correct, try to and ignore the wrong display in the section. BTW, we are fixing this issue.