critical issue with all sky polar alignment in the Southern Hemisphere: Page 2

critical issue with all sky polar alignment in the Southern Hemisphere

Mario851

Luxo I’m experiencing the exact same issue, but I don’t think it’s just a focal length limitation. I’ve tried ASPA with three different setups: an FRA500 (500mm), an Askar 120 (840mm), and a C8 Edge HD (2032mm), and the result is always the same.

The error values in ASIAIR fluctuate significantly with every refresh without even touching the Alt/Az knobs

bgastro

Luxo

It left me thinking ASPA is OK for those with scopes under 1000mm focal length - the field rotation will not be noticeable

i'm sure its nothing to do with focal length, my scope focal length is 500mm+ and have this issue

B65y788K

I have this issue. Located in Canberra.
I came from successful PA in January 2026 using a Redcat 51 with asi294, and now failing with an rc6 with the same equipment (June2026). I do believe the focal length could play a part. Could I PA with the finder instead?

bgastro

B65y788K

I assume that since you changed scope, in asiair settings you have also changed the focal lengths settings? if you forgot then PA will never work

PMTeam@ZWO

B65y788K Thank you for your feedback. In theory, a guide scope can also be used for polar alignment. If you encounter this issue again later, please submit a Bug report within the App.

Wobbly261

Likewise to the above I have tried different focal lengths and two different mounts on several occasions since it was released. It does not work. I submitted a bug report tonight. Have ZWO provided any feedback on what is being done to fix this?

PMTeam@ZWO

Wobbly261

Mario851
Could you please share the BT report ID with us? We will conduct targeted analysis based on it. Meanwhile, we are fully optimizing the algorithm for polar alignment anomalies in the Southern Hemisphere. Thank you for your feedback and support!

Mario851

@PMTeam@ZWO ?????

It has been several years since 2022. I have submitted the requested reports multiple times, and none of them have been addressed. I would appreciate your help with this, it is a well-known issue within the Southern Hemisphere community.

Corsair

PMTeam@ZWO Could you please share the BT report ID with us? We will conduct targeted analysis based on it. Meanwhile, we are fully optimizing the algorithm for polar alignment anomalies in the Southern Hemisphere. Thank you for your feedback and support!

I really hope that is the case.

There's been more than a few users in the southern hemisphere who have had issues with All Sky Polar Alignment.

Really time it was properly addressed with proper communication between you and the users who have reported issues with it in the Southern Hemisphere

Mario851

PMTeam@ZWO BT ID BT20260318249325A

Corsair

Setup and did an UNGUIDED EAA imaging session last night/ this morning (20/092026 - 21/09/2026) using ASIAIR App/Firmware 2.5.2. Location: Southern Hemisphere. Kiama Heights, NSW, Australia.

Equipment/Setup:

Sal-33 mount on and connected to usb 2.0 port of asiair but powered separately.
ASI294MC Pro camera connected to usb 3.0 port and connected to power output of asiair.
Rest of equipment: C8 SCT with f/6.3 Reducer; MLAstro P-200 Pier Extension; HEQ5 Pro Tripod
I do NOT have an EFW, EAF, CAA, Guide Camera, Guide Scope
Made sure mount was in Home position (and powered on since I'm using a Sal-33 harmonic/swg mount which doesn't have clutches) before turning on ASIAIR.

Launched ASIAIR App on my Android device. Checked location. THEN connected device to ASIAIR WIFI. Once connected then tapped on Enter Device in App. Confirmed initial settings to go to Preview Mode screen.

Went to Mount Settings > Home. Check mount stays in Home position correctly.
Then selected Mount Settings > Sync Mount.
Went to Connections Settings > Powered on camera
Went to Camera Settings > enabled cooling to 0°C

Waited for cooling to settle at desired temperature with cooling % stable.

Checked focus was good enough in Preview Mode by manually slowing mount using on screen mount controls in ASIAIR App to slew to an area more than 5° away from SCP, taking a 2s exposure, checking stars, then tapping Solve on the left. Tap on Sync/Sync Mount option in the confirmation message that pops up.

Go to Mount Settings > Home. Wait for mount to Home. Check it does so correctly.

Then did a normal Polar Alignment (no ASPA, no New Plate Solve). Did a screen recording of this.

Once done. Mount Settings > Home. Then Mount Settings > Sync Mount (yes, I do this a few times during setup).

Then use ASIAIR Sky Atlas to centre on a bright, named, star then tap Goto. Wait for it to centre. Went to Focus Mode to manually refine focus with a bahtinov mask. Once done, remove mask, then Mount Settings > Home. Then Mount Settings > Sync Mount.

Ordinarily I'd then start Unguided EAA Imaging session but this time I did the following (and screen recorded it):

Started normal PA routine again just until the point where it shows the initial error. This error had changed from where I ended the initial PA showing larger total error. However, without touching anything, if all I did was wait 5-10 seconds then tap refresh (did this twice) the total error stays stable with only arcsec changes. Tapped on finish without changing anything. Tapped on Restart icon. Then went to Mount Settings > Home.

Then went to About > enabled ASPA. Left New Plate Solve off.

Now in PA routine see the ASPA info. Started that and let it do its rotations. Then it showed the inital total error. This was also different to the total error shown in the previous regular PA process (it was actually less this time). Again, not touching anything, all I did was hit no refresh and wait 5-10 seconds then hit refresh again.

All I noticed was the same behaviour. Just slight fluctuations in arcsec. No continually increasing errors on refresh.

I then tapped finish. Tapped Restart icon. Then About > disabled ASPA. Then Mount Settings > Home. Then Mount Settings > Sync Mount. Then back to Preview Mode to begin my session.

I'll upload both screen recordings to YouTube soon and share it once I make it into a video.

@Moontanner

« Previous Page