- Messages
- 572
- Reaction score
- 102
This thread is for the general discussion of the Guide Orange Pi 3 LTS with EKOS/INDI/KStars. Please add to the discussion here.
I wouldn't personally go below the Orange Pi3 at the cost. Start KStars & INDI/EKOS on the Orange Pi, but then connect to it via a remote KStars setup. Simply running KStars on the Orange Pi isn't going to use that much resources, and the main work (captures, etc) will be on the computer running KStars and connecting remotely. It will use a slight bit of memory for KStars, but since no processing is being done via KStars, it's fairly fixed. All the plate solving and such will be on whatever computer you are using to connect to INDI/EKOS with.Hi Tracy, total Linux newbie here but I was proficient in DOS back in the day. I just received my Orange Pi 3 LTS a few days ago and I'm going to give this a try. How do we set up an Indi Server only with the client software running on a remote PC? Do you think an Orange Pi Zero 2 would handle that ?
vncserver :1
?vncpasswd
vncserver :1
under the orangepi user, are you able to connect to it via a VNC client?user
from vnc to orangepi in the /lib/systemd/system/tightvncserver.service
.sudo
users group bygpasswd -a orangepi sudo
.orangepi
user to the sudo group, changed the user name in the service file (forgot I had actually created a VNC user on the old install) to orangepi
and rebooted it seems to work. I have added that into the instructions.Great. Thanks for helping troubleshooting that issue. One thing you will find is that the Pi3 takes longer on plate syncing than the RPi 4 does, and the 2GB of RAM can get full pretty quick, but for the price it is a nice solution. The new Orange Pi5 resolved much of that, but it’s getting into the RPi 4 price range when you get it WiFi capable.Hmm...I recreated the services file and that seems to have made it work. Now to proceed with the rest of the instructions. Thanks Tracy !
Which version of Armbian did you use. My work with the Gnome version has caused issue with the VNC/X11 connection. I tried the Cinnamon desktop and have gotten a little further. I am going to try hooking up directly to a KVM solution on it and see if there is anything "quirky" that needs to be done.The process went well....actually I originally started with Armbian and ended up getting stuck at the same spot as I did with the OrangePi version....after we got that straightened out I went back to try with Armbian since I knew it was much quicker and it's worked so far. I've gotten as far as installing the extra catalogs.
GNOME
and Cinnamon
desktops.XFCE
Jammy image (all desktops used were based upon Jammy) I had no issues with VNC working correctly and my user being auto logged in.I contemplated that at one point, but decided since the eMMC is only 8GB and the install (for my current instance of Armbian) is 17GB it wouldn't work. The OrangePi install of Jammy was similar. The reason my install is so large is the databases I download for the plate solving. If you didn't download the larger databases, you could probably squeeze it on there, but I like having more stars for plate solving available. I'll do some research and see what I fan find out.Hi Tracy. Do you know how to copy the microSD card to the eMMC and make it boot from that ? I would then keep the microSD card as a backup just in case.
You don't want to write anything into the swap file... the OS uses that area for when it runs out of actual physical memory.Maybe I can copy this install to the eMMC drive and download the database files to the uSD card ? I see there's a 994.8M zram swap file on there too.
I get some message about having root access.
sudo apt-get remove <package-name>
and then put in your Armbian password for the user you created when prompted.