As I have requested in the forum before, there is a contradiction in how to start the Ekos driver.

With this update, if the remote server has a custom driver, it can no longer be started. (This is because Ekos owns and displays the XML file that should be received from the server.)

It may also crash when launching the driver in INDI Web Manager.
(My blog has a current solution.)

tstudioastronomy.blog.fc2.com/blog-entry-442.html

How to boot the driver in Ekos has long been the cause of the problem.

How to always start the server and send all the xml files of the drivers owned by the server to the client (previous suggestion).
Alternatively, I hope to change to a method that sets driver startup and driver connection separately.

Read More...