The client/server architecture of INDI/KStars/Ekos allows for a lot of flexibility to adjust to your specific situation. I have mostly used it with on-telescope server and run the client remotely on Mac. But to eliminate download times (wasted observation time), I recently switched to running all local and screen-share into it.
Whichever solution you choose a solid WiFi network is very important. I have found the Pi hotspot to be too weak for my situation, and have mostly used a dedicated non internet-connected router, strategically placed relative to the telescope. Now working on extending the regular home network with a mesh-repeater to extend coverage in garden.
You may want to check the frequency your Pi started using. If it switched to 2.4GHz, this is well known to interact with USB3 leading to all sorts of erratic behavior. Best is to force your Pi to use the 5GHz band. You may want to try and see if this solves your issues.


Sent from my iPad using Tapatalk

Read More...