Are the bulk of problems (bugs) reported with this release experienced by folks using non-ZWO devices?
Reason I ask is that I seem to be doing fine with this release, however I am using a fully-ZWO setup for mount, cameras and EAF.
One side note: I just noticed my AM5 is running the previous version firmware and not the very latest.

  • w7ay replied to this.

    GoKidd I am using a fully-ZWO setup for mount, cameras and EAF.

    The ASIAIR only supports the EAF and astro cameras.

    That being said, I have been using a non-ZWO strain wave mount since May of 2019 on the ASIAIR, once ZWO finally got a mount (and RST-150h) on loan for code development. You should have seen the "quality" of the code before RainbowAstro took pity, and gave them a free loaner. Autoguiding has also been working well with the non-ZWO mount (way better than ZWO mounts FWIW) too, once it became available on ASIAIR.

    Many of the problems for ASIAIR is that ZWO has never even touched one of those remaining troublesome mounts, and their developers are very poor at reading engineering documents -- they need a real mount to work on. I think they use trial-and-error coding.

    The same is probably true with the DSLR and mirrorless cameras. They are too cheap or too poor to buy them for code development.

    Chen

      Yeah. I've thought about an AM5 but am leaning more towards an iOptron HAE29 / HAE29EC mount since I'll be doing unguided EAA with a C8 SCT, Celestron f/6.3 Reducer and ASI294MC Pro camera (which I currently do on my HEQ5 Pro mount without issue).

      It's just a better strain wave/harmonic mount than the AM5 (even if it's a little fiddly but those little hex/Allen key screws can be replaced with small knobs).

      I'm still on 2.1-10.74 firmware on my ASIAIR Plus 32GB, though.

      Considering rolling back to 1.9.1 actually (since I'm on Android/Windows 10 with BlueStacks 5/Windows 11 with Windows Subsystem for Android) just to really experience the difference between that, the 2.1-10.74 firmware and the current 2.1.2 firmware.

      wvreeven Unfortunately not, it's an iMac 27", not easy too use in the country side ;-)

      I'm running 2.1.2, 11.01, it seems on my older TAB 4 android device; that the partial screen issue on the bottom edge that a previous beta had corrected is still there. Or, it happens randomly. I don't always notice it and it's easily corrected by a refresh.

      Chuck

      PMTeam@ZWO Dear ZWO Team, after three months of bad weather, it is not a good thing that the only clear night fails due to an update recommended by you.
      My 2400 doesn't work anymore and neither does EAF.
      We customers cannot always be human guinea pigs, we do not always have time and money to waste nor infinite patience.
      Thank you.

      Tech@ZWO do you have any idea when the canon dslr bug will be fixed. My equipment is currently useless and has not been working for 1 month (ie ever since I upgraded to 2.1.2)

        2.2_0415
        Build 678
        Firmware 4006

        Released 12 hrs ago. On gpyer.com/ for Android. No update info given. I'll wait.
        Chuck

          L5rEAosd
          can you provide a link for build 2.2_415 please. when i go to the pgyer site the latest build i see is from 2024-04-02.

          thanks

            L5rEAosd

            Thanks, it's easy to get confused re how (and where) ZWO post "tests" versus betas versus releases. much appreciated

            Size
            748.3 MB
            Publish at
            4 Hours ago
            Version
            2.2_0416
            Build
            679
            4007

            dcashel hey, if you're also facing the issue that the new images have 1px less in with i wrote a python script that lets u easily resize the older images. To prevent data loss i made it save the image as new fle (with "s_" prefixed)

            if you'd like to try it out

            but it doesn't help with the color issue (which i don't completely understand yet)

            I connected my a7Rv to ASIAIR mini with the latest firmware, and my camera settings were set as instructed, but it didn’t work properly. There was no iso setting available, as well as exposure settings, and it said “ Exposure Failure.”



              It's like popcorn at pgyer now as another 2 or 3 releases. Not sue what's happening?

              Version
              2.2_0417_2
              Build
              681
              Change Log

              • 4009

                Hi folks !
                Found the solution for my RAW problem with Nikon Z6 II.
                It's not ZWO Firmware, it's me.
                For shooting I use U3 mode with specific settings.
                When Asiair do preview it works but when Asiair do a plate solving it tells me there's a RAW problem.
                If I tried to do a new preview after the plate solving, I had the same message about RAW problem. Strange...
                So I've downgrade Asiair version to 2.1 and 2.0 with an Android terminal. Same problem.
                But in fact the problem was that for plate solving, Asiair switch Nikon Z6 II to M mode automatically.
                And in the M mode, I was in JPEG, not RAW.
                Its a little bit strange, but's it the explanation.

                L5rEAosd Looks like normal daily builds to me. They seem to be triggered manually by some developer because they're missing on weekend days.

                Hi, I've also had problems with the images on my Canon 600D. The images are not the correct color and the pixel size is also incorrect.
                When you plan to fix this problem.
                I just hope I don't have to wait months for this problem to be corrected.
                It would also be nice if they turned the live view mode back on for the DSLR cameras, it was very useful.