Just for the record and to put some of the off-topic statements from lorenzocold into perspective (some of those posts were rightfully removed by the admin because of the usage of profanity):

I have been using both the ASIAIR and Raspberry Pi 4B-based “freeware” solutions. Stellarmate is not really free, Astroberry seems to be abandoned (like many other non-profit GitHub “solutions”), Indigo is kind of open, but the full GUI is not really free either.

  • KStar/EKOS is free and well supported, but lacks an easy GUI on the iPad. I tried Stellarmate… not as easy and not as stable as the ASIAIR. Lost a few nights with Stellarmate as well.
  • KStar/EKOS has a very steep learning curve and endless tabs and menus to access literally hundreds of “tunable” settings, which are not the 1-2-3 approach by the ASIAIR.
  • With KStars/EKOS you need a remote login and have a very low quality typical LINUX-GUI.
  • Besides the Raspberry Pi that is running the indiserver (KStars/EKOS), you still need a second computer. A phone or iPad running VNC is not a good a solution, because of poor readability. Again, I found Stellarmate not really adequate yet.
  • There is no live imaging/stacking in EKOS, no easy mosaicking, no “just-click-here” for setting up hardware. I always had trouble focusing with the EKOS tools… tons of non-self-explanatory settings, no clue what they do… in the end the focusing routine runs forever and does not find the focus. The focusing interface in the ASIAIR is simply brilliant. I use it either fully automatically or manually with a Bahtinov mask.
  • The ZWO hardware is IMHO superior to the Raspberry Pi. The first ASIAIR was a RPi3, the AA Pro was an RPi4B, the AA Plus already used the industrial compute module version of the RPi4B, the new ASIAIRs are using new hardware, great external antennas, better on board memory than the off-the-shelf RPi. The new RPi5 still has the same poor WiFi antenna for the 5GHz network as the RPi4B. I use the AA mini at a distance of 20m to 30m, set-up in the garden, while I am in the warm house. Impossibly with the RPi4/5 without extra routing hardware.
  • The AA boxes have a 12V input and several 12V outputs, which you do not find on a RPi4/5, either.
  • OK… the new AA software seems to have issues with the guiding settings… if this is the only issue… I am sure ZWO will come up with a solution.
  • Ranting and using profanity will not make anyone’s case more solid nor does it provide any technical info on the actual issues.

lorenzocold

Dude... We all know this. Just chill out. It is well known that ZWO is violating open source and GPL licenses. You can choose not to use it and use something else. Get NINA setup then. Anyway, stop ranting on here like a lunatic.

I cannot get the 1228 release to connect. Using an S4 Tab; I get the error "Couldn't get IP address"? Now, I cannot get to the "RESET FIRMWARE" screen?
Any ideas?
Charles

ZWO, when will you bring the development team back to work on the ASIAir instead of working mostly on the SeeStar? We have a Beta of a few new features, but you cannot even fix the MinMo issue that is in that Beta. I am now concerned that the ASIAir is not going to see much further development. Please, correct me if I am wrong.

    4 days later

    charding

    Just speculation here. I'm thinking that these delays are being caused by them violating numerous open source and GPL licenses which they are unwilling or unable to figure out how to comply with. If I were them, I would be dumping resources on writing clean software that was their IP only. Maybe they are doing that. If so it could take a while.

    Madphotor great. Just don't post about it in this thread that has to do with the Beta. Create a new thread for your issues if you are being genuine.

    Can we please keep this thread to do with the Beta only. That's the only way it'll stay relevant and important discussions don't get lost in the noise.

    Madphotor sure thing. Stop making inappropriate posts and I'll be happy to.

    And I don't post videos on YouTube for subscribers. It's actually as a record of what I do with the ASIAIR and if it happens to help others then that's great.

    JTSAN It will prompt 'there is a new version firmware to update' after you install and run the new version app.
    So do not update the new app won't lead to a firmware update.

    Chetorolac We are looking into this problem, if there is any news i will tell you.
    Thank you for your feedback.

    lorenzocold As you did not describe the problem you have, just left many useless or discordant comments.
    Can you please tell me the problem you have and your needs? thank you in advance.

    Sorry for not checking the situation in this post promptly. I believe that everyone who posts and discusses on the forum hopes to communicate and solve doubts and problems with other astronomy amateurs in a harmonious atmosphere. We hope that the forum can always maintain a relaxed, happy, and harmonious atmosphere as well.

    Therefore, we will first delete some inappropriate discussions under this post, but it does not mean that we ignore the voices of users, I will reply and handle each user's problems one by one later. We sincerely hope that everyone can communicate harmoniously. If any users continue posting inappropriate comments, we may ban to post. We apologize for any inconvenience caused by these actions, hope everyone can understand.

    There are also a few things I would like to declare:

    We are very grateful for the support of all users and attach great importance to the ideas and suggestions of each user. We will continue to make every effort to provide better service to every user.

    We apologize for the decrease in updates and releases of Asiair recently. Indeed, we have temporarily reduced the frequency of updates because we have allocated some of our energy to Seestar, but we have never given up on Asiair users and have been paying attention to and resolving their issues, we will recover the updates as soon as possible.

    Thank you for your guys support again.

    charding About the mini move problem, we are doing more tests for verification, and consider if the change the value back to 0.1.

    [unknown] thank you! I believe that moving it to 0.2px from 0.1px solved a few issues regarding oscillation on a few AM5 mounts but unfortunately it is a worse option for most mounts that do not have these issues. I has put my guiding numbers almost to the point my mount is not achieving its specified <0.8 rms guiding promise by ZWO. Is it possible to just have a set of numbers like the guide rate tab check box has, say 0.1, 0.15, 0.2. And have it default to one of them. You have given us everything else required to get great guiding and this one more setting would be all that is required to give total PHD2 equivalent functionality and it is important. Thank you for looking at this more!

      Tech@ZWO here are my before and after logs. Worse with 0.2px minmo.

      phd2-guidelog-2023-09-22-202551.txt
      1MB
      phd2-guidelog-2023-11-19-181013.txt
      2MB

        Kevin_A I agree with your statement but would like finer control. Both here and the guiding exposure screen should allow for a few pre-select options and for entering a value. For example, with my AM5, I find that 1 second is best for guiding, but would like to try 0.8 or 1.2 etc.