Azaqui 3)Any follow up attempts at calibrating are unsuccessful with the same settings and target - this is the last calibration step before a failure:

The clue of why calibration failed is right in that screenshot.

Notice that it says "West Step 60, dist 21.7."

The way PHD2 autoguiding works is to detect how many pixels the guide star has moved from its original location, in delta-X and delta-Y in the coordinate system of the guide image.

PHD2 then tries to send a slow slew to the hour angle and declination motors of your mount to move the guide star back.

But, unless your guide camera angle is precisely aligned to the Right Ascension and Declination axis, the delta-x and delta-y are not directly related to the HA and declination, but through a rotation matrix. Even after rotation from (RA, declination) to (delta-X , delta-Y), PHD2 also needs to know the plate scale of the guide camera (i.e., how many arc seconds in RA and declination corresponds to a pixel.

Once it knows how much to correct the hour angle and declination, PHD2 then sends a N millisecond slew to the RA motor, and M milliseconds to the declination motor. These are called guide pulses.

To get the angle and plate scales, PHD2 goes trough a claibration process by purposefully applying the known guide pulses. In ASIAIR, the duration of these "calibration pulses" are given in the "Calibration Step" value of the Guide Settings window.

In your case, PHD2 has applied 60 calibration steps and the guide star has only moved 21.7 pixels!

PHD2 therefore gives up.

If you have a short focal length guide scope, you need to increase the Calibration Step time, and/or increase the guide rate (in Telescope settings).

Typically, with high quality mounts that only needs gentle guiding, you want to set the guide rate to 0.5 sidereal rate (i.e., 7.5 arc seconds per 1000 milliseconds). If the slope of the periodic error of the mount can become large, you can typically increase the guide rate to 0.75, or even 1x sidereal rate.

You then adjust the "Calibration Step" until you get somewhere between 10 and 20 setps for that "dist" number to reach or exceed 25. Lower than 4 steps will give you inaccurate guiding, greater than 20 steps is just a waste of time, but no real harm otherwise. 60 steps is too many to complete 25 pixels worth of movement, since that is when PHD2 decides your mount is not moving enough.

Chen

    w7ay
    As I mentioned I tried different calibration times of up to 4000ms.

    The issue is I cannot set the guiding rate as you suggested as ASIAIR implementation does not support it :/

    I think this is the core issue here -
    ASIAIR has to support guide rates for NexStar SE type
    mounts for it to be able to move enough.

      Azaqui The issue is I cannot set the guiding rate as you suggested as ASIAIR implementation does not support it :/

      Can you change it with your Hand Controller? With my mount, I can change the guide rate from either ASIAIR or from the Hand Controller; both works.

      As I mentioned I tried different calibration times of up to 4000ms.

      Try it again. This time, note down the "dist" after 60 steps (I know, it takes a long time to do; but you really don't have much of a choice, except to use Stellarmate, INIGO Sky, or even AstroBerry, if you want something simple minded as ASIAIR).

      If 2000ms gives you dist of 11, and 4000ms gives you dist of 22, then 8000ms might be enough.

      Remember, you using a guide scope with just 120mm focal length. Most of us are using guide scopes between 200mm and 800mm focal lengths (or even with OAG at 2000mm focal length). And on top of that, who knows what the guide rate is (check the hand controller, just in case).

      Chen

      There is no guide rate setting in the controller for NexStar 5SE, that version of the mount also does not have ST4 input.

      Not sure if there is a point in doing the super-long calibration steps though, as if guiding can't correct fast enough, it will still not do its job (the screengrab with guiding pulses going full blast and never getting smaller as the correction is not enough)

      BTW thank you for trying to help me!

      Azaqui

      1. Change the mount speed to the max then press the four directions to see if your mount moves, this is to make sure your mount is connected well.
      2. Change the mount speed to 1X in the MCP, calibration step 2000 to try.
      3. If the guide calibration still fails, please upload the log, our tech will analyze it.(Also tell us your email address so that we can locate your log)
        Thanks,

      @tech@zwo#54700

      Every time I made those attempts the goto functionality worked perfectly, but I will re-check that before the log thing.

      Where do I find the log, and how I upload it?

        Azaqui hi, you can find the "submit" in about settings page. Please submit the log as prompted. After that, don't forget to tell me the email. Thank you very much~

        @asiair@zwo#54730

        Ok finally got clear skies, went through the procedure and uploaded the logs.

        I did the guiding calibration as per your specs - x1 rate 2000ms cal step.

        How do I tell you my email (don't want to just post it on the forum)?

          As a side note there is no difference between different slew rates, and the distance between consecutive steps can decrease....

          • w7ay replied to this.

            Azaqui As a side note there is no difference between different slew rates, and the distance between consecutive steps can decrease....

            Did you check if tracking was on when you observed the East-West distance decreasing? It is the Tracking switch in the Mount Settings window.

            Tracking has to be on when you are guiding (or calibrating guiding).

            Chen

              @tech@zwo#54808 Done!

              Once again, thank you for looking into that!

              16 days later

              Are there any updates on this weeks later?

              5 days later

              Guys, this is no way to do customer support, I spent quite a lot of money on your gear

              6 days later

              @A

              @tech@zwo#54808

              Any updates?
              I still cannot use my ASIAIR because of no tracking…

                Azaqui Hi Azaqui, Sorry, our devs are working on this, if there are any updates, we will update here.
                Thank you very much for your patience and support.

                2 years later

                I know this is an old thread, but I am having a similar issue, has this ever been resolved? Has anyone gotten Guiding with the Nexstar mount and ASI Air working?

                  SFA80Wu9 Could you submit a bug report in the ASIAIR app for further analysis? thank you.

                  Write a Reply...