larkinsen We are already researching this issue, and the next version will complete the optimization

    I own an ASIAIR plus, and when I connect my Nikon Z7 I cannot raise the ISO over 400. Although I understand that the camera is ISO invariant after 400, is there a way raise it over 400? I love the device but this is limiting my shooting.

      Rcacao86 Odd. I use an AA Pro with a ZII and I successfully run it at ISO1600 (have tried other ISO on occasion but 1600 is my normal setting).

          So I went out last night to try and give it my first try,

          Using a Sony A7IV with the ASIAIR Plus - The app does recognize the Sony A7IV (USB - PC Remote) but then message comes up saying
          "Turn off any power-saving and WIFI/NC features
          Camera is not set to BULB. Reconnect it after setting"

          Camera is set to BULB mode have tried Rebooting everything and still hitting the same problem.
          Havent really gotten past that at all. Cant get a Preview image loaded up at all.

          Was not able to do anything with the ASIAir app last night. Thankfully I got some good Polar Alignment and got 2 minutes exposures with no trails. But the app did not work with the Sony A7IV. Anyone else having any luck?

            Hello.. I have a strange problem with Asi air after the last OS update. I practically can't do polar alignment, it gives too big an error and if it indicates to raise ⬆️ the frame in R.A, I raise it but the error increases; so even if it says to go, for example, to the left ⬅️ in Azimuth I do it, but here too the error increases.
            I have to do the opposite of what it indicates to decrease the error..😄 but you never get to hit and go below 1' for both Height and Azimuth (indeed, if one fixes it, the other increases in error🤯).
            I've been using asiair for years but it never happened to me... what could it be? Has anyone had the same problem?
            I tried to see if it was a focal problem, putting 0mm in the initial screen, but nothing...
            I use a C9 on AZeq6 Gt mount

              w7ay
              I did, I found that thread and got happy for a second as I thought I found the solution. I followed the guidance and it did not work. App recognizes the camera but taking a PREVIEW shot wont work, still get Exposure Failure. Cant make changes to the EXP time or control the camera's shutter from the app. Hopefully an update provides a solution soon.

                When will you fix the issue with the Nikon Z71. I can't pick any ISO other than 400. I want to be able to shoot at ISO 1000 or 1600 but the app gives the option to change, however after the photo is shot the FIT image shoes it was shot at ISO 400 and the RAW on camera also shows iso 400. This is crazy, I bout the ASIAIR, guide camera and scope and now I'm stuck at ISO400. I literally now have to shoot with a shutter release due to this bug. Please fix

                Mapleleaf I don't know what else to try. I'm going to reset the ASIAIR and my camera but I'm out of ideas.

                  So are there any future advancements on improvements on the histogram adjustments in Live Stack mode
                  to help improve the ability to do EAA with the ASIAIR? It is the biggest hold up of making the ASIAIR a great EAA device.
                  As it stands now the histogram really sucks with no color or mid level adjustments. Even the ASI Studio is much better.

                    Kring Thank you for the suggestion, but it's not the cable. I already tried multiple cables without any success. All tried cables work just fine if I connect the camera to my laptop, so they're all good.

                    At this moment, I have no solution (yet). The only way to use this is to capture using my laptop (camera connected via usb directly to computer) and to use the ASIair only for guiding... but I won't be able to do dithering.

                      scopesnc Nope I guess not from the lack of response. ASIAIR will never be a useable EAA device with out a good histogram tool for adjustments. Shame because as it sits now the histogram with no color controls makes it useless for EAA. No wonder so many are not using it for EAA.

                          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.

                          • w7ay replied to this.

                            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

                              12 days later

                              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.

                              • w7ay replied to this.

                                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

                                    w7ay

                                    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