ASIAIR v2.5.1 has been released!: Page 2

ASIAIR v2.5.1 has been released!

R0k9pZfT

Not specific to this version, but the Android app also ignores if auto-rotate has been disabled on a device. Maybe I want to turn my tablet upside down for a different perspective on the image, but the app rotates the screen anyway. Please pay attention to the system settings.

PMTeam@ZWO

R0k9pZfT
We have noticed this issue. Could you please record a video showing your tablet and the entire operation process? We would like to see how you rotate the tablet and the corresponding screen changes.
We look forward to your reply and thank you in advance.

R0k9pZfT

nic35 I guess this is a your mileage may vary situations. I have an AM3, previous generation 5 position 2" filter wheel (not the 2025 version with USB-C) all current on firmware as of this writing, and everything is detected and working for me.

"Working" only means it's all recognized and functional--excluding the new bugs ZWO added with 2.5.1!

PMTeam@ZWO

R0k9pZfT Hi, Thank you for your feedback. We have noted this issue.To help us analyze and resolve the problem more effectively, we would appreciate it if you could provide us with the following details:

Please provide a screenshot when the issue occurs. We need to know the exact time the issue occurred to help us check the logs.
Please send us a bug report when the problem occurs.

Email: tianfeng.chen@zwoastro.com

R0k9pZfT

PMTeam@ZWO Which issue? The progress ring always cuts out at exactly 50%, no matter how long the exposure. I reported it in 2.5 and you did nothing. 50%, half of the exposure time. You can reproduce it at will.

The crashing of the app with the filter applied I can't stop nor capture because the app crashes. I already sent that report, as reported.

azskyguy

I note that I was offered a version 2.5.2. It fixes the guider disconnect issue that I experienced and reported to ZWO. Glad it is fixed.

I have 2 remaining issues.

First, at times an image will refuse to download after it is completed. It gets stuck on 'preparing'. Last night it happened on image 18 of an 18 image autorun. I have sent numerous logs of this problem.

Second, and old problem has returned in 2.5.1. After a meridian flip the guider acquires a guide star and then it quickly fails to track it. I can stop the session. Manually slew to the target, and start the autorun again and all is fine. Saw this a few versions ago, it was fixed, and now it is back. Perhaps this is fixed in 2.5.2 but I haven't tried it yet.

In summary, this means I can't do an automated run without closely watching the system, negating the value of the autorun feature.

Hopefully, this will get fixed.

PMTeam@ZWO

azskyguy Hello, we apologize for the unpleasant experience you've had.
Regarding the first issue: The image you couldn’t download is likely due to the exposure failure.
Regarding the second issue: It was probably caused by guide star loss. When you start Autorun, the app will automatically select a new guide star. May I ask how often this problem occurs? We also suggest you try again on a clear night to see if the same issue occurs.
We look forward to your reply and thank you in advance.

azskyguy

PMTeam@ZWO
Thank you for the response. When you say exposure failure, the question is why does the exposure fail? This seems to be an intermittent problem and I don't think I'm doing anything to cause it. I did get a note from ZWO last night asking if they could do an FPGA update remotely. I'm going to do that tonight as they login to my computer.

As far as the guide star loss, I don't understand that either. After the Meridian flip the telescope acquires a guide star and starts guiding it guides for a few cycles and then it fails. I am imaging from Arizona where we had very clear skies and no problems with seeing. So this is still a mystery to me. I have seen this in previous versions of the software and then it goes away and now in 2.5.2 it's back.

I am pleased that the download problem will hopefully be fixed and I appreciate ZWO actually checking the logs and working on a solution.

PMTeam@ZWO

R0k9pZfT Hello, we apologize for the unpleasant experience you've had.

Regarding the crash issue when using the filter button in Star Map from Preview mode, we have tried but could not reproduce it. Please send us a bug report when the issue occurs.
We are aware of the issue that the progress ring around the shutter button on the Preview page disappears at 50% progress. We have checked the BT file you submitted earlier, but we cannot analyze it in detail without knowing the exact time when the progress ring disappears. Once we know the exact time the issue occurred, we can find the corresponding information in the bug report. Please take a screenshot when this happens and send it to us, along with a bug report.
We could not reproduce this issue. During our tests, the flat field images do show rotation angles. I will pass this on to our engineers for further analysis.

If you encounter any issues, please feel free to contact me via email. We will do our utmost to resolve all your problems.We look forward to your reply and thank you in advance.
Email: tianfeng.chen@zwoastro.com

PMTeam@ZWO

