I don't know if this has been discussed in the past, but would it be possible to separate guiding from the rest of Ekos so the guider could run on a separate machine. In my setup Indiserver runs on a Rpi on the mount, while Kstars/Ekos run indoors on my Mac. The problem is that guide images need to come from the Rpi to my Mac. With multistar guiding it would be difficult to limit the amount of data transferred. So, a lot of data transferred during an imaging session is guiding related, which I suspect is responsible for comms related issues in my setup. There is also the delay to guiding whilst the most recent guiding image is transferred; which encourages me to lower the guiding interval to compensate (which probably makes the issue worse).

(I'm aware this can be done with PHD2 but would prefer to use the internal guider).

For most convenience the guiding gui would still be part of the Ekos gui, just the processing engine would need to run a server process deployable to another machine.

I've seen a few posts on IndiHub recently; this could be a good addition for this product.

Read More...