ASIAIR v2.4.1 Public Beta Released!: Page 7

ASIAIR v2.4.1 Public Beta Released!

R0k9pZfT

2.4.1 was in the app store? It's still in beta. Is the version different on Apple?

PMTeam@ZWO

k6J471H7 Histogram is not presenting properly. This is not a show stopper but worked fine in 2.3.3.

Hello, could you provide a screenshot or FITS file so we can compare the results? Please send to email luffy.liu@zwoptical.com

k6J471H7 The EAA randomly reset itself to 0 which did not allow me to run autofocus when I was getting ready start my Live stacking capture of the Eagle Nebula. I fixed this by toggling the EAA off and on in the software.

EAF or CAA? Was ASIAIR turned off after the problem occurred? Can you send us the log? Thank you.

magore

PMTeam@ZWO
I also have have noticed a similar issue with the histogram curve that is displayed while running a plan. The displayed image is ok but the histogram shape for it is wrong. I normally have auto and zoom selected. The curve is wrong with and abrupt rise followed by a flat ramp that is slowly declining towards higher values.
I can fix it by unchecking and rechecking auto to a normal looking histogram.

Unfortunately I am running 5 hour plan run and I have 3 hours to g.
If it's still dark I will see if I can reproduce it.

magore

PMTeam@ZWO

I am seeing a histogram display issue while running a plan. All I did to fix it was uncheck and recheck auto and zoom

Before

After

Sonixx

PMTeam@ZWO

Finally I had the opportunity to test the 2.4.1. and can report that the Meridian Flip issue has been solved. Thanks for solving this!

However I observed the following things when using my ne ASI585MC Air and AM5N:

-the guiding values were mostly below 0.3“. As I was imaging with a dual narrowband filter I used 2x2 binning on the guide cam. Normal guiding values are around 0.6“. I assume that binning is not taken into account when calculating the guiding error.

-mount voltage display. Mount voltage was constantly shown as 12v while the ASIAIR voltage showed roughly 12.8V. As I was running from a battery the value in the Asiair declined from 13V to 12.8v but mount showed 12v all the time. This was different with the previous firmware.

-a small issue, in the mount info tab focuser is shown. See screenshot.

Logs are uploaded. BT20250704803200A

Best regards,

Stephan

k6J471H7

PMTeam@ZWO Hello, and thanks for getting back to me. I’ve sent you a screenshot of the histogram via email. This is a bug.

I also meant the EAF but did not capture the error log at the time.

I had the scope out last night and the focus was fine. Tracking does not work as well under 2.4.x which was frustrating but because I was imaging I could not triage.

R0k9pZfT

R0k9pZfT I'll ask again ZWO --can you explain this behavior after I completed my all sky PA? Also, did you see my issue with the guide stability settings?

PMTeam@ZWO

R0k9pZfT Hello, this is because there is room for optimization of the full sky polar axis algorithm. We will reduce the change of this error by optimizing the algorithm, which is still under research. We recommend that you use two points to align the polar axis first.

PMTeam@ZWO

magore It has been fixed. You can try the latest 2.4.1 package in the link, thank you.
iOS > TestFlight https://testflight.apple.com/join/6uEyoSl3
Android > https://pgyer.com/air_beta_android

PMTeam@ZWO

Sonixx Thank you for your feedback. We are analyzing the logs.

PMTeam@ZWO

Sonixx -the guiding values were mostly below 0.3“. As I was imaging with a dual narrowband filter I used 2x2 binning on the guide cam. Normal guiding values are around 0.6“. I assume that binning is not taken into account when calculating the guiding error.

Hello. Switching Bin should have no logical impact on the guiding error.

Sonixx

PMTeam@ZWO

It depends, if the guiding error is calculated on 4my pixels but through binning these are in fact 8my. This would effectively halve the displayed error if not taken into account. I never had the AM5N running consistently at 0.3“ RMS (at least when I looked). It is more like 0.6“ in previous firmware. I really think there is something not right. And having half the error at double the pixel size seems to hint in this direction.

PMTeam@ZWO

9kr69ubP Hello. ASIMount has not made the correction for daylight saving time. It has been synchronized to the project members and will be fixed as soon as possible.

R0k9pZfT

PMTeam@ZWO I have no problem with the all sky PA. My question is about the wildly changing values after it's complete if you reread my original post. Also why does the alignment seem to improve when I do nothing and just let it run. Again, please see the original post I referenced.

R0k9pZfT

R0k9pZfT ZWO, I'll ask you a third or maybe fourth time. Did you see this post?

PMTeam@ZWO

R0k9pZfT Hello. Your problem is caused by the same reason as the one reported by Magore. It is because there is room for optimization in the full sky polar axis algorithm. We are studying how to avoid this error change by optimizing the algorithm. In the meantime, we recommend using two-point polar axis first. Thank you for your feedback.

R0k9pZfT

I see you released a new build of the beta. Please be sure to notify us in a separate post here that you have released a new build. I feel like communication is slowly sliding back to the way it was before. You only mentioned it as an aside in a response to somebody about an issue.

9kr69ubP

R0k9pZfT and preferably an indication of what has changed.

Sonixx

I observed another small issue, that was actually existing also on previous firmwares.

When Bias frames are shot in Autorun with a filter named dark (I inserted an opaque 3d print „Filter“ in the filter wheel) ASIAIR responds that bias cannot be shot with a dark filter. The Autorun still runs as expected, but the message should be removed.

Best regards,

Stephan

PMTeam@ZWO

Sonixx Thanks for your feedback, I will pay attention to this issue.

R0k9pZfT

PMTeam@ZWO So I guess you're not going to answer the other question I posed at least four times now about an advanced guidance settings problem? I'm only responding to this post because you seem to be glossing over every single other post where I've asked about the issue.

« Previous Page Next Page »