ASIAIR v2.4.1 Public Beta Released!: Page 7

ASIAIR v2.4.1 Public Beta Released!

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.

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.

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.

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 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.

hyiger

An annoying new feature that I don't like. I space is being inserted in the object name when creating the file name for the FITS. For example: Light_NGC 6888_30.0s_Bin1_2600MM_R_gain100_20250704-231426_-9.8C_0002.fit this makes it super annoying when working with scripts. I can mass rename the files but it's just an extra step I don't want to deal with.

paramsachhotmail-com

PMTeam@ZWO Can you provide update on support for canon R5 mk2? Thanks

PMTeam@ZWO

paramsachhotmail-com

9Ej7KtYy Hello. Your requirements have been recorded in the requirements pool and we will implement them in subsequent versions. Thank you for your patience.

rbrasi27

rbrasi27 UPDATE - I have re-reviewed my flat subs (using ASIFitsView 1.15.1) from the two capture nights noted in my earlier post (2 days ago) and all the flat subs appear as they should with exposures are consistent with the settings I set in the rolled-back ASIAir Plus version. I do not know why these subs were not showing properly 2 days ago... but my reported problem symptom is no longer evident. I expect the problem may have been with the operator... ;-)... thank you for listening.

Foobaria

azskyguy Thanks for mentioning this, thought I was going crazy with these plate solving errors!

v9043ouc

I am only making this unrelated reference for new users of the ASI2600MM-Air, and as possibly they're reading this thread or visiting this forum for the first time. Feeling rather stupid for posting this but not wanting anyone else to make the same mistake, when powering on the ZWO ASI2600MM-Air initially I was unable to take a picture and see the result on my phone - I was unable to see the target in real time. I had no idea why. After many hours of random toying, for whatever the reason, I realized I had to go into Video mode first to "wake-up" the device. Then after entering video mode, the other modes functioned as normal. I have no idea why this is a necessary sequence, because on the surface, all of the other features of the camera function correctly, so as a result I was not expecting this odd but apparent necessary sequence. So hopefully this quick mention prevents other new users from unnecessary becoming frustrated. Happy Viewing!

9Ej7KtYy

Canon r8?

R0k9pZfT

In addition to my previous issue with the guide settling settings that I'm trying to get ZWO to acknowledge, I have now noticed that during the settle time, no guiding is happening. The ASIair is sitting there waiting for the mount to stabilize before it starts guiding?! After that timer expires, guiding resumes AND imaging resumes. It seems like what should be happening is that guiding resumes after focusing while the system waits for the corrections to meet parameters before resuming imaging. This is not happening. It sits there, does nothing, the timer expires, then everything fires off together, even though guiding has not yet settled in. I've now filed two bug reports on this.

« Previous Page Next Page »