ASIAIR v2.4.1 has been released!: Page 2

ASIAIR v2.4.1 has been released!

azskyguy

Starting to think the same thing. I've always liked the ZWO software... but to put out a release that can't do a meridian flip and can't plate solve, along with all the other issues, says something is wrong with their entire process of releasing software.

At the very least ZWO owes its customers an explanation, and assurances that whatever oversights caused this will never be repeated.

k6J471H7

Testing tonight and plate solving is worked fine, and so is guiding. I am now live stacking M12 for 1 hour which is doing its thing with no rejected subs, and I will switch targets when this session is complete. Maybe last night was a blip caused by the moon?

k6J471H7

k6J471H7 Finished. Good night of imaging. Plate solved, targets found, centred, focused, guided, and two live targets stacked for 1 hour each with 3 min subs. No problems to report.

andrelucasmelo

I've identified another bug where when I turn everything on, do a plante solve and try to move to the object, the HEQ5 goes to the opposite position, i.e. if I need to go north, the telescope goes south. With each new attempt, it ends up moving more and more in the wrong direction. I haven't managed to test the Meridian Flip yet, unfortunately.

BenBret-1

I hope that all of you guys who did find new bugs haven't forgotten to send your log to ZWO before closing your Asiair.

It's also a good idea to tag the PMTeam@zwo
when adding new or still existing issues.

andrelucasmelo

BenBret-1 bug reports are opened with submited logs.

Richard208

andrelucasmelo can you go over the steps to submit a log file after a night of shooting. Thanks

R0k9pZfT

For me, it's working as well as the last 2.4.1 beta, but with the same bugs in the guide settling section and now in object filtering. My object list is there, plate solve works, guiding works, histogram behaves, all sky PA works, EAF works, goto works. I'm using the android app. ZWO has been suspiciously quiet since the release.

Wheatgeneration

I’ve been using this release for several nights now. Where would I report the bugs I am seeing?

R0k9pZfT

In the last tab of the settings there's an option to submit a bug report. I'm going from memory but I'm pretty sure it's the very last tab with an "i" in a circle. You get so used to the menus that you're not always sure you're remembering correctly to tell someone else.

Richard208

PMTeam@ZWO July 13 2025. I updated to V2.4.1 four days ago. I created a sequence to shoot M13 for 180s at unity gain, for a run of 10 shots. I then confirmed and saw that the plan WAS confirmed. Switched to the operating window and hit the big white button to
start the plan... and message appeared ... No sequence has been added yet. In three years using
the Asiair, I have NEVER seen this before when trying to setup and run a plan. Is there something I am not selecting before this ??? It's driving me crazy. Can the previous version be re installed?
Thanks

PMTeam@ZWO

Richard208 Hello. Have you selected the target to shoot? Is this situation inevitable? Can you record a video and send it to luffy.liu@zwoptical.com? Thank you for your help.

Foobaria

This new version allows you to put same camera in for both Main/ Guide camera (on the main login screen only), but its doesn't function well in that mode.

cpl42

Following the upgrade, first to 2.4 (12.29) and now 2.4.1 (12.35) I am finding that a newly defined plan will not start and generates the message "No Sequence has been added yet". I have called up a previously saved plan, and this starts with the usual options dialog. Am I missing something here?

I have selected a target/targets. In each target I have set up a shooting scheme involving filter changes. I have used standard database targets, and also user-defined targets, but there is no difference in their behaviours. I'm sure this is all that I have done in the past, but I am still getting this message.

Any help would be appreciated.
Paul.

cpl42

cpl42
Fiddling around with the Plan problem tonight, I finally found the cause of this problem.

In previous versions, when I added a target to my plan, it was automatically selected/turned on/activated. All it needed was a shooting scheme, and it was ready to go. Since 2.4, adding a target has the target de-selected in the plan. One has specifically to select it/turn in on/activate it.

I don't know what the logic is behind this, but, surely, if one adds a target to a plan, it should be an active target, unless one specifically de-selects it. I'm sorry, but I find this to be nonsensical. It's cost me 2 nights of hair pulling!

andrelucasmelo

Another problem encountered.
I'm from the southern hemisphere and at times, the ASIAIR simply forgets this and reverses the direction of the Dec motor. If the object I'm commanding the Go-To to look at is to the north, it directs the telescope to the south, if it's to the south, it directs it to the north. He tries several times and as the movement is always going in reverse, he ends up doubling the error with each attempt. I tried to start a new plan with the telescope already directed to the side of the object and it still made mistake.

I've tried everything, I've put it in positive Park and it works perfectly. I've tried syncing several times and nothing happens. The coordinates are correct. This problem started with version 2.4.1. If I'd known it was going to get worse, I'd have kept doing the meridian flip manually.

I'm extremely annoyed with the product, as I've been building my observatory for over a year, and when it comes to using it I'm having more problems than pleasure in this incredible hobby.

R0k9pZfT

PMTeam@ZWO You haven't responded to anything here since announcing 2.4.1. Clearly people are still having problems. Why the silence?

andrelucasmelo

To enjoy the perfect cloudless night, I ended up finding an old Android cell phone here. I installed ASIAIR version 2.3.3, downgraded the firmware and tried again. Magically the problem disappeared.

qDl6bwKO

R0k9pZfT That’s really frustrating. It’s disappointing when repeated feedback goes without answer especially during beta when it should count most.

mariano

@PMTeam@ZWO You should open the software to the community.

Hubble's li'l Helper

I've been using the ASIAIR+ for about a year and never had an issue. Tonight I had a weird moment mostly with the PA, but noticed a few other issues, too.

This is the 1st time this has happened to me, although I'm not sure if it is related to updating the Celestron software on the hand controller and mount or the update on the ASIAIR+ firmware.
The ASIAIR completed the 1st plate solve for PA. During the 60° rotation, the mount rotation slowed down about halfway for a little bit then went back to normal speed. When it stopped at 60° it said failed.
This was continuously happing tonight.
After about 5 times, I cancelled the 60° rotation during PA, returned the scope to home position using the ASIAIR and tried the PA again.
This time it worked.
Never had this problem before.
Also, noticed the GoTo centring alignment takes more attempts now. Before it would only take one or two attempts, now it's taking 3 or 4, sometimes more.

A few times, the scope would take off in the completely wrong direction when heading to an object.

I updated the Celestron firmware (HC: 5.35.3179, MC: 6.51) a few days ago to use the dew controller through the handset, updated ASIAIR tonight before setting up the scope and also switched to OAG for the 1st time.
I was expecting guiding issues tonight while I set up the OAG. Surprisingly, guiding has been sweet, its all these other issues that have popped up, hahah.
Unfortunately, with updating both Celestron & ASIAIR firmware, I'm not sure which has caused the issues.

48DPcQF7

Hubble's li'l Helper
The PA Routine in Firmware 2.4.1 is not working with newest Celestron HC Controller Firmware HC:Gem 5.35.3179 or .3177. It has nothing to do with the newest Asiair Firmware 2.4.1 because the Problem was not fixed with 2.4.1. Only Celestron HC controller with older firmware releases are running without problems with Asiair. I checked it with 3 different CGX and CGX-L mounts and different HC controller firmware releases in combination with the latest Asiair Firmware.

« Previous Page Next Page »