SC4 / OA-X jumping problem

Discussion in 'Guiding and Adaptive Optics - StarChaser and AO' started by michael74, Apr 25, 2025.

  1. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    8,970
    Location:
    Earth
    Try it please. We think it will solve the problem for many customers.
     
  2. michael74

    michael74 Cyanogen Customer

    Joined:
    Apr 25, 2025
    Messages:
    24
    Very well, I will get back to you as soon as I have been able to test
    thank you
     
  3. JoshuaHufford

    JoshuaHufford Cyanogen Customer

    Joined:
    Oct 10, 2014
    Messages:
    576
    Any improvements for an AO-8? For the most part mine works but I do get some odd behavior with it sometimes.

    My subscription has expired, if I won't see any improvements I'll probably wait a while before I renew.
     
  4. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    8,970
    Location:
    Earth
    Hi Joshua - the improvements are not specific to the AO-8; there are improvements for the SBIG w/AO (eg STXL/STX/STT more modern SBIGs with AO), SBIG w/AO Legacy (Old ST/STL), and DL Imaging (Aluma, StarChaser, etc).
    You can always request a free trial, test it out for 30 days, and then upgrade if it works for you.
     
  5. JoshuaHufford

    JoshuaHufford Cyanogen Customer

    Joined:
    Oct 10, 2014
    Messages:
    576
    Thanks for the info.
     
  6. Martin Pugh

    Martin Pugh Cyanogen Customer

    Joined:
    Oct 27, 2014
    Messages:
    497
    Michael…have you given v7.2 a try? Have you been successful?
     
  7. michael74

    michael74 Cyanogen Customer

    Joined:
    Apr 25, 2025
    Messages:
    24
    not yet, this weekend
     
  8. michael74

    michael74 Cyanogen Customer

    Joined:
    Apr 25, 2025
    Messages:
    24
    hello Colin,
    I haven't tested version 7.2 yet.
    Is it possible to automatically disable tracking with the OA-X in maximDL during autofocus to prevent the OA-X from doing anything while autofocusing?
     
  9. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    8,970
    Location:
    Earth
    No, there is no option to do that.
    It is an interesting suggestion.
    Normally, I manually stop AO tracking before focusing.
    DLAO_STop.png
     
  10. michael74

    michael74 Cyanogen Customer

    Joined:
    Apr 25, 2025
    Messages:
    24
    ok thank you, it will be good to create this improvement into maximDL
     
  11. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    8,970
    Location:
    Earth
    I have put in a Feature Request for consideration.
     
  12. michael74

    michael74 Cyanogen Customer

    Joined:
    Apr 25, 2025
    Messages:
    24
    Hello Colin, i have installed maximDL V7.2
    in SC4 setup advanced, the dlapi.dll file is now version 4.1.2.5 and DLAPIWrapper.dll is 4.0.2.0. is it correct?
    Can you help for setting for beginning:
    here my setting: is it good for beginning?
    -Agressiveness: 10
    - max move pixels: 5 to 10
    - binning 2 for tracking
    - drive activation level: +/- 80%
    - Bump time (1/100sec): 10
    - calibration time (sec): X: 2 / Y: 2
    - SNR threshold: 50
    - track box 32x32
    is there a problem if X axis and Y axis in AO tracking speed are different (100 vs 70) after automatic calibration?
     
  13. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    8,970
    Location:
    Earth
    Yes, that is correct.
    You will need to experiment with these settings.

    Some rough calculations:
    Sidereal rate is 15.041 arcseconds per second.
    Guide camera pixel size = 4.8um
    Focal length CDK14 f/7.2 = 2560mm.
    Guider camera has 0.7x reducer, so 2560 x 0.7 = 1792mm
    Guider resolution = 4.8 / 1792 * 206 = 0.55 arcseconds per pixel.

    Binning 2x2 = OK. 1.1 arcsecond per pixel resolution on your scope. Start with that.
    Bin 3x3 = 1.65 might be better. See what works best.
    If the seeing is bad (> 2-4 arcseconds, definitely increase to 3x3 or 4x4).

    What is the guide rate on your mount? eg 1x sidereal rate?
    Some of the PW L mounts default to 0.5x

    Bump time - 10/100 = 0.1s x guide rate
    Assuming guide rate = 1x sidereal
    0.1 x 1 x 15.041 = 1.5 arcsecond bump.

    Assuming guide rate = 0.5x sidereal
    0.1 x 0.5 x 15.041 = 0.75 arcsecond bump.

    So at 1x sidereal 0.1s bump is only ~1 pixel on the guider. That's might be too small.
    Try 0.5s bump = 7.5 arcseconds, which is 4.5 to 7 pixels, which should fit in the track box.

    Calibration time:
    2s will only move the star 2 x 1 x 15.041 = 30 arcseconds on the guide sensor = 30/1.1 = 27 pixels at 2x2 binning.
    Try a longer calibration time like 10s = 136 pixels.

    Only a perfect system would be 100, 100.
    If it was 100 vs 30, there is a problem.
     
  14. michael74

    michael74 Cyanogen Customer

    Joined:
    Apr 25, 2025
    Messages:
    24
    Hello Colin,
    I followed all your instructions, I installed version 7.2 of Maxim DL
    I set it to bin3, the guide star location is done with a 2s exposure and I find a guide star with a brightness of 350. I set the track time to 1s (I can't get it below), aggressiveness to 10, max move to 10, binning 3, I manage to get a star with an SNR of 130. I don't guide the mount, only the AOX. It works, but there is still occasional (about once every minute) a guide star jump. This phenomenon is more significant when the SNR is lower than 100. Between these rapid jumps, the star remains well centered, the OAX is doing its job well. At home I am currently at Bortle 6 (19 Mag/arcsec2) (summer and moon present). In winter I am Bortle 4. I have no periodic error on my Planewave L350 mount, the balance is perfect and the polar alignment is perfect.
     
  15. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    8,970
    Location:
    Earth
    I can get it below by changing 1s - change the value with the spinner arrows [^][v] or enter the number.
    tracktime.png
    Or do you mean something else?

    Verify that Options - Enable Auto-dark is checked (enabled) This should improve SNR.
    enableautodark.png

    Try to Decrease Max Move. It sets how far in pixels the AO can tilt.
    See if it improves (decreases) RMS Wander (pixels).

    Ok.
    Upper winds or gusts can cause enough of a deviation that the AO correction is too much.

    Try to Decrease Aggressivness.
    AO will move an amount of pixels = (Agr / 10) x pixel correction needed.
    eg If the star moved 6 pixels, AO is trying to move 10/10 * 6, which is too much on average.
    See if it improves (decreases) RMS Wander (pixels).

    Ok, that is good news.

    So change the Max Move and Agressiveness, and lets see if that decreases the jumps.

    Very nice! Thank you for this information.
     
  16. michael74

    michael74 Cyanogen Customer

    Joined:
    Apr 25, 2025
    Messages:
    24
    I mean
    If I go below a second, the guide star becomes too weak and the AOX loses it, or there's a lot of jumping. I've already tried reducing the aggressiveness and max move, but it doesn't make the jumps disappear, which are certainly less violent than before the update but still present, and we see the stars splitting over a 1 to 2 minute acquisition on the main camera. I tried again with a guide star SNR at 150: there are still jumps (1 every 1-2 minutes), sometimes in bursts. There is no wind
     
  17. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    8,970
    Location:
    Earth

Share This Page