ASIAIR v2.4.1 Public Beta Released!: Page 5

ASIAIR v2.4.1 Public Beta Released!

PMTeam@ZWO

Daan0523 Hello. You can send us the log to further check why waite for five minutes.

R0k9pZfT

PMTeam@ZWO Here it is. See your buttons interspersed with the tablet's at the bottom.

R0k9pZfT

I was testing the advanced guiding setting Guide Stability. I set it to 0.6" for 15s. Normally, 0.6 is super easy to achieve, but tonight the wispy clouds are rolling in and I wanted to see what happens. What seemed to happen is it tried for 15s to reach 0.6, then image capture began. It didn't reach 0.6 for more than a moment a few times, but never for 15s until about 20-30s after the image capture restarted. It is my understanding from the text displayed in the app's settings that it should maintain less than 0.6 for 15s. It wasn't close from what I could see. I sent logs.

I also included in this report the issue that I couldn't scroll up in the bug report window of the app to correct any text or errors in my bug report!

R0k9pZfT

R0k9pZfT I hope you noticed my comment on the guide stability settings. But since I submitted a bug report you should have the same information there.

R0k9pZfT

Is there a way to directly enter coordinates? The spinners you get when you tap on the RA/Dec in the preview window are super annoying to use. Just give me somewhere to type in the numbers. This probably isn't a beta issue, but just in case.

4H29wipq

For me 2.4.1 is working correctly so far. Did a 3 filter 5 hour session with meridian flip, autofocus and auto guiding in plan mode.

9kr69ubP

In the ASIAir app, under the mount tab, the mount time shows UTC time, the current time here is UTC+1 (Daylight Saving). I get that BUT under the mount tab of ASIMount (this a 5N), the mount time is shown as UTC+1. Seems a little odd.

MarshaWilcox

My guide calibration failed. I’m using the AM5N and the ASIAir Pro. It worked before the update. Here’s the error message:

I’m hoping this will be part of the patch for the 2.4 release.

Thanks!
Marsha Wilcox

PMTeam@ZWO

MarshaWilcox Hello. Maybe this is not a bug, but a parameter setting issue. What is the Calibration Step setting in the following figure?

magore

MarshaWilcox
I noticed 8 had to clear and redo guide calibration after the update.

9Ej7KtYy

[unknown] please make this soon thx

9Ej7KtYy

PMTeam@ZWO the canon r8 is still unsupported. Please make this soon. I can’t try the rest out until the camera is supported. Thanks

R0k9pZfT

I don't know that this is a problem unique to 2.4.1, but I'm finding that opening images from the image management menu seem randomly not to load.

PMTeam@ZWO

R0k9pZfT Hi. Can you provide a screenshot? Will it appear after waiting for a while? Maybe it is in the loading process

R0k9pZfT

PMTeam@ZWO Since it's random, it's difficult to reproduce at will. When it does occur, it doesn't matter how long I wait. The progress bar across the top has completed and it just sits there and says loading. But then if I go to another folder I can load images fine. I come back later and everything works as it should. I've also noticed this on 2.3.3. Next time it happens I will get a screenshot.

R0k9pZfT

I still find the little white arrows on the new object list far far more confusing than the old layout. I finally see what you're trying to communicate, but it is not well done. I think "icky" would be the appropriate word!

4H29wipq

Small UI bug: When making flats (for example) the downloading/processing + speed label on the bottom right is not fixed but flickers a bit left and right.

Very minor issue.

RomainD

@PMTeam@ZWO Hello, since the latest update I experience another issue on my AsiairPro with meridian flip but it does not seems to be the issue fixed in this version. The merdian flip occur at the right time but the mount disconnect and then it cannot go further and fail to solve. I can reconnect the mount by clicking on the toggle button and after checking I do not have cable snag. I have been using the same telescope / mount configuration for 2 years without any issue. It started with the latest update (2.4) and i hoped it was fixed with the download of this beta version but it was not.
I imaged for 8 nights in a row and it happen on 4 of them, making me loose each time 1 hour of shooting.*
I also opened a bug report.

2025/07/02 03:21:06 Stop Tracking 2025/07/02 03:21:06 [Meridian Flip|Begin] Wait 9min6s to Meridian Flip 2025/07/02 03:30:11 Meridian Flip 1# Start 2025/07/02 03:30:11 [AutoCenter|Begin] Auto-Center 1# 2025/07/02 03:30:11 Mount slews to target position: RA:20h25m36s DEC:+42°34'2" 2025/07/02 03:30:27 [AutoCenter|End] Mount slews failed 2025/07/02 03:30:29 [AutoCenter|Begin] Auto-Center 2# 2025/07/02 03:30:29 Mount slews to target position: RA:20h25m36s DEC:+42°34'2" 2025/07/02 03:31:22 [AutoCenter|End] Mount slews failed 2025/07/02 03:31:24 [AutoCenter|Begin] Auto-Center 3# 2025/07/02 03:31:24 Mount slews to target position: RA:20h25m36s DEC:+42°34'2" 2025/07/02 03:31:45 [AutoCenter|End] Mount slews failed 2025/07/02 03:31:47 [AutoCenter|Begin] Auto-Center 4# 2025/07/02 03:31:47 Mount slews to target position: RA:20h25m36s DEC:+42°34'2" <-- It slew for 103 iteration and fail then stop at 04:45 --> 2025/07/02 04:45:01 [AutoCenter|End] Mount slews failed

PMTeam@ZWO

RomainD Hello. Our developers have responded to you. You can check the follow-up on the APP. We suspect that the communication failure is caused by the cable problem. We recommend that you try another cable.

magore

I submitted a bug report on this.
Allsky PA is still broken for me on 2.41 beta. There is also an issue concerning the UTC offsets reported on the asiair app and mount others have reported

I submitted logs

You can look at these posts post

https://bbs.zwoastro.com/d/23618-apology-and-update-on-version-24-issues-stable-version-233-available/70

And
https://bbs.zwoastro.com/d/23618-apology-and-update-on-version-24-issues-stable-version-233-available/67

And
https://bbs.zwoastro.com/d/23618-apology-and-update-on-version-24-issues-stable-version-233-available/51

PMTeam@ZWO

magore Hello. Our developers are checking the error of the All sky polar align errors.
We also recommend that you reset the mount to zero after roughly aligning the polar axis, and then perform PA again. Error accumulation is due to tracking being turned on, polar axis calibration is inaccurate, and there is deviation

PMTeam@ZWO

magore Regarding the time display issue, it may be because your area is currently in the daylight saving time phase, so the system is UTC-4, and AIR will automatically adjust the time difference caused by daylight saving time, so the final display is UTC-5.

« Previous Page