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.
ASIAIR v2.1.2 Public Beta Released！
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!
Tech@ZWO I was testing with an ASIAir Plus on an AM5 mount. The guide scope was 240mm f/4. I do not have the logs but I tested the beta and could not get the guiding I am used to getting. If my memory is correct (and I think I documented it in another post) I was getting about 0.9 guiding with this Beta with very few corrections in guiding. It would wait until the graph was beyond a reasonable error before correcting. I finally reverted back to the current software that is on the app store and guiding was back to 0.5 to 0.6 total error.
- Edited
IDK, maybe people are paying too much attention to guiding performance when it's not needed? With my smaller refractors I only need to guide under 2"/pixel and my largest at 0.85"/pixel so as long as I can guide under that consistently I really don't care what the guide setting default to. On my AM5 and AM3 that's really easy guide below these image scales.
However, with my C11 (which is at the weight limit of the AM5 anyway) I need to be guiding under 0.35"/pixel which is super hard on that mount no matter what setting are available to tweak.
At the end of the day, as long as your stars are round after a 5-10 minute sub, who cares?
hyiger I agree totally about the round stars! My image scales vary too and most my scopes are fine at 1rms. However, since the minmo change from 0.1px to 0.2px my AM5 rms numbers have doubled and now my largest 115mm scope is having issues getting the numbers I need which is below 0.7rms. My slope is fairly good at 0.155 arcsec/sec so that says a lot for people with worse slopes. It is a hard time of year to test now as my skies are just not allowing it!
Great news on the change. Once this is released, if the default stays at 0.2, I can imagine a ton of traffic over a Cloudy Nights with the topic heading "After upgrading to ASIAir 2.1.2 my guiding is bad" Most likely coming from a guy with a RedCat 51 and a 3"/pixel image scale who was guiding at 0.5"/pixel and is now 1"/pixel.
MarcK find the image resolution of your camera scope combination. There are a few online calculators such as Astronomy Tools CCD suitability calculator. That will give you your setup resolution. My 644mm scope using a camera 3.75uM pixel size resolution calculates to 1.2”, so I try to get my guiding under 0.6rms. It is best to guide at half the size of your resolution setup resolution or better. It is based on the Nyquist sampling Theorem.