Ekos thinks that it is a very excellent integrated environment in capturing an astronomical object.
Regarding the requirement of function, it has been described before.
www.indilib.org/forum/wish-list/2665-feature-request.html
indilib.org/forum/wish-list/2792-request...acking-function.html
It is wonderful that you can schedule everything automatically and operate it, but if it is not reliable with the driver you will be in trouble.
Currently I will describe the items that will cause problems in automating on schedule in my environment.
The driver you are using is as follows.
· Mount driver
CerestronGPS, SkyWatcher Alt-Az, Digital Setting circles
· Focus driver
moonlite, FCUSB
· CCD driver
QHY CCD, SX CCD, ZWO CCD, Canon DSLR
· Other drivers
GPSD, SkySafari
We use these drivers according to the usage environment.
1. Park setting
As mentioned above, since there is only one setting file and only the absolute position is recorded, it is not functioning properly with the mount driver which does not have the parking function. My mountain has become extinct.
Since it will be the command used to start and stop automation on schedule, I think that it is necessary to reliably function with any mount driver.
In digital setting, circle park is unnecessary from the purpose of mounting. Rather, I would like to use only the mount driver. (Ekos can not be used unless you add drivers for cameras that are not currently in use.)
2. Solver Options
Depending on the mount driver, the current location of the mount may not be reflected in the configuration file, causing a solver error.
-O - no - plot - no - verify --resort --downsample 2 -3 ooooo -4 xxxxx -5 30
(The part of ooooo, xxxxx will not be reflected in the mount's current location.)
3. Synchronization with GPS
In the current Ekos setting, it is synchronized with Kstars. It is not reflected in the mount. (After synchronizing with Kstars and GPS, it will not take effect until switching from Kstars to all drivers to synchronous setting.
Items other than Park are handled manually, but they are subject to the influence of automation in the attractive remote location of Ecos.
I think it is important to further improve the consistency of these drivers and Ekos.
Postscript
I switched all environments from Windows + Ascom to INDI + Ekos.
There are some operational precautions.
However, flexible integration control of the driver, Ekos is an attraction not seen in other environments.