Is there a particular reason you run kstars on the RPi?

I'm very happy with Astroberry 2 perfomance on RPi 4 with 4 GB RAM. The builtin wifi is too slow for anything but simple management.
I would not run kstars on the RPI for performance reasons, and definately not if using the builtin wifi.

Running kstars on a Windows laptop with cabled Ethernet to the indi server on the RPi4. This way I have very snappy response when imaging, and better color reproduction in the kstars fits viewer than if using VNC.
When guiding with the builtin guider from windows, the lag with wifi is unacceptable and guiding becomes very erratic. Running phd2 locally on the RPi 4 solves this. The Ekos guider via Ethernet cable is also fine.
The FITS download times I get on Wifi (10m from wifi router, one wall) is 6-7 sec / FITS. With Ethernet it's 1 sec / FITS.
I didn't want to connect a USB WiFI to the RPi4 as I'm afraid it wil interfere with camera USB traffic.

Equipment:
RPI 4 / 4 GB / 125 GB fast SD card / astroberry 2.0.1. All latest updates (sudo apt update; sudo apt full-upgrade)
Skywatcher Az GTi, with EQMOD USB cable (Not using built-in wifi)
ZWO ASI294MC with DIY cooling
ZWO ASI120MM Mini
Astrocat 250 mm
30mm F4 miniscope
Dew heaters
Ethernet cable

I just keep everything setup and ready to go. After poweron I connect kstars from my laptop and start the polar alignment in ekos. For simplicity, I tend to use the builtin guider rather than phd2.

Read More...