Awsome, it works! But i had to use this syntax:

Amazing as long as you work with commandline instructions. But what with ekos in Kstars?
Is it right that under ekos options you connect to a remote server being on localhost? Is ekos then launching a second indiserver on the local machine connecting to the one launched with a commandline instruction? Or is it just connecting as a client to the local commandline launched server?
I would avoid multiple indiservers passing data to each other even running on the local machine. Doesn't seem efficient to me.

I'm writing a tutorial on this topic now, so hopefully it should clear up any issues.

If you have a camera located remotely on a 'pig slow' network, ie, a wifi link, and multiple clients taking the same data, then it's more efficient to use a local server chained to the remote server. Using my example, for a year my all-sky camera was on the other end of a wifi link, and two clients taking the images from it. If both clients connect directly to the remote server, then two copies of each image are sent over wifi. But with a local server daisy chained to the remote end, then only one copy of the image is sent over the wifi link, and the local server sends one copy to each local client.

What is most efficient really depends on the rest of what is happening, and no one size fits all in this case.

Is there a way to put a chained server into a self-sustained mount driver? I like to use a mount driver on another remote indiserver by just selecting it like any other local mount driver. How would I do this?

You can connect to a remote indi driver running on another server by entering it's details as a remote driver in the space below the local driver selections in the profile manager.

Hi. Thank you. Yes. That works with EKOS.

I want to use chained indiservers in the ASIAIR. I don’t know how to connect to another indiserver in that case. The idea is to „fool“ the ASIAIR with a local INDI driver to connect to the remote driver and server.

ASIAIR is probably too restricted to permit that.

Well, coming back to the original question... All I need is an indi driver that connects to a remote indi server + driver rather than a local indi driver/mount. Like a make-believe driver to the local indiserver. Similar to the SkySafari driver... This sounds to me like an indi question, rather than an issue with the ASIAIR.

Hi,
I know it's an old topic but still hot from my perspective.
I know Jasems Tutorial on chained servers and it works well for me.
But my question is, is ti possible to run two indiservers on one system on different ports? I can not make that happen. The only way I have found is to run a users indiserver and another in a systemwide context. like:
systemctl --user enable indiserver.service (on port 7624)
sudo systemctl --system enable indiserver.service (on port 7634)

What I like to accomplish is more like:
sudo systemctl --system enable indiserver.service (on port 7624 and 7634)

What is wrong?

I'm not sure what you intend to do exactly.
As for your question, you can start indiserver with the "-p yourport" parameter.

I think you need to start the second indiserver from another user or both will start with the datas from the same .indi folder which is probably not what you want ?.

- Marc

Hi Marc,

I intend to use 3 cameras with Kstars/Ekos but only one imaging and one giuding camera are supported. The third one I intend to use shall observ the sky in the direction ob main OTA. I call it a cloud camera.
The idea is to start an indiserver with all the major equipment for regular observations and secondly start another indiserver on the same hardware (RPi) with a different port. This will not work. Ofcourse I know the few options of indiserver as the port option.
When I start just one server with all equipment plus the QHY "Cloudcam" and than try to use this device (indi_qhy_ccd) from a second instance of Kstars. It doesn't work eigther.
How would you approach this problem?