ASIAIR V3.0 Public Beta Released！: Page 5

ASIAIR V3.0 Public Beta Released！

azskyguy

I have a 2600 MC Air and haven't had any issues with finding guide stars using either an askar D1 or D2 filter. I'm doing fine here in Southern Arizona.

Larry.Cable

azskyguy just as a counterpoint, using an Optolong L-Synergy Sii/Oiii Db filter I found over the last
couple of evenings that the guide cam was challenged even with longer exposures and higher gain...

overall I dont think the Duo/Air cameras are ideal for imaging with DB/NB filters that do not pass Ha|b

presumably though it would be possible to override the internal guide camera with another and achieve some of
the convenience of the MC Air...

Jump

It would be great to be able to have the same level of control as nina or even be able to just use a motorised flat panel in a autorun or plan properly, without having to do a workaround like using the deepspacedad flat panel only with the "asiair cable" they have

autorun control to be able to tell when to open or close the panel in a plan, setting for closing flat panel at the end of a session just like how you can turn off the asiair/go home at the end etc

Larry.Cable

Jump +1!!!

Luxo

This is why IMHO ASIair is a long way from being ready for real remote operation.

It’s ok sitting in the car 3m from your scope, or in your lounge at home with the scope outside - but not for a real remote observatory.

The entire range of operational scenarios have to be considered to identify all the user needs. It’s also clear ASIair doesn’t have enough ports to handle all the dwvices involved.

Luxo

Many thanks to Tianfeng - setting Aeroplane Mode = ON solved the issue I had on the iPhone with iOS 27beta.

PMTeam@ZWO

Luxo Thank you too, Luxo.

chrisrose98

Larry.Cable A new updated was released to test flight and it resolved the issue with my USB stick. It is recognized again.

Larry.Cable

updated my ipad to b16 and that updated the 2600MCAir also 44.84? - I now notice that plate solving for both
P.A and auto-center times fluctuate, they are either around the norm I usually observe of 9-12s but now I am
seeing PS take 25s or more!

anyone else seeing PS times spike?

PMTeam@ZWO

chrisrose98 Hi, We’ve fixed this issue. Please use the download link in this post to re-download the latest version and try again.
If you still experience the issue, please let me know by replying here. Thank you for your continued support and feedback!

PMTeam@ZWO

minimoto71 Hi, Compared with previous versions, we haven’t made any changes to the Plate Solve feature in either v2.6 or v3.0.

If you notice that plate solving is taking significantly longer than expected, please submit a Bug Report through the app while the issue is occurring. The logs collected at that time will help us investigate the cause.

Regarding the issue where the device could not be powered off, we’ve already fixed it. Please use the download link in this post to download the latest version and try again.

If you still encounter the issue after updating, please let me know. Thank you very much for your feedback and support!

minimoto71

PMTeam@ZWO Hi again. Seems that the latest beta ( build 16 ) is solving better than previous. I ignore if anything have been "touch" or not, but in the previous beta iterations, pointing to the same location with good seeing or trying to solve previous captured images took a lot of time or just fail. Now it seems to work properly. If it was with only one ASIAir and one system, I can think about something out of place in my configuration. But with 2 different setups I don't think that was casual. But thankfully now it works as expected.

I have seen that the issue with the camera is gone too in the latest iteration, so thank you.

Now there is a new issue I have found with EQMod that wasn't present previously. When I hit the Go Home button, the ASIAir interface stops responding for a while. If I try to check the Mount or any other device's parameters, nothing is shown ( appears completely empty ). After a couple of minutes or more, it restores by itself but this never happened before in other official releases or betas. If it happens again, I will send you the log if possible ( or at least a screen capture ).

Thank you for your support

PMTeam@ZWO

SFokOovu Hi, We’ve fixed the issue that prevented the device from powering off properly. Please use the download link in this post to download the latest version and try again.
Thank you for your feedback!

SFokOovu

PMTeam@ZWO
Thank you very much. Test with Version: 3.0.0 (16) was partly negative:
After Plan Mode Asiair Software in the ASI2600MC Air shuts down and Fan is now disabled (fixed) but the Power Light of the Camera stays on and also the DC ports still provide voltage/power!

PMTeam@ZWO

Larry.Cable Hi, We’ve fixed the issue that prevented the device from powering off properly. Please use the download link in this post to download the latest version and try again.
Thank you for your feedback!

PMTeam@ZWO

UTGb2uyO Hi, Canon R8 is not supported in the current Beta version. We expect to start public Beta testing for R8 support in the next release.
If you’re interested, could you contact me by email? Once the test build is available, we’d be happy to invite you to help us test it.
My email address is: tianfeng.chen@zwoastro.com
Thank you for your support!

PMTeam@ZWO

Plus Sorry, the Sony A1M2 is not supported at the moment. I’ll share your request with our internal team for evaluation. Thank you for your suggestion and support!

PMTeam@ZWO

Gatsu87 Hi, Have you used a previous version of ASIAIR where this issue did not occur or where the performance was satisfactory?
If so, could you please try the following?

