Ekos can be accessed from the Tools menu in KStars.

 Ekos Setup

  1. Select INDI Mode: You can start Ekos either locally or remotely. Local mode is when Ekos is running in the same machine as INDI server, i.e. all the devices are connected directly to the machine. If you run INDI server on a remote machine (for example, on a Rasperry PI), you need to set the INDI server host, port, and device names in Options.
  2. Select Devices: If you are running Ekos in Local mode, select the devices you wish to connect to here. In remote mode, you can select the devices from the list. Additionally, if the driver is only available on the remote machine, you can set all the remote devices names in Options and the names shall be used accordingly. Please note that if you have a CCD with a guide head, you can leave the guider dropdown menu blank as Ekos will auto-detect the guide head from the CCD camera. Similarly, if your CCD includes embedded filter wheel support, then you do not need to specify the filter wheel device in the filter dropdown menu.
  3. Start & Stop INDI: Start and Stop INDI services. Once INDI server is established, INDI Control Panel will be displayed. Here you can change some driver options such as which port the device is connected to ...etc.
  4. Connect & Disconnect Devices: Connect to INDI server. Based on the devices connected, Ekos modules (CCD, Focus, Guide...etc) will be established and available to use.

 Ekos Options

 Remote Settings

To use Ekos in remote mode, you need to start INDI server on a remote host and configure Ekos to connect to it via the following settings:
  1. Host: Host name or IP address of the remote INDI server
  2. Port: Port of the remote INDI server.
  3. Remote Devices Names: Names of the devices started on the remote INDI server. The device name is the name you get in the INDI Control Panel when connecting to the device. Unless the driver is missing in your local Ekos installation (e.g. a custom INDI driver on a remote headless server), you do not need to manually specify any drivers names here. Just select the devices from the dropdown list in the setup tab.

Tip: You can obtain the device names by running INDI server with the verbose flag. indiserver -vv driver_executable


All INDI drivers supports loading and saving of INDI properties. For example, if you use a telescope driver, you can set your telescope aperture and focal length, and then save the configuration (under the Options tab) so it can be retrieved in a future session. The configuration option decides how to load the configuration file for INDI drivers:
  1. Never: Never load any configuration. The configuration can still be loaded manually in the INDI control panel.
  2. On Connection: Automatically load the driver's configuration on connection.
  3. Always Load Default: Always load default configuration, if it exists


Set Scheduler Module options:

  • Lead Time: Lead time is the minimum time in minutes between jobs. The scheduler starts execution of a job before its scheduled start-up time by this lead time. Early execution is useful as focusing, alignment, and guiding procedures may take prolonged periods to time to complete.
  • Pre-Dawn: Do not permit jobs to be scheduled or executed past this many minutes before dawn.
  • Pre-Emptive Shutdown: In case no scheduler job is scheduled for this many hours, perform a complete shutdown procedure and restart observatory operations once the next job is ready.


Set Capture Module options:

  • Temperature Threshold: Maximum acceptable difference between requested and measured temperature set point. When the temperature threshold is below this value, the temperature set point request is deemed successful.
  • Remember Job Progress: When starting a new capture job, check if files were previously captured and resume capture afterwards.


Ekos can utilize both astrometry.net online and offline solvers.
  1. solver: Path to astrometry.net solver binary. You only need to specify this settings if you are using the offline astrometry.net solver.
  2. wcsinfo: Path to astrometry.net wcsinfo binary. You only need to specify this settings if you are using the offline astrometry.net solver.
  3. config: Path to astrometry.net configuration file. You only need to specify this settings if you are using the offline astrometry.net solver.
  4. API Key: API Key to utilize astrometry.net online solver. You only need to specify this settings if you are using the online astrometry.net solver. You can obtain your own API key if you register in the astrometry.net site
  5. API URL: URL to the Astrometry.net API site. You only need to specify this settings if you are using the online astrometry.net solver.
  6. Use JPG: Convert captured FITS image to JPEG before uploading to astrometry.net to conserve bandwidth.


3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!