ASIAIR v2.2.1 has been released!: Page 4

ASIAIR v2.2.1 has been released!

w7ay

Kevin_A on 8th gen ipad

Yeah, that is the previous Beta. This is the history of Betas (the one on the left panel is the current one):

In the past, I have noticed that I get Testflights half a week or so before others (absolutely no idea why -- ZWO might be pushing it to real beta testers who are known to their engineers). So, just wait a day or two for v2.2.2.

Chen

minimoto71

w7ay There should be a new link to TestFlight for the Beta 2.2.2 as with the links provided in this forum you only get the version 2.2. Could you publish the link you use to test the latest beta? Thank you.

raurgo

Version 2.2.1 does not work for me, the video function remains black.

Phil-R

Overall I really like the 2.2.1 update and it’s working fine on my asiair V.1 and asiair mini. The iOS app works fine on my iPhone 13 and iPad 7th generation too.

BUT: please, please, PLEASE return the ability to copy the flats exposure times from an Autorun to a revised Autorun for the flat Darks.
Removing this functionality is a BIG MISTAKE.

zephirus

I guess by the lack of ZWO response they are fine hosing up ASIAIR imaging ...

AstroJym

zephirus
They are actually on holiday this week as per support staff.

protostar

hey theres currently a huge bug with the framing feature in this update. before it worked fine and now with the forced update i cannot use the framing to correctly show what angle my camera is looking at
here is what i wrote on astrobin and theres a lot of people who echo the same problem.

"So when it comes to framing in skyatlas (or also plate solving an image in the storage to align to that), it seems that the asiair only knows its orientation on the first actual preview image and then when refreshing to see how far you need to rotate the image train to get the frame you want, it is just completely wrong?

Even when hitting refresh multiple times it seems to jump to different rotations, and then when rotating it CCW for example, on refresh, it shows that i rotated it CW??

Never had this issue before this update and even tried two different cameras and had the same issue with both, its seriously cut into my imaging times too because the only way to frame reliably with an older image is to navigate into the image management to the frame and resolve it each time and goto, as that first orientation in skyatlas "seems" to be correct, but after refreshing its just wrong"

Link to the forum thread to see I'm not the only one with this issue

AndrewV

protostar The update was not forced upon you. You have the control on your device to turn off auto updates and then only apply them once any issues have been sorted out if they occur. It is in your control.

tomstein

protostar I have the same issue (on Android). There is also a thread about this on CN, which indicates more users are affected and this is not a single case.
My 'work around' right now is to only use the sky atlas reading when initially opening it up. Then everytime I have changed rotation/framing, I jump out and back in to it because this is the only time I can trust the angle degree reading.
Very tedious of course and certainly easy to fix, so I am hoping we get a proper solution for this in the next release.

minimoto71

protostar For me the framing issues are more related to the current position and not the rotation. In previous versions, when I set a framing, it solves and place the telescope exactly in the right position and also in SkyAtlas. Currently, with versions 2.2 and 2.2.1 both in iOS/iPadOS/macOS, the framing appears moved some degrees from the actual position of the telescope. So I see a framing in my camera an a different one in SkyAtlas. So I have to "cheat" the map to point exactly where I want be. That's a problem when I want to return the next day to the same position. Yes, I can solve a previous image and go to a previous session's coordinates, but the map will show again a wrong position I will have to check the camera to be sure I'm in the right one. Framing in SkyAtlas should be corrected because it fails often even with stars as I pointed previously.

w7ay

minimoto71 Could you publish the link you use to test the latest beta?

Same as what everybody uses.

Chen

minimoto71

There are people like me in Astrobin complaining about the framing, how well it used to work in previous versions and how it is pointing incorrectly in the last 2 version ( 2.2 and 2.2.1 ). And the issue with the incorrect pointing to the stars when in wide angle view in SkyAtlas haven't been resolved neither after noticing it during the 2.2 beta period here. So please, with the next release, take the framing issues seriously because it's affecting the way we work with SkyAtlas and the ASIAir.

protostar

AndrewV haha dude the update is forced on the hardware side if the app is auto updating by default, why are you defending a forced update practice?

yes ive rolled back to the actual stable update and disabled auto updates on the app side, but no hardware should be unusable when opening your app to control it and "forced" to update before you can continue, unless you want to take 30 minutes to go find an apk and manually downgrade before your session

minimoto71

w7ay For any reason, the beta didn't appear for all of us. Now that is official, it does. Thank you.

Nolomar

I am not able to update from v2.1.5.
When 20% of the ASIAIR restarts... any ideas?
I've never had a problem like this when I've upgraded before.

Fortin13

I’m doing the update, everything is fine. Whenever I shut down my asiair pro and start it back, it ask me to do the firmware update again. It’s the same if I shut it down with the power button, the app (shut down) or if a do a restart with the app. My current firmware is 10.74 and I’m trying to install 11.26.

protostar

minimoto71 let me know if the new 2.2.2 beta fixes it for you, i dont think ill get a chance to test it for a bit!

Andrix

minimoto71 Yesterday i was in the same situation, the update is not available both for macOS and iPhone.
Today is available for both devices

minimoto71

protostar Ok, I will test it as soon the sky is clear again in my area ( that's suppose to happen on Sunday/Monday ).

protostar

protostar testing the new beta tonight, seems like the framing is fixed at first so will see if it drifts or how it does on the meridian flip

Kevin_A

My M15 imaging test went very well last night with a great PA, great imaging conditions considering it was a 94.4% full moon…. Except for one thing!
What happened to my goto staying on target? My imaging was centered perfectly, guiding near 0.4” total and stars nice and round! I imaged for just 64 minutes on M15 at 805mm using a asi585mc pro.
What is with this goto drifting off of target after 1 hour even though my images are perfect and correct? I did another goto and it was perfectly centered again!

sompi68

Kevin_A Great Kevin

w7ay

Kevin_A What happened to my goto staying on target?

Pretty sure it is a Dither bug -- a dither that is applied as a random walk to the most recent x,y position, rather than a random vector that is applied to some original x,y position. I wonder if this bug is introduced because they are starting to plan allowing dither without autoguiding that people have been asking for.

ASIAIR allows up to a crazy Dither distance of 30(!!), which after just 20 dithers with this bug, can lead up to 600 pixels of movement from the original plate center.

Until ZWO fixes the bug, and you don't have much cropping FOV to spare, choose the smallest dither distance in Dither settings in the Guiding Advanced Settings that the camera can tolerate. 1 pixel if monochrome camera, 2 for Bayer camera.

Chen

« Previous Page Next Page »