ASIAIR v2.4.1 Public Beta Released!: Page 3

ASIAIR v2.4.1 Public Beta Released!

PMTeam@ZWO

azskyguy This is exactly what we did in v2.4.1, fixing most of the issues you reported. We sincerely invite you to join the test, because we are very concerned about the BUG you reported, so we need your help to submit log analysis and tell you why it happened. Is it a device problem or a software bug, we need to solve it.

PMTeam@ZWO

9Ej7KtYy You can download the test version through the link. We will test it for a longer period of time to avoid missing bugs by releasing it too quickly.

9Ej7KtYy

PMTeam@ZWO I just tried the version and it does not support the canon r8. Thanks

PMTeam@ZWO

enzinho25 Hello. Could you please give a more detailed description of the problem so that we can better understand what you are encountering?

enzinho25

PMTeam@ZWO i attach the screenshot

PMTeam@ZWO

enzinho25 Hello. What is your ASIAIR model? Some models do not support this function.

enzinho25

R0k9pZfT i attach the file

enzinho25

PMTeam@ZWO this is asiair pro

R0k9pZfT

I'm running in Live mode with the ASIair set to autofocus every 30 minutes or 1 degree C change. It just refocused, and it appeared to me to restart the image capture even before guiding had settled in again. I saw it say something like "settling" on the guide window, but image capture was already started and the guiding graph clearly showed it needed to make some minor tweaks. I suggest maybe waiting to resume capture for 15-20s while guiding settles.

9kr69ubP

R0k9pZfT there are a bunch of settings under guider advanced settings to control the guide settle offset and time.

R0k9pZfT

Took a new sequence of 20 Bias frames. This is just cosmetic, but it said it took 19m 46s to take the 20 bias frames. Clearly that's not true!

R0k9pZfT

Why does a series of 20 bias frames cause the temp on a 2600mc-duo to go up by 0.5-0.6C, but on a 2-3m dark the temp is virtually unwavering? This is with temp set at either 0 or -10.

9kr69ubP

R0k9pZfT the readout electronics generate heat and as a rapid burst of Bias frames are constantly being read this generates a lot more heat than a Dark. If the cooler is already working hard, it can struggle to maintain the set point temperature.

James203

R0k9pZfT

I see this too, had opened a bug report for it. They said it's the rapid image capture that causes it, but I don't have the issue on my 2600MC Duo - only on the Air. Anyway, if you set a 2s interval, the temp mostly stays constant.

R0k9pZfT

9kr69ubP Thanks! I didn't even think to check there.

R0k9pZfT

9kr69ubP At 0 it said the cooler was at about 27%.

PMTeam@ZWO

9Ej7KtYy Hello. I would like to ask if everything went smoothly when you used v2.4.1, and whether you encountered any problems during the process.

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

azskyguy

I gave 2.4.1 a try on my ASI6200MC and had no obvious issues. I had turned off meridian flip so could not test that. I felt plate solves were a little slower than usual, and would like to lengthen the exposures for solves.. maybe there is a setting for that I missed.. am using an NB filter.. in older versions of the software did not see plate solve issues. I used the standard solve setting, nit the new one which failed in last firmware. If I get bolder tonight I'll turn the auto flip on, but am not imaging near the meridian tonight. Just want to confirm random flips are not happening. So I got through the evening without obvious bugs.

PMTeam@ZWO

azskyguy Hello. v2.4.1 has fixed the problem of incorrect meridian flip. Looking forward to your feedback

PMTeam@ZWO

enzinho25 Yes. This feature is not supported on this device

christopher.henderson

Howdy!

I went to troubleshoot my logs this morning and I was pleasantly surprised to see a patch being offered for "meridian flip" issues. I've installed your beta and I'll take it for a ride tonight.

For clarity's sake, here is the precise issue that has been manifesting for me the past several nights. Let's first observe the logs for a successful night of imaging M16 in hydrogen.

2025/06/25 23:36:04 [AutoFocus|End] Auto focus succeeded
2025/06/25 23:36:05 [Guide] ReSelect Guide star
2025/06/25 23:36:06 [Guide] Start Guiding
2025/06/25 23:36:08 [Guide] Guide Settle
2025/06/25 23:36:10 [Guide] Settle Done

// ...successful exposures...

2025/06/26 00:33:32 Stop Tracking
2025/06/26 00:33:33 [Meridian Flip|Begin] Wait 12min48s to Meridian Flip
2025/06/26 00:46:21 Meridian Flip 1# Start

I began imaging at 11:30pm and the merdian flip was executed at 12:30am.

Now let us observe a failed night attempting to capture LRGB stars in M16.

2025/06/28 23:33:14 [AutoFocus|End] Auto focus succeeded
2025/06/28 23:33:17 [Guide] ReSelect Guide star
2025/06/28 23:33:18 [Guide] Start Guiding
2025/06/28 23:33:19 [Guide] Guide Settle
2025/06/28 23:33:21 [Guide] Settle Done

// ...successful exposures...

2025/06/28 23:35:40 Stop Tracking
2025/06/28 23:35:40 [Meridian Flip|Begin] Wait 0s to Meridian Flip
2025/06/28 23:35:40 Meridian Flip 1# Start

// It then enters into a loop of attempting recentering until it bails out on the plan

2025/06/28 23:38:10 [AutoCenter|Begin] Auto-Center 1#
2025/06/28 23:38:10 Mount slews to target position: RA:18h20m11s DEC:-13°47'11"
2025/06/28 23:38:11 Exposure 5.0s
2025/06/28 23:38:17 Plate Solve
2025/06/28 23:38:26 Solve succeeded: RA:18h20m11s DEC:-13°47'16" Angle = 174.629, Star number = 4312
2025/06/28 23:38:26 Pierside is wrong
2025/06/28 23:38:26 [AutoCenter|End] The target is centered`

It began the meridian flip an hour before it was suppose to. I can also confirm this via Stellarium.

I presume that what "Pierside is wrong" is saying here is...

Hey. I did the meridifian flip and I'm dead center on the target, but I landed in the same spot where I started. There's no way that's right.

I will add some gratitude to this thread.

You folks are taking a lot of heat for this buggy release. Because it is a buggy release. However, I am a software engineer myself and I can say that I have worked with too many developers that would have let the above scenario spiral out of control and destroy thousands of dollars worth of equipment. The fact that it deteced this bizarre fault and behaved appropriately is not lost on me.

You folks likely won't remember this release fondly. Although, I am quite appreciative of the defensive programming that your developers practiced in order to keep our equipment safe while we sleep.

9kr69ubP

christopher.henderson the almost exactly one hour error is suspicious. Daylight saving?

PMTeam@ZWO

christopher.henderson I went to troubleshoot my logs this morning and I was pleasantly surprised to see a patch being offered for "meridian flip" issues. I've installed your beta and I'll take it for a ride tonight.

Thank you. Looking forward to your feedback.

9kr69ubP

R0k9pZfT the Peltier cooler is quite slow to adjust to an increase in thermal load so 20 bias frames may not be long enough. Too hot here at the moment to confirm but I’ll give it a try in a few days time.

christopher.henderson

9kr69ubP

Thank you for thought. Unfortunately, daylight's savings was back in March.

I ran the beta last night and the meridian flip executed at the correct time and the plan completed successfully. I'll report to this thread if I do end up observing the issue again.

« Previous Page Next Page »