Downgrade to the version that worked well for you, reproduce the issue you described, and submit a Bug Report through the app.
Then upgrade back to the current version, reproduce the same issue again, and submit another Bug Report.
By comparing the logs from the two versions, we’ll have a much better chance of identifying the root cause of the problem.

Also, could you let us know whether you’re using an iPhone (iOS) or an Android phone? If you have any questions or need any assistance during the downgrade process, please feel free to contact me at tianfeng.chen@zwoastro.com.

One more important note: Before downgrading from ASIAIR v3.0 to an earlier version, please reset the firmware in the v3.0 app first. After the firmware has been reset, you can then downgrade to the previous version.

Gatsu87

PMTeam@ZWO I have tried both ASIAIR 3.0 beta versions, and as other users have already reported, the incorrect contrast issue in the guiding screen with the ASI2600MC Air/Duo is still present.

The other issue is also still present: when guiding through 6 nm and 3 nm narrowband filters, I now need to use Bin 2 and 3-second exposures to achieve stable guiding.

If I remember correctly, with ASIAIR version 2.3.3, guiding worked very well through narrowband filters using 2-second exposures, gain 380, and Bin 1.

Regarding the downgrade procedure, I performed a firmware reset to try to go back to the original ASIAIR 3.0 beta version, because guiding performance seemed slightly better with that version compared to the latest beta. However, when I launch the ASIAIR app after resetting the firmware, it immediately asks me to update the firmware, and I have no option to refuse or skip the update. Could you please explain how I can remain on or return to an older firmware version so that I can properly perform the comparison and submit the two Bug Reports you requested?

I am using Android.

In any case, I am also already in contact with your support team via email regarding these issues.

@Eric , are you also still experiencing guiding problems when using narrowband filters?

FERNANDEZ

Hello ZWO Support Team,

I would like to suggest an improvement for the Sky Atlas feature.

It would be very useful to have a more complete sky atlas including not only bright nebulae, galaxies, and star clusters, but also dark nebulae and catalog objects such as LDN (Lynds Dark Nebulae), vdB (van den Bergh nebulae), and other faint deep-sky objects.

For astrophotography, especially when preparing a precise framing, it would be extremely helpful to have these objects clearly visible on the atlas, with their coordinates displayed directly. This would allow users to select an object, adjust the framing accurately, and send the exact coordinates directly to the GoTo system.

A feature showing the field of view of the telescope/camera setup, combined with object outlines and coordinates, would make the planning and framing process much easier and more precise.

Thank you for considering this suggestion. I believe this improvement would be very valuable for many astrophotographers using ZWO equipment.

Best regards

Luxo

This thread is about beta testing of 3.0.0 not feature requests. BTW what you suggest is a considerable undertaking, and Charles Bracken (TAIC) is compiling something along these lines.

This was why I suggested a while back that the ability to load a custom catalog from a table was badly needed, then users can configure a list of whatever they like using (say) MS Excel and load that.

Most catalogs have piles of objects of little or no interest and I’d prefer to cull those out rather than have to scroll through the junk in ASIAir on the night

FERNANDEZ

Luxo
Thanks for the clarification. I understand that this thread is focused on the 3.0.0 beta rather than feature requests.

I completely agree that implementing a full custom catalog system would be a significant undertaking, especially if a similar project is already being developed by Charles Bracken (TAIC).

That said, I still think the ability to import a simple user-defined catalog from a table (CSV, Excel, etc.) would be an extremely valuable addition. It would allow each user to create a personalized observing list and avoid scrolling through hundreds of objects that are irrelevant to their interests. For many of us, spending a few minutes organizing targets beforehand is far preferable to searching through a cluttered catalog in the field at night.

Hopefully, this kind of flexibility can be considered in a future release.

Luxo

Larry.Cable
Experienced the guide camera issue tonight (ASI2600MC DUO) and will try to pinpoint what the issue is. Something very odd is going on - reducing the gain the background was much brighter and the stars invisible, yet increasing the gain produced white stars on black background.

As this was an outreach night I didn’t have much time to explore it but will do on the weekend.

Moontanner

Luxo

Although not specific to this Beta, the Duo/Air guiding contrast issue is very real. It doesn't care if I'm running narrowband, or a simple luminance filter.

The image above is an old one as an example. At 250 gain that screen should be covered in stars.
I have loads of others at different gains and various other settings. All of them seem to have some sort of stretch applied that messes up the contrast compared to my other stand alone guide camera.

It's rare that I can't get the rig guiding after playing around with the settings, so I just get on with my life and ignore the fact that the guiding screen is a turd compared to using my 290 in an OAG.

DaveC

I have an older iPad that can’t load testflight (the ios can't be upgraded to 16.0). Is there another way to get the beta?

Larry.Cable

DaveC

if you have an ARM silicon Mac you can install and run it there ... or an android phone/tablet

PMTeam@ZWO

DaveC Hi, Could you let us know which version of iPadOS you’re using?

« Previous Page Next Page »