ASIAIR v2.5 has been released!: Page 4

ASIAIR v2.5 has been released!

Moontanner

So far, so good here. With limited opportunities to test between all the rain and unstable astmosphere, the two nights I managed seemed to work OK in plan mode. Nothing fancy.
The broadband data is all going to be rubbish anyway due to the Moon, so I deliberately had the EFW do LRGB in quick sucsession and there was no issue with the autofocus routine beyond a momentary connection dropout with the EFW. It recovered perfectly after taking one shot through the slot one filter during the reset process. (NFI what caused the dropout).

There's still some weird behaviour with the guiding that has so far only occured while using the CAA. It's not totally lost the plot like it was doing prior to the updates, but that was intermittent anyway. I guess further testing will tell the full story there.
I'll be throwing several different angles into the next run to see if the CAA gets lost again and tries to rip out the cords.

All in all, I'd say I quite like update so far. Both Plan and Autorun seem to work well thus far and I'm liking the subtle changes to the UI.

Moontanner

peter.muller

Last time that happened to me it turned out to be related to increased interference. New neighbours setting up proper networks in a sleepy suburban street forced me to add an extender near my rig after years of trouble free use without.

My rig slews around just fine, although I haven't tried in video mode yet. If I get a chance tonight I'll shoot some video of the moon and test it out.

89E2n8Qp

@PMTeam@ZWO

I am experiencing critical safety issues with ASIAIR v2.5(13.13)
and Meade LX200R mount that make the equipment completely unusable.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
EQUIPMENT CONFIGURATION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

• ASIAIR Mini v2.5 (13.13) - Serial Number: e9ffca8a
• Mount: Meade LX200R 8" (GPS SMT v4.0g)
• Driver: "Meade LX200 Classic"
• Connection: USB-Serial (CP2102 chip)
• Main Camera: Sony ILCE-7C
• Guide Camera: ZWO ASI120MM Mini
• Device: iPhone 16 Pro Max + iOS 26.1

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CRITICAL ISSUES (Started immediately after v2.5 update on Dec 25)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Issue 1: All-Sky Polar Alignment - Infinite Loop

Plate solving succeeds
"RA axis will be auto-rotated..." screen appears
Pressing "Next" causes infinite loop
Mount rotates 180+ degrees without completing
Tested with 2 different cables → Same behavior

Issue 2: STOP Command Complete Failure

STOP button completely ignored
Mount continues slewing indefinitely
Only solution: Physical power switch (safety hazard!)
Started AFTER the polar alignment issue

Critical: Mount works perfectly with hand controller only.
Hardware is confirmed working.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONTRAST WITH OTHER USERS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

@Luxo reported that v2.5 works "AWESOME" with SkyWatcher CQ350.
However, my Meade LX200R has critical failures.

This suggests v2.5 fixed some mounts but not LX200 Classic driver.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RELATED TO KNOWN ISSUE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Forum: https://bbs.zwoastro.com/d/18296-asiair-buggy-w-lx200-classic
Ticket: BT20240506897672A
User @Solarity received updated driver that fixed LX200 issues.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
LOGS AND SCREENSHOTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

I have screenshots available:

Firmware v2.5(13.13) version
Equipment configuration (LX200 Classic driver)
Polar alignment infinite loop screen

How do I extract logs? My imaging site has no internet connection,
so I cannot submit logs through the app. Please advise how to extract
and send logs via email.

I can send to:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
REQUEST
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Updated LX200 Classic driver (from ticket BT20240506897672A)
Instructions to rollback to v2.3.3 (which worked with LX200)
Instructions to extract logs without internet connection

This is safety-critical - I cannot use my equipment safely.

Thank you for your urgent attention.

Luxo

89E2n8Qp

Please refer ASAIr: The Missing Manual Version 1.0

section 19 details submitting bug reports online and offline;
section 22 provides instructions on reverting to version 2.3.3

PMTeam@ZWO

89E2n8Qp Hello, we have noticed this issue and would appreciate it if you could provide us with more information. If you are willing, please try the following operations at your convenience:

Perform a clean update: first restore the firmware, then download the 2.5 version of the app and upgrade to the compatible firmware.
Try to reproduce the problem. If the problem recurs, please long-press the "ASIAir" icon on the homepage for 5 seconds to access the logs.

