ASIAIR v2.4.1 has been released!: Page 7

ASIAIR v2.4.1 has been released!

R0k9pZfT

R0k9pZfT Started a thread on this. Hopefully someone will submit a bug report if it's widespread.

R0k9pZfT

Found another bug, albeit it's minor. After "successfully" updating the firmware on my AM3, the mount resets and returns with the same firmware. It has 1.7.3 before, 1.7.3 after. I know it's trying to update to 1.7.7. Yes, I've exited the ASIair software and rebooted everything. I've tried this three times. Bug submitted.

PMTeam@ZWO

R0k9pZfT We have received your log. Are you using BLE connection?

andrelucasmelo

Corsair

Is this a bug? I thought that every time I did the dithering, the movement of the mount caused some destabilization that made the error reach 8" and then come down to zero. I've already adjusted everything, balancing backlash, guiding adjustments and nothing has been solved.

Hn2z7ENs

Hn2z7ENs Follow up. I returned from my dark site trip and started using my other setup and found same issue with EAF not finding a suitable focus star. This happens about 50% of the time, and will work sometimes without me changing anything. I’m running two ASIAirs on two different scope, 700mm and 300mm with same camera (D5300). Both with broadband filter, so lots of good stars to pick from. The ASIAir also beeps for no apparent reason while in Plan mode and imaging.

R0k9pZfT

PMTeam@ZWO Yes, bluetooth. Didn't even cross my mind to try something else.

PMTeam@ZWO

R0k9pZfT Yes. In addition to waiting for stabilization after the guide dither, there are some other situations where the system needs to wait for the guide star to stabilize. However, this part of the setting is the system default and is not open.

R0k9pZfT And on that note, there are several threads here asking you to please PLEASE update the ASIair documentation. I think it's over seven years out of date, and it would also be nice if it were much more detailed. Such as with this explanation you provided. But it needs a whole lot of work and updates. A lot of work. And by update, I mean bring it all the way up to 2.4.1!

What document are you referring to?

R0k9pZfT

PMTeam@ZWO
Your website with all of your manuals. Other than your quick guide, they're sorely out of date.

https://www.zwoastro.com/guides-and-manuals/

On the first part of your response, the problem is the guide star doesn't stabilize before you start capturing. That is my complaint. It won't even start guiding until that time out expires. It's completely upside down and backwards. You should guide, let it stabilize, then start the image capture. Instead it either all does nothing or it all starts together after an event like focusing.

PMTeam@ZWO

KF7DS excepting drift caused by dithering (this bug has been around forever)

Hello. It is normal for the guiding data to drift due to dither. Whether the subsequent guiding can be pulled back to a lower error range normally？

KF7DS ending sequences early in multi sequence autorun sessions.

Did anything abnormal happen during the shooting? Can you share the shooting log? Thank you

Luxo

R0k9pZfT - Agreed the documentation is very out of date - I started to write a manual to help others in my astro club. https://www.icloud.com/iclouddrive/0daJSd0vS8tgAlgGgEVWZFttA#ASIAir_Missing_Manual_0.3

9kr69ubP

Does that suggest there is an issue with using a Bluetooth mount connection when guiding?

R0k9pZfT

9kr69ubP Not for me. I get excellent guiding using only Bluetooth. It may or may not be a problem being used to update the mount firmware, but guiding has been a non-issue for me.

retman

Luxo This is an excellent beginning to a "thankless task". I hope that ZWO pays attention to this post and understands that maybe they should PAY someone to produce a full manual AND keep it updated with EACH new software/firmware revision. I fully agree with other posts that ZWO must pay attention to fully testing revisions before they release them! (i do not agree that the AM3 and AM5 are "toys" as they, and other strain wave mounts, have brought a much needed improvement to guiding accuracy, when configured properly (hard to do without good documentation)!

Your efforts are much appreciated. i would happily pay a little more for a product that had proper documentation and support.

deans

Like others I have had my share of issues with the last mess of an update, but something to consider is the original design intent of the ASI Air. Was suppose to be a easy simple way to control basic imaging runs.

So many have put pressure on ZWO to add this or that, and make it work like this, etc. It is no longer a KISS system like it started out being.

Granted they are trying to keep everyone happy but maybe they should just limit some of the new stuff and just "Keep It Simple Stupid."

There are other options out there if you want full blown, do everything, systems.

Anyways just my 2 cents.

Dean

retman

deans agreed, some of the latest products (i'm talking to you CAA) have caused lots of issues. a stable platform would keep lots of folks from jumping ship.

Luxo

deans ".... but something to consider is the original design intent of the ASI Air. Was suppose to be a easy simple way to control basic imaging runs..."

And when it works, it is wonderful. for an application that is actually quite complicated - from end to end - as shown in my "Missing Manual".

Kevin_A

I think that asiair still has a few bugs to fix, the CAA should also be a priority to reconfigure its basic functions as well. But overall, my guiding has been the best it has ever been with my original 432s period length AM5 now running at 0.5s exposures on a 0.25X pulse guide rate with the latest mount and Asiair firmware. The last 6 sessions were all under 0.42rms with zero spikes and some 2 hour sessions running below 0.30rms. Before I was getting 0.7rms at best for the last 2 years. So, I cannot complain other than green previews after performing the A/F routine and my CAA sitting on a shelf due to not wanting to damage my camera due to cable twists. I however can only speak for myself and my 4 different Asiair setups. YMMV.

R0k9pZfT

I've now had multiple events where I tap on the Focuser icon on the left side in Preview, and the position says 0. I need to tap the EAF tab along the top and close it before the same Focuser icon on the left reads the current position. Only once did I proceed to the focus routine when it said 0, and at the time it returned an error (I don't remember what it said).

All of this only happens when first starting up the app after having shut everything down the previous night. If the ASIair is running and I close & restart the app. no problems with this. So--first run of the night after poweroff only.

Astrodinsk

Hello, please add a function to ASIAIR so that after the plan or autorun is executed, at the end of the session the camera can heat up itself and return to the ambient temperature smoothly automatically depending on the settings. I think this function will be useful to many along with such as automatic parking, etc.

R0k9pZfT

PMTeam@ZWO Once again, it's been a week since ZWO has posted to The forum. This isn't the only thread where people are asking questions that need a response from you. Why do you keep disappearing? If you're only one person, perhaps you shouldn't be posting as representing a team.

« Previous Page