Can you make ekos connect to mutipe INDI servers running different gear sets? i.e one server has mount, guider and focuser and another has imaging ccd.
Kstars has this ability allready in device manager but not in Ekos?
You can chain the indiserver as you indiserver is a kind of device.
Have look with "indiserver --help"
As example with simulator you can do:
On first indiserver instance (As example 192.168.125.10) lunch the server with it requested drivers For example :<<indiserver -v indi_simulator_telescope>> It would run one instance connected to the telescope
On the second server you lunch it with <<indiserver -v "Telescope Simulator"@192.168.125.10 indi_simulator_focus>> It would connect the the first server and to the local fosuser.
-> "Telescope Simulator" is the name from the GetDefaultName() function. This is the name of the device you use when configure EKOS to work remote instead of local in KStars configuration.
Then you can connect via EKOs, or throuhg the device mannager (Ctrl-D) to the last indi server.
That's it. Regards
Skywatcher HEQ5, Televue 101-IS, Takahashi FS-60CB
Focus Boss II with OptecInc TCF-S focuser and Starlight Instruments HSM20 handy stepper motor
Guiding camera ZWO ASI120MM
Filterwheel OptecInc IFW
Camera not set yet
Do I understand this rightly? Could I start on my kstars machine an indiserver that connects only eqmod and ghoto ccd and then start another one on my raspi that only uses the focuser but also includes the kstars machine and then I connect ekos to the raspi and I should get eqmod gphoto and fokuser accessible? (sorry for the many and's) This would solve A LOT of my problems.
--= human, without Windows™ =--
pls excuse my bad english!
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.
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.
INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
Waveshare Stepper Motor Board - DIY Focuser
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.