@Support@ZWO , @PMTeam@ZWO My ASIair Plus 256GB was bricked just minutes after updating to 2.2.1. I was getting ready to take darks for a different imaging workflow last night, powered the unit with the recommended DC adapter from ZWO, then switched the power on. All worked fine, prompted to update to 2.2.1, then thats where the issues began.

I cannot get it to replicate the SYS32X error message now, as it will not boot up or connect to my computer anymore.

The unit is getting power, and powering the output ports, but it does not boot, does not connect to the other equipment, and is no longer recognized by my computer as a connected device when I plug it in.

As it only occurred after updating, I have reason to believe that the issue is related to the firmware, and strongly recommend users to backtrack until this gets resolved.

    Prismokay The unit is getting power, and powering the output ports, but it does not boot, does not connect to the other equipment, and is no longer recognized by my computer as a connected device when I plug it in.

    Give this a try...

    1) Turn the ASIAIR off and remove power from it.

    2) wait half a minute or so, just in case there is a large enough capacitors in there (there really isn't).

    3) connect power, but with ASIAIR turned off.

    5) hold down black reset button, and keep holding it down when turning on the ASIAIR power switch.

    6) keep on holding the rest button for at least 5 seconds. Longer duration does not hurt.

    7) release the reset button, and then power off ASIAIR again.

    8) again, wait half a minute before turning ASIAIR back on. Removing power cable in between probably does not hurt, either.

    9) (connect power back) and turn on ASIAIR.

    Does ASIAIR boot up now? See if you can find its WiFi hotspot, etc.

    If successful, it has booted with the original firmware that came from the factory when you bought it.

    Connect to the iOS ASIAIR app, and it should find the ASIAIR WiFi (if not, try connecting to the ASIAIR's hotspot). The app should then ask to update the firmware to one that matches the app.

    Steps 5) is often missing from instructions from the YouTube and Facebook shills.

    Chen

      w7ay Did all steps in order about 10 times, zero response from the ASIair, it doesnt make any sound, and even refuses the reset.

      • w7ay replied to this.

        Prismokay

        If it is within warranty, just return the unit. There is no reason you should waste any more of your time working as unpaid QC for ZWO. Let your dealer deal with them.

        Chen

          My observation so far with the latest version is…
          My initial PA will say my AZ is off by 50” and once adjusted the second PA says I am off by the same amount in the other direction. I do a third PA back to the original starting position and it is perfect.

          Guiding seems a bit erratic for the first 15 minutes no matter where I image then it settles down to under 0.5rms for the rest of the night. If I had to guess why I would say that my mounts gears are a bit sloppy and it takes awhile for backlash to be removed and it guides much better at 28 lbs than using a 5 lb scope. It is noticeable better with a heavier scope… so probably just a sloppy fit SWG. My mount also prefers 1.0s guiding and not 0.5s. 0.5s is horrible as asiair cannot react fast enough or reacts too much and no matter how small my pulses are or how low my aggressiveness is, it overshoots too much and it goes off the rails. My AM5 mount also runs very well at 1.5s in turbulent skies. My guiding setup prefers dimmer less defined guide stars, a big aperture guide scope helps but image quality not as much, as stars that are heavily defined or oversaturated no matter how pinpoint do not work well for my centroid estimation. It prefers small stars with a solid center and faded edges. So typical PHD2 requirement. Asiair still picks oversaturated stars as a guide star occasionally which is a pain due to it then guiding on a flat top big HFD star with a huge centroid it can never find the center of as the star is all saturated and not good to guide with. I then force it to pick a new star and it sometimes works out better… or I reduce gain on the fly.
          Asiair has been disconnecting frequently more often and at least 5 times a night compared to no other changes, where 1 time was infrequent.
          Overall guiding is improved but that might be due to the AM5 mount firmware update too.
          I did notice that my guide calibration when starting out was not great and repeating it a second time with no changes created a much better calibration. I also noticed on a few times my calibration has disappeared when imaging the next night. It may be human error but I am not certain… I will verify that tonight.
          Overall I a happy with my results as my images at 805mm have had perfectly round stars but the disconnects, repeated PA and double calibrations are a bit annoying to have to do!
          Here is a typical log from 2 nights ago during a big moon, smokey atmosphere and a slight wind… not too bad but still with a few blips from the atmosphere etc.

          Even though there is no mention of it in the release notes, ASIAIR Beta v2.2.2 (out for 2 days) appears to have fixed the failure (or very slow) to report coordinate changes when executing a GOTO or meridian flip. The coordinates appear to again update every second or so now.

          email address for the Beta feedback also appears to be optional now.

          Chen

          My OAG calibration and guiding seem to be working properly now. I had reinstalled the ASIair app on my ipad and did the firmware update on the ASIair today.

          Guiding is also now back to ignoring saturated stars again. This Beta release is looking good so far.

          Chen

            I still only see 2.2. beta in IOS test flight.

            w7ay

            hello Chen, thank you for the good (at least better) news regarding the latest beta. i went to the android site
            https://pgyer.com/air_beta_android

            but it advised that there were no new updates. is this beta for testflight only? (or not a "public " beta?)

            Tested it out again and sure enough my PA said I was off by 35’ 31” this time in AZ again. I had not moved my mount in 1 week of imaging. I set it at home again and did It again and it was good this time. Once I fine tuned PA to within 20” I set it at home again and went and I calibrated and started imaging and checked the goto and it was perfectly pointing on M33.
            All through the night there were no disconnects but guiding was horrible. I was getting excellent guiding with no changes 2 nights ago and the night after. I tried a few things and even though the skies were more clear I was at 1.0rms and choppy and I redid a goto to center my target and get a better guide star… after 2 hours I checked my goto and the goto target box was not even centered on M33, it was not even in the box! I checked my image capture and it was perfectly centered. I again redid did a goto and checked again and it was then back in the box. WT? I did notice that my goto target box had drifted off a few nights ago as it was just slightly off the center of M33. But tonight after 2 hours M33 was completely outside the goto box. I have never had that ever happen. So no, that is not good!
            No changes in weather except for clearer skies, no setting changes or mount movement or anything.

              Kevin_A

              Hi Kevin. I almost had the exact same thing happen to me with my AAP. I left my scope out parked in home position for at least 4 nights straight. But I had problems...towards the end of PA, all of a sudden I would get "plate solve failed" messages....but I did not get those messages at the begining of PA.(?) PA finally worked after several tries, but easily lost over an hour of clear skies.

              The following nights, I skipped PA altogether and went directly for my targets....and it centered them perfectly. But then had guiding issues afterwards. And on my last night, I had the exact same thing happen to me in which my target drifted out of center...and to the right of the screen....and it was M33 🙂

              Over the weekend, I contacted ZWO support and sent them my logs. They said they would get back to me by today.
              Best of luck!
              Jeff

                AstroJym
                Hey Kevin. I just noticed your wifi extender. I just bought one, TP-lInk AC1900, but for the life of me I can't get it to connect to my ASIAIR +. How did you do it? I tried through Station Mode, but I I always get a "auto reconnect" message every 2 minutes. So I'm doing something wrong.

                Any insight?
                Jeff

                  AstroJym you must use 2.4G. Originally I found 2 ways… use a ethernet cable to set it up and or go into the station mode settings and select the 2.4 wifi handle.

                    Kevin_A
                    So the ethernet goes directly into your extender just for "set-up"?, or do you have to leave it plugged in all the time?

                      AstroJym i am not sure if I can trust the PA at all now.
                      If it is actually out 35’ and then I try it again and it says it is 20” and good and then when I start imaging it might be actually so far off and why it has drifted off target in software but guiding is keeping it on target physically. I may have to put my Polemaster on the side of my mount tonight and verify if PA is whacked!
                      My 3.5 hour M33 uncropped looks fairly decent and stars are round at 805mm even though it is not great for my resolution guiding 1 night at 0.8-1.0rms total. This image is just stacked as is and minimal post processing.