ASIAIR gone crazy?

SigurdG

An entirly new problem has popped up the last couple of days: When doing a goto, the scope moves in the wrong direction and does a validation in a totally different part of the sky. Does this a couple of times before it gives up. I take a picture, does a plate solve - success! - sync the mount and try a goto again. Same result. Sny ideas? And yes, focal length, local position etc. are correct.

--Sigurd

SigurdG

It's -25 C outside, too cold for ASIAIR Plus?

SigurdG

Well, seems like a restart of the ASIAIR fixed it (but lots of strange things have happened: initiated a meridian flip five hours in advance, initiated a goto home before the autorun was completed etc.)

Corsair

Was your whole setup - tripod and all - properly setup physically BEFORE turning on the ASIAIR? I.e. pointing True North/South , levelled, balanced, and in proper Home position

After you do a successful Polar Alignment - did you go to Mount Setting page and choose Go Home. Then after it settles into the correct Home position did you go to Mount Settings > Sync Mount?

I also always tell the mount to Go Home before slewing to next target.

SFj9LuNr

I've not been able to sync mount when pointing close to the NCP. I can plate solve OK. I get an error saying something to the affect of moving off at least 5 degrees to sync mount.

I've experienced ASIAir crazies but then I'm using a C8 SCT and AVX mount. Tried to locate and center on Bode's Galaxy with my 585MC. ASIAir found it and plate solved and usually backs off a bit then comes back on the target to plate solve to check centering then reports centered but this time it decide to head off to another part of the sky. Slapped on my Nikon D5100, restarted everything, but didn't do another PA and it found Bodes Galaxy. I guess the 585MC sensor was too small a FOV while the D5100 is APS-C. I wonder how large the star database in ASIAir is compared to the ASTAP star databases, D80, D50, D20.