ASIAIR v2.1 has been released
I myself am using it for EAA. Definitely Startools or any professional imaging program will do a better job than the application.
Another thing is some stupid rules on some EAA forums that prohibit the further processing of photos and force you to only use the capture and stack application.
Can someone please show me where I can backdate my update from 2.1-10.74 to a previous version like I had last week as this little box no longer talks to my heq5 mount? I wish they would give me the option to not update ever when it works I am happy but now it's back to being a paperweight till I get help.
Malcome I wish they would give me the option to not update ever when it works I am happy but now it's back to being a paperweight till I get help.
If you use iOS/iPadOS, have you been using iMazing to back up the older versions of the ASIAIR app? If not, there is no way to go back to older versions.
If you are using Android, look inside your Files folder to look for older APK files. You can then install an older ASIAIR app from the older APK. But you also need to change the firmware to somethong at least as old as the APK install. Thare have neen numerous postings in this forum on how to go back to older firmware.
Chen
I have lot of issues since last firmware update. The calibration data is lost after each session (and yes auto restore calibration is on, as it has always been). The first GOTO command after PA sends the scope on the wrong side of the meridian (yes, DST is off on the mount), so I have to twist its arm to get the scope on the correct side. Last but not least, meridian flip fails everytime. The meridian flip routine starts exactly when it should, but the motors move just for one second and stop. Nothing happens after that, and tripod crash occurs if I don't supersede the ASIAIR and do a goto manually on the target. I highly doubt that all these problems are operator error since I've used my asiair for three years in a row without any problem, and I have changed neither my setup (AP900 mount) nor my settings.
- Edited
dan_paris The meridian flip routine starts exactly when it should, but the motors move just for one second and stop.
This sounds amost like it is trying to perform a GOTO (that is how the ASIAIR asks a mount to perform a Meridian Flip) when the mount thinks the target is still on the correct side of the pier. I.e., the ASIAIR thinks the target has already transited the Meridian, but the mount thinks the target is still on the original side of the meridian.
To check, you can do this indoors, and in the daytime even, try to set up an auto run session.
Use SkySafari, or one of many iOS apps, to find the current Local Sidereal Time (no, the ASIAIR is too crippled to display it; and it may be wrong anyway).
Home the mount. Do not ever manually slew across the Meridian after this. Only use GOTO.
Add 1 hour to the Local Sidereal Time and use that as the target's RA. For the target declination, use your approximate Latitude. This will place the target one hour east of the Meridian, and close to Zenith. The declination is not important, but if you make it your Latitude, the OTA will be pointing straight up as a further sanity check.
Ask ASIAIR to GOTO to this target.
Now go to AutoRun and set up a fake session. Turn on Auto Meridian Flip. There is no need to turn on guiding or anything else.
Start AutoRun, and you should see autorun report something like "Meridian flip in x minutes" at the bottom of the Preview window.
If you had set the RA to the LST plus 1 hour, AutoRun should report 60 minutes for the value of x.
If it is off by more than one or two minutes, the ASIAIR and the mount are not in sync. It could be either because of time, UTC offset or Longitude.
Chen
Thanks a lot Chen. It seems indeed that there's a time discrepancy between the mount and the ASIAIR. I will try what you suggest during the week.
What I noticed is the following. If I start the mount with the keypad but without the ASIAIR, the time is correct, the time zone (1 hour EAST of Greenwich) is correct and the longitude is correct. As soon as I connect and sync the ASIAIR to the mount, the mount "believes" that my time zone is 1 hour WEST of Greenwich. This is probably the root of both meridian flip and goto problems. I have no idea how to fix this.
Also it does not explain the third problem: why guiding calibration is lost after each session?
best regards,
Dan
Seems there are new bugs with ASIAir App 2.1.1 and ASIAir Plus on iOS 16. FWIW, the Android version of the app is much more stable and I don't notice these bugs.
- Connection occasionally dropping over Wi-Fi even when standing 2m away
- App freezes on the startup screen when reconnecting to device after closing and restarting the app. This doesn't go away until I reboot my iPhone.
- After a while, I was unable to switch between different modes like Preview and Autorun. For example, stuck on Autorun. Have to kill and restart app.
- Preview mode sometimes stops working when I'm pressing the exposure button and nothing happens. Have to restart the app.
- Still an issue on iOS where cellular data needs to be turned off in order to connect to device when not in station mode. This has been an issue from the very beginning.
- Edited
Requests for next version of ASIAir app:
- Filter offsets please!!!! Auto-refocus on filter changes eats up time.
- Please add support for PHD2 Guiding Assistant.
- Under mount information please include LST. I'm worried that my Air and mount don't have the correct time and my rig goes smashing into my pier instead of doing a flip.
- On iOS fix the issue where I have to turn off cellular data in order to connect over the ASIAir Wi-Fi
giuseppe2308
Hello:
Have you solved the problem because I have the same issue with my EQ6 mount. I talked to sky watcher and the tech there suggested I use an EQ Mod cable between the air and the mount's hand controller port. I ordered one from Amazon and will see if that solves the problem. Before the FW update, I was completing PA in under five minutes. Now it takes up to 15 minutes. The cable I got from AMZ works with my mount and your AZEQ6. It's about $19 and worth a try.
I see where the A6100 is supported but mine simply will not connect. I've been through every setting 10 times and the only result I ever get from the A6100 is "Connecting".
ASIAIR Plus is running 2.1.1(10.74)
- Edited
@Support@ZWO and @PMTeam@ZWO - Running the latest 2.1 update for IOS, and I'm seeing a recurrence of a bug I reported (and which was fixed) in the 2.0 beta. Anytime I set up a new plan or try to modify an existing plan, the exposure time (I tried lights only) is locked to 300s. That field no longer has a pick list option, and is only text entry. However, if I try to edit the text to a valid whole number, no matter what value I enter, it throws an error stating “Exposure should be between 0.000032s-0s”. I've tried the fix from the 2.0 beta of rebooting, full power off/on (with power plug removal while off), and I cannot get it to work. One random session, I did see the pick list again on one of the plans I had created before, but there was no set reason why it worked that one time (and has not since).
Gain in Autorun! Thanks a million! Very happy today
Anything on this ZWO …?
It's been awhile since I've checked/tried. Does a Celestron CGX-L mount still have to be connected through the hand controller?? Unless I'm missing something.....or have a particular thing not set right....I cannot move my mount with the arrows on the screen to finely frame my target. Can someone help me out??
Thanks!!
Tom
It's been awhile since I've checked/tried. Does a Celestron CGX-L mount still have to be connected through the hand controller?? Unless I'm missing something.....or have a particular thing not set right....I cannot move my mount with the arrows on the screen to finely frame my target. Can someone help me out??
Thanks!!
Tom
Yes, you still need to use the hand controller
Really disappointed that my Canon EOS R3 is not supported by the ASIAir mini I just bought. When will this flagship camera be added to your list of supported devices please? Absolutely shocking that the R5 and R6 work but the R3 does not.
- Edited
It looks like ZWO, Have screwed things up again, I cannot understand why they dont solve all the issues that most users are having with there current devices, all they seem to do, is bring out a new item (eg the mini ) or new firmware which they must know isnt working properly, and expect current users to deal with it, It also looks like every time some one has and issue, and posts it on here to try and get a solution, ZWO, very rarely respond with a solution, and anything they suggest, to fix a problem just creates other problems, for example, Why dont they do something about being able to reload previous firmware, I believe that would be a great thing, because it is quite obvious any new firmware they release, Is just a load of crap........I really hope some other company comes up with a similar device like the ASIAIR, so the people having to deal with all these problems, at least have an option to go to another product, hopfully made by a company that cares about there customers
At Least thats how i feel