Mount control can be either done via the Sky Map interactively or via the Mount Control Panel in the mount module. Configure telescope properties (focal length & aperture) for both your primary imaging telescope and guide scope. However, it is recommended to select the telescopes in the equipment profile and not change the values directly in the mount module.
- Aperture (mm): Specify the value of aperture for your telescope. Defaults to the values set for your telescope in your current running profile.
- Focal Length (mm): Specify the value of focal length for your telescope. Defaults to the values set for your telescope in your current running profile.
Configurations: You can set up to 6 configurations for your mount module. To save the information, select an unused Config # from the drop-down menu and then enter a name in the field next to it, then click on Save Telescope Info.
It is recommended to specify the primary & guide telescopes in the Ekos Profile as this ensures the correct information is always used for this profile regardless of the INDI driver state.
- RA: Right Ascension
- DEC: Declination
- AZ: Azimuth
- ALT: Altitude
- HA: Hour Angle
- LST: Local Sidereal time
You can do a Meridian Flip from the Mount Module.
Equatorial mounts flip after crossing the meridian in order to prevent the imaging equipment train from hitting the tripod. With Ekos, you can set an hour angle limit which if exceeded, the mount will be commnded to flip. The mount must begin tracking east of the meridian in order to the meridian flip to be commanded in Ekos.
When commanding a meridian flip, Ekos will suspend the autoguiding process and waits until the mount completes the flip. Once the mount begins tracking again post meridian flip, Ekos will plate-solve and make any necessary slew commands to bring the mount to the exact location it was tracking prior to the flip.
Next, it will automatically capture a frame and select a suitable guide star, performs calibration, and resumes autoguiding. If In-Sequence focuing is enabled, it will also capture and focus a suitable star. It then resumes the capture process form where it left.
All these steps are completely automated and require no user intervention!
- Flip if HA >: Request a meridian flip if the hour angle exceeds the specified value. Capture and Guiding will be suspended and resumed after the flip is complete.
- Hours: Set Hour Angle unit to Hours
- Degrees: Set Hour Angle unit to Degrees. If the mount is configured to flip at 5 degrees, set the value in Ekos to 3 degrees less (2 degrees).
- Pier Side: Shows the pier side direction.
- Clear Model: Deletes all mount alignment points.
- Clear Parking: Clears parking information.
- Purge all configuration: Deletes all the configuration files (config #1, config #2, etc)
- Park At: Specify the time when you would to park your mount.
- Everyday: If you want to park your mount everyday at a specific time, then check this checkbox.
- Timer: Displays the countdown until the mount is parked. To activate the countdown, click on the Start button.
- Start : Starts the Auto Parking process.
- Stop : Stops the Auto Parking process.
Auto Parking should not be used when scheduler is active as it can interfere with the scheduler operation.
Mount Control: Opens up the Mount Control dialog. This control is also accessible from KStars toolbar.
Tracking: You can enable or disable tracking from the mount module.
Parking: You can park or unpark your mount from the mount module.
Limits: You enable Altitude Limits or Hour Angle Limits if you do not wish your mount to move past a specific limit. The values are expressed in hours. Setting a 1 hour (HA) limit means your mount is restricted to 15 degrees east and west of the meridian. Setting it to 3 HA (3*15) means your mount is free to move 45 degrees east and west of the meridian.
Clicking on this button will open the Mount Control dialog where you will be able to control your Mount manually using arrow buttons and abort movement using a STOP button. It is possible to reverse the controls if you feel it is easier that way to control your mount. The speed of the mount can be controlled using a slider which has four speeds: Guide, Centering, Find, and Max. The details of the mount's position are shown, which are: RA, DEC, AZ, ALT, HA, and ZA. You can specify the target you want to move to using the Target field. To specify a Target, click on the magnifier icon and selecting an object. You can specify manually where to go to by filling the RA/AZ or DE/AL field and then choosing the type by clicking on the appropriate setting. There is a status bar that shows if the mount is idle or doing some action. The small button on the bottom-right corner is used to sync the GPS location. There are four main options for automatic mount control:
- GOTO: Slews your mount to the selected target and tracks it.
- SYNC: Sets the mount coordinates as the current coordinates. No motion takes place.
- PARK: Park the mount to its parking position. The parking position varies from mount to mount. Some driver support custom parking positions while others support only one static parking position. For GEM mount, parking position is usually with the mount looking toward the celestial pole with the counter weights down.
- UNPARK: Unparks the mount so it can be moved.
The observatory module is used to manage the dome and weather-triggered shutdown procedure. It has weather data directly displayed in the module. Along with the configurable thresholds for Warning and Alert states, you can rest easily knowing that KStars can take the appropriate actions to protect your observatory from adverse weather conditions. The observatory module also includes a dedicated weather widget with love plotting for each parameter.
- Position: Controls the position of the Dome.
- Motion: You can move the Dome in four ways.
- Absolute: Select the absolute position you want the Dome to move and then click on Move (abs). This will move the Dome to the absolute position you set.
- Relative: Select the amount of degrees (either positive or negative) you want the Dome to move from the current position and then click on Move (rel). This will move the Dome to the relative position you set.
- Clockwise (CW): Rotates the Dome Clockwise forever until you click on Abort.
- Counter Clockwise (CCW): Rotates the Dome Clockwise forever until you click on Abort.
- Motion: You can move the Dome in four ways.
- Slaving: If enabled, Dome motion will follow telescope motion.
- Park/Unpark: Park or Unpark the Dome. For advanced control, please use the INDI Control Panel.
- Abort: Aborts the Dome motion.
- Open/Close: You can open or close your shutter through the observatory module.
- Dome: If selected, the dome needs to be unparked for the observatory status being "READY".
- Shutter: If selected, the shutter needs to be open for the observatory status being "READY".
- Weather: If selected, the weather needs to be OK for the observatory status being "READY".
- Ready: Observatory status. Select the observatory elements that are relevant for the status:
- Dome: unparked → ready
- Shutter: open → ready
- Weather: OK → ready
Current data of the weather sensors. Click on the sensor name to display its data over time.
- auto scale values: Scale the value axis to the current value range.
- : Clear sensor data history.
- Graph: You can see the values of both axes if you hover over the graph. You can zoom in or out using the scroll wheel.
- Alert: Check this checkbox in order to get an Alert whenever any weather value goes under or above the range set in your weather driver INDI Control Panel.
- Warning: Check this checkbox in order to get an Warning whenever any weather value is close to going under or above the range set in your weather driver INDI Control Panel.
- Park Dome: Parks the dome whenever you get a warning.
- Close Shutter: Closes the shutter whenever you get a warning.
- Status: Shows the status of the warning.
- Delay (sec): Delays the warning after n amount of seconds.
Ekos Alignment Module enables highly accurate GOTOs to within sub-arcseconds accuracy and can measure and correct polar alignment errors. This is possible thanks to the astrometry.net solver. Ekos begins by capturing an image of a star field, feeding that image to astrometry.net solver, and getting the central coordinates (RA, DEC) of the image. The solver essentially performs a pattern recognition against a catalog of millions of stars. Once the coordinates are determined, the true pointing of the telescope is known.
Often, there is a discrepancy between where the telescope thinks it is looking at and where it is truly pointing. The magnitude of this discrepancy can range from a few arcminutes to a couple of degrees. Ekos can then correct the discrepancy by either syncing to the new coordinates, or by slewing the mount to the desired target originally requested.
Furthermore, Ekos provides two tools to measure and correct polar alignment errors:
- Polar Alignment Assitant Tool: Very easy tool to measure and correct polar errors. It takes three images near the celestial pole (Close to Polaris for Northern Hemisphere) and then calculates the offset between the mount axis and polar axis.
- Legacy Polar Alignment Tool: If polaris is not visible, this tool can be used to measure and correct polar alignment errors. It captures a couple of images near the meridian and east/west of the meridian. This will enable the user to adjust the mount until the misalignment is minimized.
At minimum, you need a CCD/Webcam and a telescope that supports Slew & Sync commands. Most popular commercial telescope nowadays support such commands.
For the Ekos Alignment Module to work, you have an option of either utilizing the online astrometry.net solver, offline, or remote solver
- Online Solver: The online solver requires no configuration, but it requies active internet connection and depending on your Internet bandwidth, it might take a while to upload and solve the image.
- Offline Solver: The offline solver can be faster and requires no Internet connection. In order to use the offline solver, astrometry.net must be installed natively in addition to the necessary index files. This option is not available in Windows.
- Remote Solver: The remote solver is an offline solver the resides on a different machine (for example, you can use Astrometry solver on StellarMate). Captured images are solved on the remote machine.
ASTAP is an astrometric plate solver, stacking of images, photometry, and FITS Viewer application available for Windows, MacOS, and Linux on multiple architectures.
Ekos included support for solving via ASTAP in the Align module in addition to the existing astrometry.net solver. ASTAP employs a different method to solve images making it extremely fast while at the same time requiring a smaller star catalog compared to other astrometric solvers.
You need to download and install the G17 Star Catalog for ASTAP to work locally.
ASTAP Solver Settings
- Search Radius: The program will search in a square spiral around the start position up to this radius.
- Down Sample: Down sample prior to solving. Also called binning. A zero value will result in auto selection downsampling.
- Update FITS: Update the fits header with the found solution.
- Force Large Search Window: Improve solving reliability in some cases. Search window will be large with overlap but it can slow down solving.
If you are planning to use Offline astrometry then you need to download astrometry.net application.
Astrometry.net is already shipped with StellarMate so there is no need to install it. Index files from 16 arcminutes and above (4206 to 4219) are included with StellarMate. For any additional index files, you need to install them as necessary. To use Astrometry in StellarMate from a remote Ekos on Linux/Windows/MacOS, make sure to select Remote option in Ekos Alignment Module. Furthermore, make sure that the Astrometry driver is selected in your equipment profile.
To use astrometry.net offline (without internet connection) under Windows, you need to download and install the ANSVR Local Astrometry.net solver on your Windows PC. The ANSVR mimics the astrometry.net online server services on your local computer; thus the internet not required for any astrometry queries. From the point of view of Ekos, it is still communicating with an online astrometry.net server.
After installing the ANSVR server and downloading the appropriate index files for your setup, make sure ANSVR server is up and running and then go to Ekos Alignment options where you can simply change the API URL to use the ANSVR server as illustrated below:
Do not forget to include the full URL including the http part. In Ekos Align module, you must set the solver type to Online so that it uses the local ANSVR server for all astrometry queries. Then you can use the align module as you would normally do.
Remember as indicated above that StellarMate already includes astrometry.net. Therefore, if you would like to use StellarMate remotely to solve your images, simply change solver type to Remote and ensure that your equipment profile includes Astrometry driver which can be selected under the Auxiliary dropdown. This is applicable to all operating systems and not just Windows.
Offline vs. Online
Offline solver option is not available under Windows even if you download a local copy of astrometry.net. This is because the offline option requires a native astrometry.net installed, while on Windows the local astrometry.net provides a web-interface to mimic the online astrometry.net service. Use Online option and change the web API as indicated above to make it behave like the offline version. There is no performance differences between a native offline astrometry.net and a non-native one on Windows that uses the Web Services API to communicate with Ekos.
Astronomy.net is already included with KStars for MacOS, so no need to install it.
Astrometry.net is already included with StellarMate. But if you want to reinstall it anyway under Ubuntu, use this command:
sudo apt-get install astrometry.net
Download Index Files
For offline (and remote) solvers, index files are necessary for the solver to work. The complete collection of index files is huge (over 30 GB), but you only need to download what is necessary for your equipment setup. Index files are sorted by the Field-Of-View (FOV) range they cover. There are two methods to fetch the necessary index files: The new download support in Align module, and the old manual way.
Automatic download is only available for Ekos users on Linux & MacOS. For Windows users, please download ANSVR solver.
To access the download page, click Options button in the Align module and then select Astrometry Index Files tab. The page displays the current FOV of your current setup and below it a list of available and installed index files. Three icons are used to designate the important of index files given your current setup as following:
You must download all the required files, and if you have plenty of hard drive space left, you can also download the recommended indexes. If an index file is installed, the checkmark shall be checked, otherwise check it to download the relevant index file. Please only download one file at a time, especially for larger files. Once you installed all the required files, you can begin using the offline astrometry.net solver immediately.
You need to download and install the necessary index files suitable for your telescope+CCD field of view (FOV). You need to install index files covering 100% to 10% of your FOV. For example, if your FOV is 60 arcminutes, you need to install index files covering skymarks from 6 arcminutes (10%) to 60 arcminutes (100%). There are many online tools to calculate FOVs, such as Starizona Field of View Calculator.
|Index Filename||FOV (arcminutes)||Debian Package|
|index-4219.fits||1400 - 2000||astrometry-data-4208-4219|
|index-4218.fits||1000 - 1400|
|index-4217.fits||680 - 1000|
|index-4216.fits||480 - 680|
|index-4215.fits||340 - 480|
|index-4214.fits||240 - 340|
|index-4213.fits||170 - 240|
|index-4212.fits||120 - 170|
|index-4211.fits||85 - 120|
|index-4210.fits||60 - 85|
|index-4209.fits||42 - 60|
|index-4208.fits||30 - 42|
|index-4207-*.fits||22 - 30||astrometry-data-4207|
|index-4206-*.fits||16 - 22||astrometry-data-4206|
|index-4205-*.fits||11 - 16||astrometry-data-4205|
|index-4204-*.fits||8 - 11||astrometry-data-4204|
|index-4203-*.fits||5.6 - 8.0||astrometry-data-4203|
|index-4202-*.fits||4.0 - 5.6||astrometry-data-4202|
|index-4201-*.fits||2.8 - 4.0||astrometry-data-4201-1
|index-4200-*.fits||2.0 - 2.8||astrometry-data-4200-1
The Debian packages are suitable for any Debian-based distribution (Ubuntu, Mint...etc). If you downloaded the Debian Packages above for your FOV range, you can install them from your favorite package manager, or via the following command:
sudo dpkg -i astrometry-data-*.deb
On the other hand, if you downloaded the FITS index files directly, copy them to
It is recommended to use a download manager as such DownThemAll! for Firefox to download the Debian packages as browsers' built-in download manager may have problems with download large packages.
How to Use?
Ekos Align Module offers multiple functions to aid you in achieving accurate GOTOs. Start with your mount in home position with the telescope tube looking directly at the celestial pole. For users in Northern Hemisphere, point the telescope as close as possible to Polaris. It is not necessary to perform 2 or 3 star alignments, but it can be useful for some mount types. Make sure your camera is focused and stars are resolved.
- Capture & Solve: Capture an image and determine what region in the sky the telescope is exactly looking at. The astrometry results include the equatorial coordinates (RA & DEC) of the center of the captured image in addition to pixel scale and field rotation. Depending on the Solver Action settings, the results can be used to Sync the mount or Sync and then Slew to the target location. For example, suppose you slewed the mount to Vega then used Capture & Solve. If the actual telescope location is different from Vega, it will be first synced to the solved coordinate and then Ekos shall command the mount to slew to Vega. After slew is complete, the Alignment module will repeat Capture & Solve process again until the error between reported and actual position falls below the accuracy thresholds (30 arcseconds by default).
- Load & Slew: Load a FITS or JPEG file, solve it, and then slew to it.
- Polar Alignment Assistant: A simple tool to aid in polar alignment of German Equatorial Mounts.
- Legacy Polar Alignment Tool: Measure polar alignment error when a view of the celestial pole (e.g. Polaris for Northern Hemisphere) is not available.
Warning! Never solve an image at or near the celestial pole (unless Ekos Polar Alignment Assistant Tool is used). Slew at least 20 degrees away from the celetial pole before solving the first image. Solving very close to the poles will make your mount pointing worse so avoid it.
- CCD: Select CCD to capture from
- Exposure: Exposure duration in seconds
- Accuracy: Acceptable difference between reported telescope coordinate and actual solved coo
- Bin X: Set horizontal binning of the CCD
- Bin Y: Set vertical binning of the CCD
- Scope: Set the active telescope in case you have different Primary and Guide scopes. FOV is re-calculated when selecting a different telescope.
- Options: Options that are passed to the astrometry.net solver. Click the Edit button to explore the options in detail.
- Solver: Select solver type (Online, Offline, Remote). Remote solver is only available when connecting to a remote device.
By default, the solver will search all over the sky to determine the coordinates of the captured image. This can take a lot of time; therefore, in order to speed up the solver, you can restrict it to only search within a specified area in the sky designated by the RA, DEC, and Radius options above.
Options for offline and online solvers.
Most of the options are sufficient by default. If you have astrometry.net installed in a non-standard location, you can change the paths as necessary.
- Use Sextractor not python: This allows you to use Sextractor to make XY Lists in order to avoid using python with astrometry.net. It vastly improves the solver speed. This is a good option to be enabled on MacOS since they don't need to install python.
- Rotator: Rotator threshold in arc-minutes when using Load & Slew. If the difference between measured position angle and FITS position angle is below this value, the Load & Slew operation is considered successful.
- Time out: Timeout in seconds to wait for astrometry solver to complete.
- WCS: World-Coordinate-System is a system for embedding equatorial coordinate information within the image. Therefore, when you view the image, you can hover it and view the coordinate for each pixel. You can also click anywhere in the image and command to the telescope to slew there. It is highly recommeneded to keep this option on.
- Overlay: Overlay captured images unto the sky map of KStars.
- Upload JPG: When using online astrometry.net, upload all images are JPEGs to save bandwidth as FITS images can be large.
- Auto Park: Automatically park the mount after completing Polar Alignment Assistant Tools.
Warning: Turning Auto Park off might lead to inaccurate results.
Ekos selects and updates the optimal options by default to accelerate the performance of the solver. You may opt to change the options that are passed to the solver in case the default options are not sufficient.
- --no-fits2fits: This option should ONLY be checked if your astrometry.net version is 0.67 or earlier. Uncheck for any versions greater than 0.67.
- --resort: Check this option if your image does not have much nebulosity. If it does have strong nebulosity, uncheck it.
- --no-verify: This will prevent the solver from looking at an already existing WCS Header before blindly trying to solve the image. It is recommended to keep it checked.
- parity: Detect parity and reuse it to speed up solver.
- Use Scale: Set image scale to speed up solver as it does not have to search index files of different image scales.
- Low: The lower end of the imager scale, calculated as a little smaller than the shorter dimension of the image.
- High: The high end of the imager scale, calculated as a little bigger than the longer dimension of the image.
- Units: The units of the imager scale bounds above.
- dw: degree width
- aw: arcminute width
- app: arcsecs per pixel
- : Update Image Scale Bounds from the currently active camera and telescope combination.
- Auto Update: Automatically update image scale values when CCD and/or Mount parameters are updated.
- Down Sample: Downsample the image to shrink its size and speed up the solver.
- Auto: Automatically determine downsample value based on image size
- Use differential slewing instead of syncing: Do not use Sync when Slew to Target is selected. Use differential slewing to correct for discrepancies. This is useful on some mounts (e.g. Paramount).
- Use position: Set estimated position to speed up astrometry solver as it does not have to search in other areas of the sky.
- RA: The RA of the Estimated Telescope/Image Field Position in hh:mm:ss notation
- DEC: The DEC of the Estimated Telescope/Image Field Position in dd:mm:ss notation
- Radius: The Search Radius for the Estimated Telescope/Image Field Position in degrees.
- : Update coordinates to the current telescope position.
- Auto Update: Automatically update position coordinates when mount completes slewing.
- Custom: Additional optional astrometry.net options.
Capture & Solve
Using Ekos Alignment Module, aligning your mount using the controller's 1, 2, or 3 star alignment is not strictly necessary, though for some mounts it is recommended to perform a rough 1 or 2 star alignment before using Ekos alignment module. If you are using EQMod, you can start using Ekos alignment module right away. A typical workflow for GOTO alignment involves the following steps:
- Set your mount to its home position (usually the NCP for equatorial mounts)
- Select Slew to Target in the Solver Action.
- Slew to a nearby bright star.
- After slew is complete, click Capture & Solve
If the solver is successful, Ekos will sync and then slew to the star. The results are displayed in the Solution Results tab along with a bullseye diagram that shows the offset the reported telescope coordinates (i.e. where the telescope thinks it is looking at) vs. its actual position in the sky as determined by the solver.
Each time the solver is executed and returns successful results, Ekos can run on the following actions:
- Sync: Syncs the telescope coordinates to the solution coordinates.
- Slew to Target: Syncs the telescope coordinates to the solution coordinates and then slew to the target.
- Nothing: Just solve the image and display the solution coordinates.
Sometimes, the solver would fail to solve an image for various reasons. Here are some tips to get you started in the right direction:
- Do you have the correct index files installed for your FOV? By default StellarMate come preinstalled with index files 4206 to 4219, but if your FOV is on the narrower scale, you might need to install more index files.
- Do the RA/DE coordinates of the telescope in Alignment Module make sense? By default, the solver searches within 30 degrees of the current mount location. If the mount is way off in the sky, the solver would fail. If this happens, go back to your parking home position and then slew to a nearby star. If the star is off by more than 30 degrees, then there is something wrong with the mount, time, and location settings so check each of those.
- Check the quality of your image, does it have suffcient stars? Astrometry.net can work with minimal data, but if there is a lot of noise and very few stars, it might struggles to find a solution. Try increasing exposure time to compensate.
- Increase binning to the maximum supported by your camera.
- Increase exposure time to 10 seconds or more.
- Enable Dark Frame option to clean up the image before sending it to the solver.
- Perform rough Polar Alignment before using the alignment module.
- Automatic downsampling is turned on by default. It essentially reduces the size of your image before it is fed to the solver. For most users, this option improves solver efficiency. However, it can create issues for others. Go to Astrometry options and turn off automatic downsampling and if that doesn't work, try turning off downsampling completely.
Polar Alignment Assitant
When setting up a German Equatorial Mount (GEM) for imaging, a critical aspect of capturing long-exposure images is to ensure a proper polar alignment. A GEM mount has two axis: Right Ascension (RA) axis and Declination (DE) axis. Ideally, the RA axis should be aligned with the celestial sphere polar axis. A mount's job is to track the stars motion around the sky, from the moment they rise at the eastern horizon, all the way up across the median, and westward until they set.
In long exposure imaging, a camera is attached to the telescope where the image sensor captures incoming photons from a particular area in the sky. The incident photons have to strike the same photo-site over and over again if we are to gather clear and crisp image. Of course, actual photons do not behave in this way: optics, atmosphere, seeing quality all scatter and refract photons in one way or another. Furthermore, photons do not arrive uniformly but follow a Poisson distribution. For point-like sources like stars, a point spread function describes how photons are spatially distributed across the pixels. Nevertheless, the overall idea we want to keep the source photons hitting the same pixels. Otherwise, we might end up with an image plagued with various trail artifacts.
Since mounts are not perfect, they cannot perfectly keep track of object as it transits across the sky. This can stem from many factors, one of which is the mis-alignment of the mount's Right Ascension axis with respect to the celestial pole axis. Polar alignment removes one of the biggest sources of tracking errors in the mount, but other sources of error still play a factor. If properly aligned, some mounts can track an object for a few minutes with only deviation of 1-2 arcsec RMS.
However, unless you have a top of the line mount, then you'd probably want to use an autoguider to keep the same star locked in the same position over time. Despite all of this, if the axis of the mount is not properly aligned with the celestial pole, then even a mechanically-perfect mount would lose tracking with time. Tracking errors are proportional to the magnitude of the misalignment. It is therefore very important for long exposure imaging to get the mount polar aligned to reduce any residual errors as it spans across the sky.
Before starting the process, point the mount as close as possible to the celestial pole. If you are living in the Northern Hemisphere, point it as close as possible to Polaris.
The tool works by capturing and solving three images. After capturing each, the mount rotates by a fixed amount and another image is captured and solved.
After first capture, you can rotate the mount by a specific amount (default 30 degrees) either West or East. After selecting the magnitude and direction, click Next to continue and the mount will be rotated. Once rotation is complete you shall be asked to take another capture, unless you haved checked Auto Mode. In Automated mode, the rest of the process will continue with the same settings and direction until a total of three images are captured.
Since the mount's true RA/DE are resolved by astrometry, we can construct a unique circle from the three centers found in the astrometry solutions. The circle's center is where the mount rotates about (RA Axis) and ideally this point should coincide with the celestial pole. However, if there is a mis-alignment, then Ekos draws a correction vector. This correction vector can be placed anywhere in the image. Next, refresh the camera feed and make corrections to the mount's Altitude and Azimuth knobs until the star is located in the designated cross-hair. To make it easy to make corrections, expand the view by clicking on the Fullscreen button
If you are away from StellarMate or PC, you can use your Tablet to monitor the camera feed while making corrections. Use the StellarMate's web-based VNC viewer or use any VNC Client on your tablet to access StellarMate. If Ekos is running on your PC, you can use applications like TeamViewer to achieve the same results. The following is a video demonstrating how to utilize the Polar Alignment Assistant tool.
Legacy Polar Alignment Workflow
Using the Polar Alignment mode, Ekos can measure and correct for polar alignment errors. To measure Azimuth error, point your mount to a star close to the meridian. If you live in the northerm hemisphere, you will point the mount toward the southern meridian. Click on Measure Az Error to begin the process. Ekos will try to measure the drift between two images and calculates the error accordingly. You can ask Ekos to correct Azimuth error by clicking on Correct Az Error button. Ekos will slew to a new location and asks you to adjust the mount's azimuth knobs until the star is in the center of the Field of View. You can use the Focus Module's Framing feature to take a look at the image as you make your adjustments.
Similarly, to measure Altitude error, click on the Measure Alt Error button. You need to point your mount either east or west, and set the Altitude Direction combo box accordingly. Ekos will take two images and calculates the error. You can ask Ekos to correct Altitude error by clicking on the Correct Alt Error button. As with Azimuth correction, Ekos will slew to a new location and asks you to adjust the mount's altitude knobs until the star is in the center of the FOV.
After making a correction, it is recommended to measure the Azimuth and Altitude errors again and gauge the difference. You may need to perform the correction more than once to obtain optimal results.
Before starting the Polar Alignment tool, you must complete the GOTO Workflow above for at least one point in the sky. Once your mount is aligned, proceed with the following (assuming you live in the northern hemisphere):
- Slew to a bright star (4th magnitude or below) near the southern meridian (Azimuth 180). Make sure Slew to Target is selected. Capture and solve. The star should be exactly centered in your CCD field of view.
- Switch mode to Polar Alignment. Click Measure Az Error. It will ask you to slew to a star at the southern meridian which we already done, click continue. Ekos will now perform the error calculation.
- If all goes well, the error is displayed in the output boxes. To correct for the error, click Correct Az Error. Ekos will now slew to a different point in the sky, and you will be required to ONLY adjust the mount's azimuth knobs to center the star in the field of view. The most convenient way of monitoring the star field is by going to the Focus module and clicking Start Framing. If the azimuth error is great, the star might not be visible in the CCD field of view, and therefore you have to make blind adjustments (or simply look through the finderscope) until the star enters the CCD FOV.
- Begin your azimuth adjustments until the bright star you slewed to initially is as close to center as you can get it
- Stop Framing in the Focus module.
- Repeat the Measure Az Error to ensure we indeed corrected the error. You might have to run it more than once to ensure the results are valid.
- Switch mode to GOTO.
- Now slew to a bright star either on the eastern or western horizon, preferably above 20 degrees altitude. It has to be as close as possible to the eastern (90 azimuth) or western (270) cardinal points.
- After slew is complete, capture and solve. The star should be dead center in the CCD FOV now.
- Switch mode to Polar Alignment
- Click Measure Alt Error. It will ask you to slew to a star at either the eastern (Azimuth 90) or western (Azimuth 270) which we already done, click continue. Ekos will now perform the error calculation.
- To correct for the error, click Correct Alt Error. Ekos will now slew to a different point in the sky, and you will be required to ONLY adjust the mount's altitude knobs to center the star in the field of view. Start framing as done before in the focus module to help you with the centering.
- After centering is complete, stop framing.
- Repeat the Measure Alt Error to ensure we indeed corrected the error. You might have to run it more than once to ensure the results are valid.
- Polar alignment is now complete!
The mount may slew to a dangerous position and you might risk hitting the tripod and/or other equipment. Carefully monitor the mount's motion. Use at your own risk.
Ekos Scheduler is an indispensable arsenal in building your roboic observatory. A Robotic observatory is an observatory composed of several subsystems that are orchestrated together to achieve a set of scientific objectives without human intervention. It is the only Ekos module that does not require Ekos to be started as it is utlized to start and stop Ekos. It is designed to be straightforward and intuitive. However, the scheduler should only be used after you mastered Ekos and knows all the quirks of your equipment. Since the complete process is automated, including focus, guiding, and meridian flip. All equipment should be thoroughly used with Ekos and all their parameters and settings adjusted to achieve best result.
With Ekos, the user can utilize the powerful sequence queue to image batches of images for a particular target. In simple setups, the user is expected to focus the CCD, align the mount, frame the target, and start guiding before initiating the capture process. For more complex observatory environments, there are usually predefined custom procedures to be executed to prepare the observatory for imaging, and another set of procedures on shutdown. The user may plan to image one or more targets during the night, and expects data to be ready by morning. In KStars, tools such as the Observation Planner and What's up Tonight help the user in selecting candidates for imaging. After selecting the desired candidates, the user can add them to the Ekos Scheduler list for evaluation. The user may also add the targets directly in Ekos scheduler or select a FITS file of a previous image.
Ekos Scheduler provides a simple interface to aid the user in setting the conditions and constraints required for an observation job. Each observation job is composed of the following:
- Target name and coordinates: Select target from the Find Dialog or Add it from Observation Planner. You can also enter a custom name.
- Optional FITS file: If a FITS file is specified, the astrometry solver shall solve the file and use the central RA/DEC as the target coordinates.
- Sequence File: The sequence file is constructed in the Ekos Capture Module. It contains the number of images to capture, filters, temperature settings, prefixes, download directory..etc.
- Priority: Set job priority in the range of 1 to 20 where 1 designates the highest priority and 20 the lowest priority. Priority is applied in calculating the weight used to select the next target to image.
- Profile: Select which equipment profile to utilize when starting Ekos. If Ekos & INDI are already started and online, this selection is ignored.
- Steps: The user selects which Ekos modules should be utilized in the observation job execution workflow.
- Startup Conditions: Conditions that must be met before the observation job is started. Currently, the user may select to start as soon as possible Now, or when the target is near or past culmination, or at a specific time.
- Constraints: Constraints are conditions that must be met at all times during the observation job execution process. These include minimum target altitude, minimum moon separation, twilight observeration, and weather monitoring.
- Completion Conditions: Conditions that trigger completion of the observation job. The default selection is to simply mark the observation job as complete once the sequence process is complete. Additional conditions enable the user to repeat the sequence process indefinitely or up until a specific time.
You must select the Target and Sequence before you can add a job to the Scheduler. When the scheduler starts, it evaluates all jobs in accord to the conditions and constraints specified and attempts to select the best job to execute. Selection of the job depends on a simple heuristic algorithm that scores each job given the conditions and constraints, each of which is weighted accordingly. If two targets have identical conditions and constraints, usually the higher priority target followed by higher altitude target is selected for execution. If no candidates are available at the current time, the scheduler goes into sleep mode and wakes up when the next job is ready for execution.
The description above only tackles the Data Acquisition stage of the observatory workflow. The overall procedure typically utilized in an observatory can be summarized in three primary stages:
- Data Acquisition (including preprocessing and storage)
Startup procedure is unique to each observatory but may include:
- Turning on power to equipment
- Running safety/sanity checks
- Checking weather conditions
- Turning off light
- Fan/Light control
- Unparkig dome
- Unparking mount
Ekos Scheduler only initiates the startup procedure once the startup time for the first observation job is close (default lead time is 5 minutes before startup time). Once the startup procedure is completed successfully, the scheduler picks the observation job target and starts the sequence process. If a startup script is specified, it shall be executed first.
Depending the on the user selection, the typical workflow proceeds as following:
- Slew mount to target. If a FITS file was specified, it first solves the files and slew to the file coordinates.
- Auto-focus target. The autofocus process automatically selects the best star in the frame and runs the autofocus algorithm against it.
- Perform plate solving, sync mount, and slew to target coordinates.
- Perform post-alignment focusing since the frame might have moved during the plate solving process.
- Perform calibration and start auto-guiding: The calibration process automatically selects the best guide star, performs calibration, and starts the autoguide process.
- Load the sequence file in the Capture module and start the imaging process.
Once the observation job is completed successfully, the scheduler selects the next target. If the next target scheduled time is not due yet, the mount is parked until the target is ready. Furthermore, if the next scheduled target is not due for a user-configurable time limit, the scheduler performs a preemptive shutdown to preserve resources and performs the startup procedure again when the target is due.
If an unrecoverable error occurs, the observatory initiates shutdown procedure. If there is a shutdown script, it will be executed last.
The following video demonstrates an earilar version of the scheduler, but the basic principles still apply today:
Another critical feature of any remotely operated robotic observatory is weather monitoring. For weather updates, Ekos relies on the selected INDI weather driver to continuously monitor the weather conditions. For simplicity sake, the weather conditions can be summed in three states:
- Ok: Weather conditions are clear and optimal for imaging.
- Warning: Weather conditions are not clear, seeing is subpar, or partially obstructed and not suitable for imaging. Any further imaging process is suspended until weather improves. Warning weather status does not pose any danger to the observatory equipment so the observatory is kept operational. The exact behavior to take under Warninig status can be configured.
- Alert: Weather conditions are detrimental to the observatory safety and shutdown must be initiated as soon as possible.
Aborted Job Management
Define what should happen when a job steps into an error or aborts:
- Don't re-schedule (None): Don't restart the job in case of an error or an abort.
- Re-schedule after all terminated (Queue): If a job gets aborted, the scheduler will only re-schedule it if when all jobs are finished or aborted. If this is the case, the scheduler re-schedules all aborted jobs and sleeps for the given delay.
- Re-schedule immediately (Immediate): As soon as a job gets aborted, the scheduler will re-schedule it and waits the given delay.
If the option for re-scheduling errors is selected, errors are handled like aborts. Otherwise, jobs that step into an error are never re-scheduled.
Startup & Shutdown Scripts
Due to the uniqueness of each observatory, Ekos enables the user to select startup and shutdown scripts. The scripts takes care of any necessary procedures that must take place on startup and shutdown stages. On startup, Ekos executes the startup scripts and only proceeds to the remainder of the startup procedure (unpark dome/unpark mount) if the script completes successfully. Conversely, the shutdown procedure begins with parking the mount & dome before executing the shutdown script as the final procedure.
Startup and shutdown scripts can be written any language that can be executed on the local machine. It must return 0 to report success, any other exist value is considered an error indicator. The script's standard output is also directed to Ekos logger window. The following is as sample demo startup script in Python:
#!/usr/bin/env python # -*- coding: utf-8 -*- import os import time import sys print "Turning on observatory equipment..." sys.stdout.flush() time.sleep(5) print "Checking safety switches..." sys.stdout.flush() time.sleep(5) print "All systems are GO" sys.stdout.flush() exit(0)
The startup and shutdown scripts must be executable in order for Ekos to invoke them (e.g. use chmod +x startup_script.py to mark the script as executable). Ekos Scheduler enables truly simple robotic operation without the need of any human intervention in any step of the process. Without human presence, it becomes increasingly critical to gracefully recover from failures in any stage of the observation run. Using KDE notifications, the user can configure audible alarms and email notifications for the various events in the scheduler.
Manual Target Selection
When selecting a target usign the Ekos Find Tool, the objects equatorial coordinates (J2000) are automatically filled in the RA/DE fields. You can also define your own custom target. Simply type in your target name in the target field and then manually enter the desired J2000 coordinates in the respective fields.
KStars provides a conventient method to Copy Coordinates. Simply right-click on the desired object or point in the sky where you want to image, and click copy coordinates. You can paste the coordinates in any text editor and then copy back the J2000 coordinates in the scheduler RA and DE fields as shown below.
Hubble-like super wide field images of galaxies and nebulae are truly awe inspiring, and while it takes great skills to obtain such images and process them; many notable names in the field of astrophotography employ gear that is not vastly different from yours or mine. I emphasize vastly because some do indeed have impressive equipment and dedicated observatories worth tens of the thousands of dollars. Nevertheless, many amateurs can obtain stellar wide-field images by combining smaller images into a single grand mosaic.
We are often limited by our camera+telescope Field of View (FOV). By increasing FOV by means of a focal reducer or a shorter tube, we gain a larger sky coverage at the expense of spatial resolution. At the same time, many attractive wide-field targets span multiple FOVs across the sky. Without any changes to your astrophotography gear, it is possible to create a super mosaic image stitched together from several smaller images. There are two major steps to accomplish a super mosaic image:
- Capture multiple images spanning the target with some overlap between images. The overlap is necessary to enable the processing software from aligning and joining the sub-images.
- Process the images and stitch them into a super mosaic image.
The 2nd step is handled by image processing applications such as PixInsight, among others, and will not be the topic of discussion here. The first step can be accomplished in Ekos Scheduler where it creates a mosaic suitable for your equipment and in accordance to the desired field of view. Not only Ekos creates the mosaic panels for your target, but it also constructs the corresponding observatory jobs required to capture all the images. This greatly facilitates the logistics of capturing many images with different filters and calibration frames across a wide area of the sky.
Before starting the Mosaic Job Creator in Ekos Scheduler, you need to select a target and a sequence file. The Sequence File contains all the information necessary to capture an image including exposure time, filters, temperature setting...etc. Start the Mosaic Job Creator by clicking on the icon next to the Find button in Ekos Module.
On first use, you need to enter your equipment settings including your telescope focal length in addition to camera's width, height, and pixel dimensions. Finally, you need to enter the rotation of the camera with respect to north, or the position angle. If you don't know this value, start Ekos and slew to to your desired target then use the Align module to solve the image and obtain the position angle.
Next, enter the desired number of horizontal and vertical panels (e.g. 2x2, 3x3...etc) and then click Update. The target FOV shall be calculated given the number of panels and your camera's FOV and the mosaic overlap shall be displayed. By default, the percentage of the overlap among images is 5%, but you can change this value to your desired value. You can also move the complete mosaic structure around to fine tune the position of the mosaic panels. When satisfied, click Create Jobs and Ekos shall create an observation job and a corresponding customized sequence file for each panel. All the jobs shall be saved to an Ekos Scheduler List (.esl) file that you can load on any suitable observing night and it will pick off where you left. Before starting the Mosaic Job Creator, check that all the observation job conditions, constraints, and startup/shutdown procedures are as per your requirements since these settings shall be copied to all the jobs generated by the Mosaic tool.
With Ekos Scheduler, multi-night imaging is greatly facilitated and creating super mosaics has never been so easy.
Ekos Guide Module enables autoguiding capability using either the powerful built-in guider, or at your option, external guiding via PHD2 or ln_guider. Using the internal guiding, guider CCD frames are captured and sent to Ekos for analysis. Depending on the deviations of the guide star from its lock position, guiding pulses corrections are sent to your mount Via any device that supports ST4 ports. Alternatively, you may send the corrections to your mount directly, if supported by the mount driver. Most of the GUI options in the Guide Module are well documented so just hover your mouse over an item and a tooltip will popup with helpful information.
To perform guiding, you need to select a Guider CCD in Ekos Profile Setup. The telescope aperture and focal length must be set in the telescope driver. If the Guider CCD is attached to a separate Guide Scope, you must also set the Guide Scope's Focal Length and Aperture. You can set these values under the Options tab of the telescope driver or from the Mount module. Autoguiding is a two-step process: Calibration & Guiding.
During the two processes, you must set the following:
- Guider: Select the Guider CCD.
- Via: Selects which device receives the autoguiding correction pulses from Ekos. Usually guider CCDs have an ST4 port. If you are using the guider's ST4 to autoguide your telescope, set the guider driver in the Via combo box. The guider CCD will receive the correction pulses from Ekos and will relay them to the mount via the ST4 port. Alternatively, some telescopes support pulse commands and you can select the telescope to be receiver of the Ekos correction pulses.
- Exposure: CCD Exposure in seconds.
- Binning: CCD Binning.
- Box: Size of box enclosing the guide star. Select a suitable size that is neither too large or too small for the selected star.
- Effects: Specify filter to be applied to the image to enhance it.
Main Module Controls
Most of the main module controls are briefly explained in this section.
- Capture: Takes one capture
- Guide: Starts the guiding process
- Stop: Stops the guiding process
- Loop: Starts taking frames every n seconds (n = exposure value)
- Subframe: Subframe the image around the guide star. Or for PHD2, receive the Guide Star Image instead of the full image frame. For the Internal Guider, before checking this option, you must first capture an image and select a guide star. Uncheck it to take a full frame again.
- Auto Star: AutomaticControl
Capture: Takes one capture
Guide: Starts the guidally select the calibration star.
- Dark: Subtract dark frame. If no dark frame is available, a new dark frame shall be captured and saved for future use.
- Show in FITS Viewer : Shows frame in FITS Viewer
- Clear calibration data : Clears all the calibration data for the guiding process.
- Manual Dither : Allows manual dithering.
- Guider: Select active Guiding Camera.
- Via: Select which device receives the guiding correction commands.
- Exp: Exposure time in seconds.
- Bin: Guide camera binning. It is recommended to set binning to 2x2 or higher.
- Box: Guide star tracking box size. Box size must be set in accordance to the selected star size.
- Effects: Apply filter to image after capture to enhance it.
- Directions: Shows the values of RA and DEC.
- RA: Guide Right Ascention Axis
- +: East Direction Guiding
- -: West Direction Guiding
- DEC: Guide Declination Axis
- +: North Direction Guiding
- -: South Direction Guiding
- RA: Guide Right Ascention Axis
- Swap: Swap DEC direction pulses. This value is determined automatically from the calibration procedure, only override if necessary.
- Connect: Connect to external guiding application.
- Disconnect: Disconnect from external guiding application.
- Status Bar: Displays the status of the guiding process
- Scope: Select which telescope to use when performing Field of View calculations.
- Guiding rate: Mount guiding rate (x15"/sec). Find out the guiding rate used by your mount and update the value here to get the recommended value of proportional gain suitable for your mount. Setting this value does not change your mount guiding rate.
- P: Recommended proportional rate given the selected guiding rate.
- Focal length: Guide camera focal length. Unit is in millimeters (mm)
- Aperture: Guide camera aperture. Unit is in millimeters (mm)
- F/D: Focal ratio
- FOV: Field of view (arcmin)
- Guiding Delta ": Immediate Guiding RA deviation in arcseconds and Immediate Guiding DEC deviation in arcseconds respectively.
- Pulse Length (ms): Generated RA pulse and Generated DEC pulse respectively.
- RA RMS": RA Guiding RMS error.
- DE RMS": DEC Guiding RMS error.
- Total RMS": Total Guiding RMS error.
- Guide SNR: Guide Signal-to-noise ratio.
Dark frames are immensly helpful in reducing noises in your guide frames. It is highly recommended to take dark frames before you begin and calibration or guiding procedure. To take a dark frame, check the Dark checkbox and then click Capture. For the first time this is performed, Ekos will ask you about your camera shutter. If your camera does not have a shutter, then Ekos will warn you anytime you take a dark frame to cover your camera/telescope before proceeding with the capture. On the other hand, if the camera already includes a shutter, then Ekos will directly proceeds with taking the dark frame. All dark frames are automatically saved to Ekos Dark Frame Library. By default, the Dark Library keeps reusing dark frames for 30 days after which it will capture new dark frames. This value is configurable and can be adjusted in Ekos settings in the KStars settings dialog.
It is recommended to take dark frames covering several binning and exposure values so that they may be reused transparently by Ekos whenever needed.
In the calibration phase, you need to capture an image, select a guide star, and click Guide to begin the calibration process. If calibration was already completed successfully before, then the autoguiding process shall begin immediately, otherwise it would start the calibration process. If Auto Star is checked, then you are only required to click capture and Ekos will automatically select the best fit guide star in the image and continues the calibration process automatically. If Auto Calibration is disabled, Ekos will try to automatically highlight the best guide star in the field. You need to confirm or change the selection before you can start the calibration process. The calibration options are:
- Pulse: The duration of pulses in milliseconds to be sent to the mount. This value should be large enough to cause a noticable movement in the guide star. If you increase the value and you do not notice any motion of the guide star, then this suggests possible mount issues such as jamming or connection issues via the ST4 cable.
- Two axis: Check if you want the calibration process calibration in both RA & DEC. If unchecked, the calibration is only performed in RA.
- Auto Star: If checked, Ekos will attempt to select the best guide star in the frame and begins the calibration process automatically.
The reticle position is the guide star position selected by you (or by the auto selection) in the captured guider image. You should select a star that is not close to the edge. If the image is not clear, you may select different Effects to enhance it.
Ekos begins the calibration process by sending pulses to move the mount in RA and DEC. If the calibration process fails due to short drift, try increasing the pulse duration. To clear calibration, click the trash-bin icon next to Guide button.
Calibration can fail for a variety of reasons. To improve chances of success, try the tips below.
- Better Polar Alignment: This is critical to the success of any astrophotography session. Perform a quick polar alignment with a polar scope (if available) or by using Ekos Polar Alignment procedure in the Align module.
- Set binning to 2x2: Binning improves SNR and is often very important to the success of the calibration and guiding procedures.
- Prefer use ST4 cable between guide-camera and mount over using mount pulse commands.
- Select different filter (e.g. High contrast) and see if that makes a difference to bring down the noise.
- Smaller Square Size.
- Take dark frames to reduce noise.
- Play with DEC Proportional Gain or disable DEC control completely and see the difference.
- Leave algorithm to default value (Smart)
Once the calibration process is completed successfully, the guiding shall beging automatically hereafter. The guiding performance is displayed in the Drift Graphics region where Green reflects deviations in RA and Blue deviations in DEC. The colors of the RA/DE lines can be changed in KStars color scheme in KStars settings dialog. The vertical axis denotes the deviation in arcsecs from the guide star central position and the horizontal axis denotes time. You can hover over the line to get the exact deviation at this particular point in time. Furthermore, you can also zoom and drag/pan the graph to inspect a specific region of the graph.
Ekos can utilize multiple algorithms to determine the center of mass of the guide star. By default, the smart algorithm is suited best for most situation. The fast algorithm is based on HFR calculations. You can try switching guiding algorithms if Ekos cannot keep of the guide star within the guiding square properly.
The info region displays information on the telescope & FOV, in addition to the deviations from the guide star along with the correction pulses sent to the mount. The RMS value for each axis is displayed along with the total RMS value in arcsecs. The internal guider employs PID controller to correct the mount tracking. Currently, the only the propotional and integral gains are utilized within the algorithm, so adjusting it should affect the length of the generated pulses sent to the mount in milliseconds.
To enable automatic dithering between frames, make sure to check the Dither checkbox. By default, Ekos should dither (i.e. move) the guiding box by up to 3 pixels after each frame captured in Ekos Capture Module. The motion duration and direction are randomized. Since the guiding performance can oscillate immediately after dithering, you can set the appropriate Settle duration to wait after dither is complete before resuming the capture process. In rare cases where the dithering process can get stuck in an endless loop, set the appropriate Timeout to abort the process. But even if dithering fails, you can select whether this failure should terminate the autoguiding process or not. Toggle Dither Failure Aborts Autoguide to select the desired behavior.
Non-guide dithering is also supported. This is useful when no guide camera is available or when performing short exposures. In this case, the mount can be commanded to dither in a random direction for up to the pulse specified in the Non-Guide Dither Pulse option.
Ekos supports multiple guiding methods: Internal, PHD2, and LinGuider. You need to select the desired guider in your Ekos equipment profile:
- Internal Guider: Use Ekos internal guider. This is the default and recommened option.
- PHD2: Use PHD2 as the external guider. If selected, specify the host and port of the PHD2. Leave to default values if Ekos and PHD2 are running on the same machine.
- LinGuider: Use LinGuider as the external guider. If selected, specify the host and port of the LinGuider. Leave to default values if Ekos and LinGuider are running on the same machine.
GPG RA Guider
Ekos also supports GPG RA Guider, but this is for RA only--that is, guiding for DEC still happens, but using the existing guiding algorithms. This guider can be enabled by going to the Guide Module, clicking on Options (bottom-right) and then clicking on the GPG RA Guider tab and then checking the Enable GPG checkbox. This guider is based on the work in this PhD thesis and is the same as the well-regarded PHD2 guide algorithm known as Predictive PEC. It estimates the periodic error in the guiding system, and tries to fix it before it happens. This system should perform about the same as the standard guider for the first period or two of your mount's periodic error, then improve. When using this system, it's best to set in advance what your mount's worm-gear period is. For example, the Orion Atlas pro is about 480s. You enable this in the Guide options menu, in the GPG RA tab, and then checking "Enable GPG". There are other parameters you can change, but as indicated earlier, the main one to think about is "Major Period".
It can be used with all Guide star-detection algorithms but has been tested most and is recommended with SEP MultiStar. It combines a reactive correction whose aggressiveness is controlled with Control Gain and Minimum Move, with a predictive correction controlled by Prediction Gain. Again, The most important parameter is Major Period. If you can determine it for your mount, it's much
better to set it yourself and uncheck Estimate Period.
- Enable GPG: Toggles GPG RA Guiding.
- Major Period: The length in seconds of the mount's major period (that's being corrected).
- Estimate Period: If checked, the GPG estimates the mount's major period. Otherwise, it uses the entry above.
- Prediction Gain: The fraction of its prediction the GPG uses to move the mount.
- Control Gain: The fraction of the guide-star drift that the GPG uses to move the mount.
- Minimum Move: The min-move parameter the GPG uses to move the mount when it uses its backoff proportional guider.
- Long-range Length Scale: Length scale of the long range kernel.
- Long-range Variance: Long-range kernel signal variance
- Periodic Length Scale: Periodic Kernel length scale
- Periodic Variance: Periodic kernel signal variance
- Short-range Length Scale: Length scale of the short-range kernel
- Short-range Variance: Short-range kernel signal variance
- Approximation Points: Number of points used in the Gaussian Process approximation
- Num Periods for Inference: The min number of periods that must be sampled before prediction is fully used. Before that, it is mixed with the control/proportional guider.
- Num Periods for Period Estimate: The min number of periods that must be sampled before GPG fully estimates the period.
Guiding Direction Control
You can fine tune the guiding performance in the Control Section. The autoguide process works like a PID controller when sending correction commands to the mount. You can alter the Proportional and Integral gains to improve the guiding performance if necessary. By default, guiding corrective pulses are sent to both mount axis in all directions: positive and negative. You can fine-tune control by selecting which axis shall receive corrective guiding pulses and within each axis, you can indicate which direction (Positive) + or Negative (-) recieves the guiding pulses. For example, for Declination axis, the + direction is North and - is South.
Each mount has a particular guiding rate in (x15"/sec) and usually ranges from 0.1x, to 1.0x with 0.5x being a common value used by many mounts. The default guiding rate is 0.5x sidereal, which is equivalent to a proportional gain of 133.33. Therefore, set the guiding rate value to whatever value used by your mount, and Ekos shall display the recommended propotional gain value that you may set in the propotationl gain field under the Control Parameters. Setting this value does not change your mount guiding rate! You must change your mount guiding rate either via the INDI driver, if supported, or via the hand controller.
The drift graphics is a very useful tool to monitor the guiding performance. It is a 2D plot of guiding deviations and corrections. By default, only the guiding deviations in RA and DE are displayed. The horizontal axis is the time in seconds since the autoguiding process was started while the vertical axis plots the guiding drift/deviation in arcsecs for each axis. Guiding corrections (pulses) can also be plotted in the same graph and you can enable them by checking the Corr checkbox below each Axis. The corrections are plotted as shaded areas in the background with the same color as that of the axis.
You can pan and zoom the plot, and when hovering the mouse over the graph, a tooltip is displayed containing information about this specific point in time. It contains the guiding drift and any corrections made, in addition to the local time this even was recorded. A vertical slider to the right of the image can be used to adjust the height of the secondary Y-axis for pulses corrections.
The Trace horizontal slider at the bottom can be used to scroll through the guide history. Alternatively, you can click the Max checkbox to lock the graph onto the latest point so that the drift graphics autoscrolls. The buttons to the right of the slider are used for autoscaling the graphs, exporting the guide data to a CSV file, clearing all the guide data, and for scaling the target in the Drift Plot. Furthermore, the guide graph includes a label to indicate when a dither occurred so the user knows guiding was not bad at those points.
The colors of each axis can be customized in KStars Settings color scheme.
A bulls-eye scatter plot can be used to gauge the accuracy of the overall guiding performance. It is composed of three concentric rings of varying radiuses with the central green ring having a default radius of 2 arcsecs. The last RMS value is plotted as with its color reflecting which concentric ring it falls within. You can change the radius of the inner most green circle by adjusting the drift plot accuracy.
The Calibration Plot shows the mount positions recorded during internal-guider calibration.
Basically, if things are going well, it should display dots in two lines which are at right angles to each other--one when the calibration pushes the mount back and forth along the RA direction, and then when it does the same for the DEC direction. Not a ton of info, but can be useful to see. If the two lines are at a 30-degree angle, something's not going well with your calibration! Here's a picture of it in action using the simulator.
The colored dots (same color scheme as the internal guider) shows the RA and DEC samples on their way out, and the small white and yellow circles show their return paths.
You can opt to select external PHD2 application to perform guiding instead of the built-in guider.
If PHD2 is selected, the Connect and Disconnect buttons are enabled to allow you to establish connection with the PHD2 server. You can control PHD2 exposure and DEC guide settings. When clicking Guide, PHD2 should perform all the required actions to start the guiding process. PHD2 must be started and configured before Ekos.
After launching PHD2, select your INDI equipment and set their options. From Ekos, connect to PHD2 by clicking Connect button. On startup, Ekos will attempt to automatically connect to PHD2. Once connection is established, you may begin the guiding immediately by click on the Guide button. PHD2 shall perform calibration if necessary. If dithering is selected, PHD2 shall be commanded to dither given the offset pixels indicated and once guiding is settled and stable, the capture process in Ekos shall resume.
Ekos saves a CSV guide log data that can be useful for analysis of the mount's performance under ~/.local/share/kstars/guide_log.txt. This log is only available when using the built-in guider.