Good Morning...
Glad to hear everyone's back to work at ZWO - ASI. Have purchased a ASI183MMC and taking delivery soon (purchased through High Point Scientific in NJ). Plan to soon add the ASIAir Pro to my inventory.
As you deal with that nasty virus, our prayers and thoughts are with all of you - please stay safe & healthy.
First, the ASIAir has been a wonderful technology, allowing me to connect my guide camera, focuser, EFW, and main imaging camera - everything works very well together. Plate solving works wonderfully, and the connection to SkySafari Pro works nicely for my image planning and to see how DSO will move during the session.
However, I've been using the ASIAir with an AVX mount with Celestron GPS unit connected to the mount, and have seen erroneous longitude information captured in the ASIAir software (using iPad) - have not seen any issues with the latitude.
I use the GPS to capture date, time and GPS coordinates (GPS is setup and on in the hand controller). All of this information shows up in the hand controller.
The ASIAir is connected to the hand controller USB port (bottom of the unit).
When on the Telescope (mount) tab, what I've found is that the longitude appears to be 180 degrees off - I'm located at 97W and strangely the ASIAir is reading the AVX information as 277W (180+97 = 277).
It's easy to miss the error when setting up (and the GoTo functionality fails) - I now check the mount information to confirm the Lat & Long prior to starting a session. Not sure if the plate solving is suppose to update the Lat & Long - but the plate solving information is synching to the mount. In the SkySafari app - I've got the right Lat & Long setup and when I use the GoTo function, the scope slews to the right location.
I don't sync the lat & long information from the iPad via ASIAir.
I've tried closing the ASIAir app and re-opening; tried shutting down the mount (powering off and disconnecting the USB); re-setting the GPS (turning it off and on); and then rebooting everything.
After randomly trying several different things - miraculously the longitude gets set to the right value. The issue is very intermittent. Seems to appear every 2-3 sessions. No obvious rhyme or reason for this erroneous information.
Is this a known bug?
What's surprising - I selected the the Sky Scan mount in the Telescope tab - the information was read correctly but when I went back to the AVX mount - the longitude was showing 277.
Welcome any suggestions - could be (likely) user error. Can reliably replicate the issue but certain have seen it on 5 different occasions.
Thanks - Jim