ASIAIR v2.1.2 Public Beta Released！: Page 10

ASIAIR v2.1.2 Public Beta Released！

Kevin_A

[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!

charding

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.

Kevin_A

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

Tech@ZWO

Kevin_A Hi Kevin,
Thank you very much for your log, and we will release the option to choose the mini move in the next version.

Tech@ZWO

charding Thank you for your feedback, i conveyed this to our ASIAIR team.

charding

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.

hyiger

charding

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?

Kevin_A

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!

MarcK

hyiger
Kevin_A
Just out of curiosity, what is the formula for calculating the maximum RMS of your own setup?

Kevin_A

Tech@ZWO thank you for listening to our requests!

charding

Tech@ZWO Please make sure we can enter any value that is between a reasonable range. I do not want that we can choose only 0.1 or 0.2
While you are at it, being able to enter a value for guide camera exposure would be great. The 0.5, 1, 2, 3 is too limited.

charding

Tech@ZWO this is not a good implementation. Having two values to pick from is bad. Please implement the entry of a value and maybe limit it to the transfer 0.8 to 0.25

hyiger

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.

Kevin_A

hyiger I am myself only interested in my 800mm scope pixel scale for minmo adjustability as my ultra widefield setups are not affected.

Kevin_A

MarcK you can go thru calculating your worst slope that gives youbthe best guiding arcsec/sec on the zwo website.
It is under the AM5 product page somewhere…. It looks like this image.

MarcK

Kevin_A
Thanks for your answer Kevin
My question was more about the camera and focal length. In terms of the theoretical maximum possible error before the stars are no longer round.

Kevin_A

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.

MarcK

Kevin_A
And the ratio of guiding camera / scope to main camera / scope does not have to be taken into account? I have 4.90 arcsec px main camera / scope and 6.44 arcsec px guiding camera / scope. This would mean that I would still have an acceptable guiding at over 2 rms?

Kevin_A

MarcK guide scale calculators also exist at that website. A less than 5 to 1 is a typical ratio for scope resolution to guide scope resolution . My 644 scope guides with a 240mm guide scope so it is basically 2.5-1 after calculating the individual resolutions. The smaller the guide scope resolution the better the guiding. I use a 240mm guide scope with my 2.9uM pixel guide camera and it works great. It will be way better than a 120mm guide scope with a guide camera with 3.75uM pixels as the resolution is better on the 240 combo. OAG’s work great sometimes because a 644mm scope using 2.9uM pixel resolution would be even smaller and have small tight star centroids to guide on at the increased focal length. That is kinda the typical jist of it. Guiding does not care about your imaging scope that much. It just cannot be a 120mm guide scope used on a 2000mm imaging rig. It needs to be about 3-1 to be in a sweetspot or lower. As your guide scope setup resolution gets bigger then your guiding accuracy gets lower due to centroid estimation error. It is nice to get it below 4 but the higher the focal length requires it to get even smaller. My 644mm imaging scope has a resolution of 1.2” and the max I want my guide scope is 3.6” as 3 to 1 is ideal… but 3” (2.5-1) is where Iam now and it is a bit better.

Kevin_A

MarcK based on your numbers you are either fairly wide field imaging or have fairly large pixels. Your numbers are well sampled for your setup as you would only need to guide at 2.5rms to get round stars anyways and your ratio is very small so you need not worry.

caradou

Hi team,
I bought the asiair plus knowing that this new beta is supporting sony Alpha A1 (ILCE-1) (see new features)
i'm running the latest beta, and i'm still not able to connect my camera. Any known issue.
I followed all the tutorials, this link as well https://www.yuque.com/zwopkb/asiair/lf7nd44fruq3vukh

It's saying that my camera is not in Blob mode when it is.
I have the same screen than this one

Thank you for your help this is my first time with ASIair.
I opened a bug ticket couple weeks ago, but i had no answer.

Luxo

My rig has a choice of three cameras - a main camera (3,000mm focal length), a guide camera, and a wider-field "finder" camera.

At present I have to manually select the "finder" camera as the MAIN camera to do the polar alignment, and then GOTO and plate-solve. I then manually select the real "main" camera to start imaging at 3000mm.

Would it be possible to add pull-down menus to choose a specific camera for the plate solve function, and and a pull-down menu to choose a camera for the polar alignment, instead of always using the main camera, and have those settings remembered for the evening ?

« Previous Page Next Page »