You can send us your screenshots, screen recordings, and logs via email, and we will do our best to find the cause.

Tayfun

That night, I noticed another issue. While searching for a comet, when I scroll down the list, it gets stuck at the year 2020 and the application crashes.

Luxo

Could you try to see if that is repeatable, and give details of exactly what you did or looked up so ZWO can try for themselves ?

One of the issues I suspect is that (1) their "logs" don't really provide much help pinpointing a problem and (2) unless they can reproduce the issue they have no clue where to start looking.

More to the point unless a bug can be reproduced ZWO cannot confirm whether it has actually been fixed.

Looks like 2.5 is two steps forward, two sideways and two backwards.

johnpd

Due to flaky USB2 issues with my trusted old ASIAIR Pro, I decided it was about time to get a new ASIAIR Plus. I updated it to v2.5 hoping that at least everything essential would work. I started playing around with it inside (weather a little nasty here now) and things seem to go well. I tried my main camera (ASI533MC Pro), my guide camera ASI220, and the newly installed EAFN. Things seem to be working ok, but all of a sudden I started getting freezes in Preview mode with my main camera. It dropped the connection to my iPad. I was sitting right next to the ASIAIR so I did not understand that. I checked the iPad's Wi-Fi connection and it said that it was connected to the ASIAIR. My only option was to restart the ASIAIR. This happened at least a half dozen times in a row. The last time I tried for a short time it seemed to be working again. I have extracted logs. One of the ZWO support persons here said not to restart the ASIAIR if an issue surfaces, but I had no choice. If ZWO wants them I will gladly send them.

Luxo

Ok it’s rapidly becoming clear 2.5 is not fit for use and once again ZWO have not addressed the bugs that cause it to crash. When you need your gear to work the only solution is

Do NOT update to 2.5.
Revert to version 2.3.3.

Even that is prone to crashing but at least it works most of the time.

@ZWO nice try but until you fix the bugs that cause the crashes this is not fit for use.

I will suggest everyone revert to 2.3.3,and no more testing until you fix these crashes.

johnpd

Luxo
Fortunately I have two iPads available: an old Mini and a Pro. I updated the Mini to 2.5 and used that. The Pro is still golden with v2.3.3. I can use that with my old ASIAIR Pro. I just have to use USB2 ports on my camera. The only thing is that I am not sure of is whether v2.3.3. will handle the new EAFN I had installed on my RedCat 51.

JohnD

89E2n8Qp

@Luxo5 @PMTeam@ZWO

URGENT: iOS Rollback to v2.3.3 Required

Thank you @Luxo5 for the Missing Manual reference and your latest
updates confirming that v2.5 is not fit for use!

CRITICAL UPDATES FROM LUXO5 (8 hours ago):

✅ Successfully reverted to v2.3.3
✅ PLAN mode working on v2.3.3
🔴 Confirmed: "v2.5 is not fit for use"
🔴 Recommendation: "Everyone should revert to 2.3.3"

I completely agree and urgently need to follow this advice!

MY CURRENT SITUATION:
✅ Successfully reset firmware: 13.13 → 10.40
✅ Current status: App 2.5(10.40), Firmware 10.40
❌ CANNOT get v2.3.3 app on iOS

iOS ROLLBACK CHALLENGE:
Following Missing Manual Section 22.2:
✅ Reset firmware to 10.40
✅ Deleted and reinstalled app
❌ Result: Still got v2.5(10.40), not v2.3.3

Attempted iMazing method:
✅ Downloaded iMazing, connected iPhone
✅ Found "Manage Versions" feature
❌ Requires paid license ($44.99)

URGENT RISK:
Every connection shows "Update Firmware to 13.13" prompt.
Risk of accidentally updating → permanently stuck on v2.5
(which Luxo5 now confirms is "not fit for use").

URGENT REQUEST TO @PMTeam@ZWO:
Given Luxo5's strong recommendation that EVERYONE should revert
to v2.3.3, could you please provide an official iOS method?

TestFlight beta link for v2.3.3?
Direct IPA download for v2.3.3?
Alternative iOS rollback procedure?
Temporary fix until v2.5 crashes are resolved?

EQUIPMENT & CRITICAL ISSUES:

ASIAIR Mini (Serial: e9ffca8a)
Meade LX200R 8" (GPS SMT v4.0g)
iOS device
Issue 1: STOP command non-functional (SAFETY CRITICAL)
Issue 2: Polar Alignment infinite loop
Ticket: #35573