azskyguy Please feel free to let me know if the issue persists after the remote update.
By the way, have you experienced any disconnection issues with the guiding camera again after using version 2.5.2？

PMTeam@ZWO

Aobrien1441 Dear User,
We have urgently fixed the random disconnection issue related to guide camera and equatorial mount, and now we are releasing the beta version with this fix. You may download the updated version via the links below.
Android: https://pgyer.com/air_beta_android
iOS: https://testflight.apple.com/join/6uEyoSl3
If you encounter any issues while using this fixed beta version, please feel free to contact me via email. We will do our utmost to resolve all your problems. We look forward to your reply and thank you in advance.
Email: tianfeng.chen@zwoastro.com

gm6wS8xS

PMTeam@ZWO

If I follow the link to TestFlight I get the old version Version: 2.5.8 (4) from 24.02.2026

Update: I must end the TestFlight for ASIAir and rejoin with the link to get 2.5.22 (11)
will test tonight

Eric

PMTeam@ZWO

I am getting "exposure failed" errors on both my ASI2600mm Air and ASI2600mc Air cameras almost every night now, running the plan mode on a single target, each night it gets to around 100-125 exposures and then encounters some kind of error, the exposure doesn't finish, then the plan ends and end of plan sequence initiates. The cameras have worked fine for months, both are less than a year old. The log(s) simply just say:
"2026/03/20 00:13:21 Exposure 60.0s image 112# failed
2026/03/20 00:13:21 [Guide] Stop Guiding
2026/03/20 00:13:21 [Autorun|End] Pause Autorun
2026/03/20 00:13:21 Pause Plan New Plan
2026/03/20 00:13:21 Turn Off Cooling
2026/03/20 00:13:21 [Guide] Stop Looping
2026/03/20 00:13:21 Stop Tracking
2026/03/20 00:13:36 Mount GoTo Home POS
Log disabled at 2026/03/20 00:13:36"

I avoided updating to the newest firmware because of the reported disconnect issues from other users in this thread, I did update to the newest firmware and will run another plan session tonight. We have so few clear nights it's EXTREMELY frustrating that these cameras even have exposure failure/download issues even within their own "ASIAir" environment. You guys seriously need to address this issue, too many people are reporting 2600 series download issues/exposure failures either in NINA or even with the ASIAir, the cameras are too expensive for this kind of stuff to be happening regularly.

azskyguy

PMTeam@ZWO
No disconnections yet... 2.5.2 seems to have fixed it.
Thanks

FC1Ke90s

Hello ASIAIR-Team
I can confirm that the calibration has now started. Thank you for the fix!

At the same time, I've noticed that when the guiding problem "Star Lost" occurs, the mount can move completely uncontrollably. This can only be stopped by switching off the power.

This is completely impractical. Firstly, the alignment is lost, and secondly, the risk of damage is very high. I hope you can resolve this issue.

Yngvarr

I updated today to v2.5.1 and I’m experiencing some issues that I never had before.

I’m getting random disconnections of the system, followed by automatic reconnection. This behavior was never observed on previous versions.

I also noticed a very slow image preview download speed, fluctuating between ₃₀ kbit/s and 130 kbit/s, which makes the preview almost unusable.

Both issues started immediately after the update.
Has anyone else experienced similar problems?

piotrc

Yngvarr I have the same problem after the latest update :-/

SFj9LuNr

I have a new ASI2600MC Pro. I’ve experienced exposure failure error messages. Disconnecting the camera in the app and reseating the USB 3 cable and reconnecting camera seems to restore the connection.

I’m also noticing when in Autorun taking Flats , 30, 3 sec exposure about halfway into the sequence the power drops to 0% and it goes from -5C up to about 3C and the the power kicks in and the power comes back. I’ve seen the odd Light frame showing the temperature has increased, the the next frame is back to -5C. I’ve connected camera power to an external source and seen this issue.

I’m going to test my ASI2600 MC with NINA and my Pegasus Powerbox to see if it’s the camera cooling system.

8YMzs635

Hello,

the angular deviation detection isn't working anymore! Anyone else got that issue?

I Goto from and old light but I don't get the info as in former versions that the FOV is rotated.

How do I get that back?

piotrc

Unfortunately, in addition to this unstable connection after the latest update the network connection via cable is broken as well. Hej @PMTeam@ZWO how can I return to a previous version???

Corsair

piotrc
Instructions on how to downgrade are in this manual: https://mega.nz/file/ft52jaLY#Fn0iBy4UIPlV-QM4xa28Ofu20ixwF8EmiBwNOiVvP2A from @Luxo

See section 26.4.

« Previous Page Next Page »