ASIAIR v2.4.1 has been released!

PMTeam@ZWO

We’re excited to announce that v2.4.1 is now officially available on the App Store and Google Play!

This update was made possible thanks to your valuable feedback during the beta testing phase. Many of you helped us test the fixes under less-than-ideal weather conditions, and we truly appreciate your patience and support.

Here’s what we’ve fixed in v2.4.1：

Fixed occasional abnormal meridian flip
Fixed overexposure issue in flat field auto-stretching
Fixed the exposure time setting of polar calibration (upper limit is 10s)
Default theme mode now set to dark (Android)
Fixed the occasional issue where shooting sequences were not displayed in Plan mode (Android)
Fixed occasional exposure time reset to 3s/10s during Live / Autorun / Plan mode (Android)
Fixed celestial object filter not working (Android)
Fixed the occasional problem of guide image not refreshing (iOS)
Fixed the issue that Plan cannot add LBN and other targets (iOS)
Fixed the issue of repeated switching between single frame and stacked image during Live shooting (Android)

paulitoweb

Hello PMTeam@ZWO , I am a bit confused with the 2.4.1 and 2.4.9 versions…
Is the 2.4.9 the “old” 2.3.3 ?
Is the 2.4.1 the last stable version of 2.4 ?
Thanks in advance for clarification
Paolo

rikiau123

perfetto

R0k9pZfT

Yet during beta I continued to have unacknowledged and unresolved issues with guiding even though I posted and asked about them about half a dozen times.

andrelucasmelo

After the update, the image solver time went up alarmingly. It's taking me almost 300 seconds to solve each frame of the mosaic.

azskyguy

Yes. plate solves take forever.

andrelucasmelo

In addition to the bug of the meridian flip continuing and the increase in image solver time, when I did the meridian flip manually using preview and motor controlar on Asiair and after waiting for ASIAIR not to try to undo it about 10 times, the DEC axis was inverted. Every time ASIAIR tried to go north, the motor went south. I spent 2 hours and 30 minutes in the cold trying to solve it until it finally worked.

andrelucasmelo

In contact with support, it was recommended that the new plate solve algorithm be used to solve the high image solving time, since several errors in the previous algorithm were found in the logs. The time has been reduced. Other problems have not yet been retested.

azskyguy

That's interesting. The last advice was NOT to use the new algorithm. At any rate, plate solving always worked fine until these recent updates. 2.4.1 should not have been released if it's default plate solve function does not work, which it didn't for me last night. I sent a log.

I don't know what happened at ZWO, their software, at least for me, was always stable.

Javier_Covancho

I'm starting to wonder whether to download the new version or not. I think I'll wait a bit.

PhMur

That's great but.... The map is empty! The search button finds nothing. Tonight's best is empty,....

k6J471H7

Hello. Like others have said, plate solving no longer works. It takes a very long time to figure out that it is not working. When I set focal length to 0, this makes no difference. Everything else is working - tracking, focus etc. Tried turning new plate solving on and off. Nothing more I can do as it is late so must call it a day.

jimw85044

Same here. Plate solving does not work. I will try again after the moon comes up later in the evening. Moon light pollution may be a factor. Meridian flip acted odd but this may have been my fault. I need to do more testing.

BUG - ASIAIR will not work / load if you say use 'Approximate Location' during startup. There's no need to use GPS 'seconds' to have a good location.

I may step back to 2.3.3 again. I may end up selling my ASIAIR if these issues can't be resolved.

Jim
Phoenix, AZ

k6J471H7

jimw85044 agreed. Moon might have been a factor but after an 1.5 hours of trying to plate solve it eventually did. Against my better judgement I then set a 1 hour live session of M16 but every 3 min sub was rejected. I then tried 30 mins of auto and although the images looked fine on the screen, every saved image was poor and I could not stack within v2.4.1.

R0k9pZfT

ZWO, where did you go now that it's released? What about these issues? What about my issues with the guide settling parameters reported with two bug reports and asked about with several questions during beta?

R0k9pZfT

Found another object list filter problem. I set it to show me objects only in the NW, W, and SW. Didn't have any effect. Other filter options are working like FOV and altitude. Not direction. Bug reported & logs uploaded in case it actually is addressed.

David1303

Thanks ZWO for prompt action. I was one of the fortunates who didn’t run into any issues with 2.4.
I have updated to 2.4.1 and last night I was testing a Plan, it was a cloudy and a poor “seeing” night but I focused PA’ed and took a few images. Unfortunately after downloading this morning most of the files were corrupted and unopenable.
I have given the rig a good look for cables snafoos etc, reinstalled the software (iOS) but according to the forecast will not be able to take any more images for a few days. Do I need to reformat the eMMC? I didn’t particularly want to lose the images yet off the ASIair Mini device as I may want to use the GoTo off some of the fits files.

jimw85044

I decided to sell my ASIAIR Plus 256GB today. I don’t get out as much as I would like and can’t afford to be a Beta or even an Alpha tester for ZWO. I have concerns about ZWO's SW development, test and release process. I have been using NINA since release 1.1. Release 3.2.x is stable, feature rich and can be controlled from Android or iOS devices now. I will be using NINA full time.

Jim

azskyguy

Starting to think the same thing. I've always liked the ZWO software... but to put out a release that can't do a meridian flip and can't plate solve, along with all the other issues, says something is wrong with their entire process of releasing software.

At the very least ZWO owes its customers an explanation, and assurances that whatever oversights caused this will never be repeated.