This is now even more urgent given the community consensus
that v2.5 should be avoided entirely.

I cannot safely operate my equipment and risk being permanently
locked into v2.5 if firmware accidentally updates.

Thank you for urgent assistance! 🙏

P.S. @Luxo5: How did you successfully revert to v2.3.3?
Are you on iOS or Android? Any iOS-specific advice would be
greatly appreciated!

Luxo

89E2n8Qp
Going back to 2.3.3 is detailed in
ASIAir: the Missing Manual

Section 22.- Follow instructions carefully, you have missed one or more steps.

Tsstflight is not used and there is no link. That you ask this means you did not read section 22 of the manual.
iMazing fetches the app directly from the App Store.

In your device SOFTWRE UPDATES MUST BE SWITCHED OFF AND STAY OFF otherwise it will update straight back to 2.5. Never, ever turn it on.
When you apply the firmware reset disconnect from ASIAIR while that happens and DO NOT update it (again, if you do let it update you will have 2.5 firmware).
in iMazing, select "Manage Apps". Click LIBRARY (you must select the LIBRARY, not DEVICE). There you will see all your apps listed including ASIAir.
You must RIGHT-CLICK on ASIAir to get the popupmenu to show all versions. Most fail to RIGHT CLICK.
Download version 2.3.3 to the library. You can have severeal different versions in the LIBRARY.
Once it has downloaded to the LIBRARY, select the version you want and install that in the DEVICE.

Open the app on your device, reconect to ASIAir and instal firmware for 2.3.3. It should show version 12.03.

PMTeam@ZWO

geirhagabr Hello，Please turn off this button.

89E2n8Qp

PMTeam@ZWO

