Ekos can be accessed from the Tools menu in KStars.
- 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.
- Select Devices: If you are running Ekos in Local mode, select the devices you wish to connect to here. In remote mode, the devices will be filled automatically from the device names you defined earilar in Options. 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.
- 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.
- 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.
Remote SettingsTo 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:
- Host: Host name or IP address of the remote INDI server
- Port: Port of the remote INDI server.
- 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. It is usually the same name as the driver, but it can differ. For example, the driver "QSI CCD" will only provide one device with name "QSI CCD". However, the "SX CCD" (Starlight Xpress driver) will change the device name depending on the actual device connected, for example "SX CCD LodeStar", and it is this device name that must be configured in Ekos.
Tip: You can obtain the device names by running INDI server with the verbose flag.
indiserver -vv driver_executable
ConfigurationAll 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:
- Never: Never load any configuration. The configuration can still be loaded manually in the INDI control panel.
- On Connection: Automatically load the driver's configuration on connection.
- Always Load Default: Always load default configuration, if it exists
Audible AlarmsEnables and disables audio alarms for Ekos. You can enable or disable the alarms per module. There are two alarms (Ok and Error) that are triggered when the process either results in success or failure.
Astrometry.netEkos can utilize both astrometry.net online and offline solvers.
- solver: Path to astrometry.net solver binary. You only need to specify this settings if you are using the offline astrometry.net solver.
- wcsinfo: Path to astrometry.net wcsinfo binary. You only need to specify this settings if you are using the offline astrometry.net solver.
- config: Path to astrometry.net configuration file. You only need to specify this settings if you are using the offline astrometry.net solver.
- 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
- 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.