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.
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.)
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.
Thank you for your wonderful work.
If you have an altazimuth mount simulation driver, you can use Solver to support the introduction of the Dobsonian telescope.
Please consider adding it.
This driver is often buggy.
There was a bug in this update as well, but I was able to work around it by following the steps on the blog.
There are two points.
1. Do not connect automatically (set without connecting to the device)
2. In the driver control panel, delete only the setting name part and set. (Enter the aperture and focal length.)
The operation of the purge button → default button explained in the blog is also performed without connecting to the device.
Yes, I understand that you are a user.
I have been using INDI for 4 years.
The evolution in the meantime was amazing.
However, I also feel that there are improvements due to repeated updates.
I have a lot of information and distributions about INDI on my blog.
The blog also mentions notes about INDI, so please have a look if you have time.
Thank you for your reply.
Indi is a very nice environment, but I would like you to consider the compatibility of the initial setting file when reviewing the driver setting items and updating.
Even though the function does not change, items related to parks and domes are added to the driver and it does not work, or the initial settings are not read and problems often occur.
The driver for NanoPiM4 (Armbian: Arm64, Bionic) has been updated, so I expected it and updated it.
KStars crashes when I connect the driver. The system is also malfunctioning and requires a reboot.
It was a disappointing result.
Attach the log.
After changing the source, it seems that the apt update is not available. ....
I am looking forward to an early update of the driver. (Not updated yet)
The joystick can only be used on server-side machines.
I think it would be convenient if the joystick could be used with the Ekos mount controller....
I posted a request long ago.
Ekos category that do not save images (preview, focus processing, PlateSolving, etc.), it is more comfortable to switch to the process of cropping frames in stream mode (the image displayed in live video in Ekos).
It would be even better if an option was added to easily change the pixel size of the streaming.
I think it's wonderful.
It would be better if the focus could be operated in the same way.
Thank you for information.
I think that many of the causes of troubles, including this driver, are due to insufficient implementation and initial settings of the park function.
I feel that this mount does not require the Park function.