×

INDI Library v2.0.1 Released (06 Apr 2023)

Bi-monthly release with major changes to INDI properties and client API in addition to new drivers and improvements. An important feature for this release is the full support for XISF file format which is used by PixInsight. INDI cameras can now natively capture in XISF format.

Read More...

Hope to improve the driver startup method in Ekos

  • Posts: 446
  • Thank you received: 29

Hope to improve the driver startup method in Ekos was created by T-Studio

 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.
1 year 10 months ago #73215

Please Log in or Create an account to join the conversation.

  • Posts: 446
  • Thank you received: 29

Replied by T-Studio on topic Hope to improve the driver startup method in Ekos

By the way, CCD Ciel is the following procedure.

1. Enter the IP address of the remote server to connect to → Connect
2. Display the list of drivers running on the remote server → select

The correct rule.
With this style, you can connect with a custom driver on the remote server without any problems.
1 year 10 months ago #73216

Please Log in or Create an account to join the conversation.

Time to create page: 0.127 seconds