It's pretty straightforward. Setup an artificial star at a workable distance for your optics. I have the Hubble 5-star Artificial Star with 5 star sizes to choose from. Use the smallest one you can. Set exposure and gain and ensure Auto Select star can pick out the artificial star.
Initial steps should be set high enough to make a noticeable change. Then run an autofocus routine. Observe the graphs. Once it reverses directions note if the reverse HFR values are above of below the earlier HFR at the same step position.
If you are above, you have uncorrected backlash. Below, the backlash is overcompensated for.
You can do this with real stars, but atmospheric seeing will reduce the accuracy. Using average of 2 or more frames helps.

Read More...

I used an artificial star averaging 2 frames. Then adjusted the backlash value until the points focusing in matched well with the points focusing out.

Read More...

The EKOS Scheduler is not designed for multiple parallel scopes and cameras. But another user reported success with two strategies.
First Strategy. One INDI server with all his equipment that included the second camera and focuser and an instance of CCDciel to orchestrate a capture sequence and autofocus.
Second strategy: A virtual machine running KStars and EKOS. Selecting NO when asked if you wish to stop the current instance of INDI.
They reported the second strategy downloaded images more quickly.

Read More...

Andrew replied to the topic 'How To Do Image Stacking' in the forum. 3 days ago

So neither of those initial replies are what you are interested in. While transferring images to be stacked is fine, rather than live stacking, it is typically done once all the images have been taken along with what are known as calibration frames.
The other reply regarding focus stacking in an entirely different image processing technique that is not applicable to astrophotography. 

What you are looking for is software that aligns and combines images with an averaging algorithm. That also can apply calibration frames used to clean up noise and gradients. 
DeepSkyStacker and SIRIL are free. There are also more advanced programs such as Pixinsight and Astro Pixel Processor.
You will need to post-process your stacked images in a good photo editor such as Photoshop, or GIMP which is free. 

This is something you'll want to do on a desktop, not on a raspberry pi. 

Read More...

Andrew replied to the topic 'Maximum focus Position' in the forum. 3 days ago

The maximum focus position is defined in the sesto senso driver as 200,000. If you require more steps, you can edit this value and compile a customized version for yourself.

159     FocusAbsPosN[0].max   = 200000.;
github.com/indilib/indi/blob/master/driv...cuser/sestosenso.cpp

Read More...

Add the GPSD INDI driver to your INDI profile as an AUX driver and configure the device port accordingly.

Read More...

"Adaptive Sampling" Is that why I saw my focus frames appeared to have a progressively lower resolution? It didn't seem to harm the focus routine, but I would only see a pixelated mess in the module's image viewer after a while.

Read More...

Andrew replied to the topic 'Orion StarShoot AutoGuider Pro' in the forum. 6 days ago

QHY Driver.

Read More...

Andrew replied to the topic 'AstroPi3 Scripts revised' in the forum. 1 week ago

setupAstroRaspbianPi.sh includes code that comments out dtoverlay=vc4-kms-v3d/ in /boot/config.txt.
This line must be left uncommented to use the second HDMI output on a Raspberry Pi 4.

# This comments out a line in Raspbian's config file that seems to prevent the desired screen resolution in VNC
# The logic here is that if the line does exist, and if the line is not commented out, comment it out.
if [ -n "$(grep '^dtoverlay=vc4-kms-v3d' '/boot/config.txt')" ]
then
    sed -i "s/dtoverlay=vc4-kms-v3d/#dtoverlay=vc4-kms-v3d/g" /boot/config.txt
fi
if [ -n "$(grep '^dtoverlay=vc4-fkms-v3d' '/boot/config.txt')" ]
then
    sed -i "s/dtoverlay=vc4-fkms-v3d/#dtoverlay=vc4-fkms-v3d/g" /boot/config.txt
fi
 


Read More...

So. I took this and ran with it for my specific needs with the Star Adventurer.
I managed to write in some additional code that will convert for me what position on the Star Adventurer's time dial corresponds to an Hour Angle.
From line 148 in source code kstars/widgets/infoboxwidget.cpp

    dms sa(lst - p->ra());
        if (sa.Hours() < 6.0)
    {
        sa.setH(18 + sa.Hours());
        sign = 'W';
    }else if (sa.Hours() < 12.0)
    {
    sa.setH(-6 + sa.Hours());
    sign = 'W';
    }else if (sa.Hours() < 18.0)
    {
    sa.setH(6 + sa.Hours());
    sign = 'E';
    }else
    {
    sa.setH(-18 + sa.Hours());
    sign = 'E';
    }
    m_strings << i18nc("Star Adventurer", "Star Adventurer") + ": " + sign + " " + sa.toHMSString();
 


Read More...

I just performed a KStars update and was pleasantly surprised to see my wish has been fulfilled. Thank you very much Jasem. Excellent work!


This is a cheat sheet I made to convert the Hour Angle to a position on the back of the Star Adventurer. It has proven to be quite an accurate method for me.
 


Read More...