Thank you for noticing my issue (I'm user 89E2n8Qp, Ticket #35573).

I appreciate your "clean update" suggestion, but I'd like to explain why I'm requesting v2.3.3 access first.

My Experience:
My issue with v2.5 has an interesting pattern:
• Initial startup: direction keys and STOP work fine ✅
• After repeated "NEXT" during Polar Alignment: problems occur ❌

STOP command stops responding
Polar Alignment appears to loop indefinitely
Equipment becomes difficult to use

I'm not certain of the cause, but this pattern might be significant.

Why v2.3.3 First:

@Luxo5 mentioned: "I have reverted to v2.3.3 and PLAN now works correctly"
Testing v2.3.3 first could help determine if the issue is v2.5-specific
Weather-dependent: reproduction requires clear skies (currently rainy)
v2.3.3 baseline → then v2.5 comparison might provide useful data

iOS Access Challenge:
Attempted iMazing (Missing Manual 22.2):
• Requires $44.99 license for version history
• Apple ID never had v2.3.3 (new purchase)
• Cannot access v2.3.3

Request:
Would it be possible for ZWO to provide official v2.3.3 access for iOS?

TestFlight link?
Direct IPA?
Alternative method?

What I Can Offer:
If v2.3.3 becomes available:

Test with my LX200R setup
Report observations
When weather permits: compare with v2.5 behavior
Share information that might help

Equipment: ASIAIR Mini (e9ffca8a), Meade LX200R 8", iOS 26.1

Detailed email sent to luffy.liu@zwoastro.com and tianfeng.chen@zwoastro.com.

Thank you for your consideration!

PMTeam@ZWO

Luxo Hello Luxo, thank you for raising the issue you encountered. We are currently investigating the firmware crash issue you reported a few days ago caused after AF during planned shooting. We conducted stress tests overnight, continuously running AF, but the problem did not recur. According to the logs you provided, firmware information was lost due to a reboot. Could you please tell us the probability of this issue recurring? If this problem occurs again, please try extracting the logs and sending them to us again, and we will do our best to find the cause.

Luxo

PMTeam@ZWO

You have the full sequence described in the email I sent 30 December. rebooting is inevitable - I had to remove power to bring the ASIAir home, and restart it there to extract anything - the telescope site does not have permanent power or internet.

Chose NGC1566 as a target east of the meridian so that a flip would occur.
ASIAir was set with AUTORUN with Exposure = 180s, 100 frames. Meridian flip allowed, with the guider set to recalibrate, and EAF to AUTOFOCUS after the flip.
EAF was also set to AUTOFOCUS after 30 minutes.
Guider found a good bright guide star, calibrated and guiding ran very nicely around 0.3 arcsec RMS.

What happened…

First sub was at 2025/12/29 22:14,
After 9 subs the median flip commenced at 22:42 (NGC1566 transited at 22:43)
The guider found a guide star, recalibrated, and EAF AUTOFOCUS was OK
The 10th sub at 22:49.
After 10th sub ASIAIR refocused at 22:49, and started next sub
A HARD CRASH followed at 22:50.
Rebooted ASIAir, Pressed SYNC TO MOUNT to update ASIAir with the current mount position (it had drifted off target)
Used the Star Atlas to re-centre on NGC1566 with plate solve - the plate-solve worked.
Restarted AUTORUN at 22:57.
Took two subs followed by HARD CRASH at 23:36
Rebooted, re-sync to mount, and restart AUTORUN.
Took 10 subs followed by HARD CRASH at 00:13
Rebooted ASIAir, Pressed SYNC TO MOUNT to update ASIAir with the current mount position (it had drifted off target)
Restarted AUTORUN, first sub finished at 00:23
After 10th sub, AUTOFOCUS commenced and finished.
HARD CRASH followed the AUTOFOCUS.

So… 4 x AUTOFOCUS, each time followed by a hard crash requiring power-off-reset of the firmware.

It appears your logging is buffered in memory and is not flushed to the SD card. Hence, in a firmware crash the log is lost, not stored. Suggest you use a binary stream and flush it to storage after every message. Once the problem is resolved in a later version you can remove the flush command (I lknow it is not good for EMMC or SD storage).

The weather is overcast here - the next opportunity might beJanuary 9 or 10.

PMTeam@ZWO

Treebeard Hello, could you please provide us with the log file? This would help us find the cause.

Luxo

PMTeam@ZWO

From a software perspective my suspiciion was it is somehow related to the AUTOFOCUS occurring automatically.
However ... given all the issues historically with versions 2.4.X, its quite possible the cause is entirely unrelated and has been present for a long time - earlier versions have also been unreliable.

There is also the issue with WiFi failing at random as reported by others here for many years.

Luxo

OK... looking at the ASIAir on my bench with a port scanner, I see its IP is 10.0.0.1 and ports 22, 139 and 445 are open.
Port 445 is the SMB server (for extracting files).

It appears to accept an SSH connection on port 22... so, ZWO:

What is the password to log in as pi ?
I can see you have changed the default password.
You can email me privately, you have my address.
There should be kernel logs that can be extracted, right ?

Alternatively I can put the ASIAir on my LAN and set up port-forwarding so you can SSH into it from your end using port 22 and my public IP. It's been a while since I did this stuff but can do again.

Luxo

89E2n8Qp

I have done this with iMazing for about 20 users in my astro club, it worked perfectly for all. CloudyNights members know about it and are doing the same.

It doesn't matter that you did not have 2.3.3 previously. If you have ever installed any version of ASIAir on your device, the App Store will allow iMazing to access all of the released versions right back to version 1.0.

There is nothing stopping you doing what is described, apart from spending $44.99.
It is small change to have your rig working again, considering what you've sunk on the rig..

Up to you.

Forget about TestFlight ZWO won't do that again except for a beta, and that's going to have a time limit.
The point about the iMazing trick is that it instals the full, released version of 2.3.3 with NO TIME LIMIT.

PMTeam@ZWO

89E2n8Qp Hello, we have checked these two email addresses but haven't received the email you sent. Could you please send it again? Thank you for your feedback.
luffy.liu@zwoastro.com , tianfeng.chen@zwoastro.com.

89E2n8Qp

Luxo

Thank you so much for clarifying! I didn't realize iMazing could access all versions regardless of previous download history - that's very helpful to know.

You're absolutely right that $44.99 is relatively small compared to the equipment investment. However, I'd prefer to explore official solutions first.

I've already sent an email to ZWO support (luffy.liu@zwoastro.com, tianfeng.chen@zwoastro.com) requesting official v2.3.3 access for iOS users. If the official solution doesn't work out, I'll consider purchasing the iMazing license.

I really appreciate your patience and guidance. Your Missing Manual has been incredibly valuable throughout this process!

Thank you again!

Best regards

« Previous Page Next Page »