lorenzocold
Well good bye then.
@PMTeam@ZWO @Tech@ZWO care to get rid of those off topic and unhelpful posts above?
lorenzocold
Well good bye then.
@PMTeam@ZWO @Tech@ZWO care to get rid of those off topic and unhelpful posts above?
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.
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.
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.
Do not talk to me again
PMTeam@ZWO @Tech@ZWO think you need to step in here. It will surely help.
AstroDude42
Thank you for your feedback, could you tell me more information of your devices?
and do you have some PHD2 log before and after the mini move changes?
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.
[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!