Much appreciated Kevin! I started mucking with the settings (I had clicked the first check box for grins) without success. Oddly enough, following your lead, with just the other check box checked I still get the same large window ugliness at 150%. So, I've set it back to 149%.
I will try my other laptop. It will probably work just fine - at this point, nothing would surprise me.
Finally found the solution - Windows desktop scaling *MUST* be less than 150%. Mine was set to 150% and I had the issues. I set it to 149% and it looks good and Ekos modules window looks good, too. Set it to 151% and it looks ugly again and Ekos modules window collapses as soon as I try to resize.
Okay, so I'm trying running Kstars on Windows and connecting to Indi server on the Potato - so far it's going okay. I'm running simulators for now, but I've run into a small issue. When I click the "Play" button, I get the usual window for the different modules - guide, focus, mount, etc. It's huge and rather ugly, like it's set to a lower resolution, and the lower half is off the screen. However, when I grab the top edge to resize, it collapses never to be seen again.
What am I missing?
Hi Kevin and thanks! I like your idea of using the laptop for some of the heavy lifting. I hadn't thought of that!
My current RP's have 4GB. Not blazingly fast but not too bad. I think Aaron might have hit on one potential area of performance savings for the Potato - kill the GUI at boot.
Thank you! I take when you say 16-bit instead of 32-bit, you're talking about the color depth? And you're suggestion about the disabling the default GUI - currently, it does boot into XFCE, so it's using a bunch of resources for that. If I disable this at boot will the RDP kick off its own? Or is it doing that anyway, so as currently configured it's running 2 instances of XCFE or whatever?
As for Kstars, I can enable low resource mode for the FITS viewer, but Kevin's idea is likely the way I'll go. I'll be using my laptop anyway - that's how I use the Pi - so yeah, why not, right?
I have Astoberry on 2 Raspberry Pi 4's and it is fantastic. But I've had three Pi4's die on me in the past, and given the high cost of pi these days, I decided to try an alternative - Libre Le Potato (2GB, 4 ARM Cortex-A53 @ 1.512GHz, 64-bit)
I got Armbian/Ubuntu 22.04 installed, and I got Indi and Kstars installed. I've tested it out over RDP and it does work. However, it is noticeably slower than the Pi4 (to be expected since this is advertised as more of a Pi3 replacement). But I would like to streamline this gadget as much as possible to squeeze out all possible performance. This means getting rid of bloat and unnecessary startup apps and tasks.
I've read Jerry Black's Odroid writeup (my inspiration for attempting this), but that device seems to have enough horsepower to overcome any shortcomings.
I use VNC on the RP4's, but I read RDP is faster, so that's what I'm using on this Le Potato. I'm also using xfce and lightdm.
ugh - turns out I was using an older version of Ubuntu (16.04). I've now updated to 20.04 or 22.04 and the command worked.
I had my Astroberry die.
So, I am experimenting with trying to install Indi/Ekos/Kstars on an Orange Pi PC+. I have Ubuntu installed, but when I attempt to:
sudo apt-add-repository ppa:mutlaqja/ppa
I get the following error:
Cannot add PPA: 'ppa:~mutlaqja/ubuntu/ppa'.
ERROR: '~mutlaqja' user or team does not exist.
What did I do wrong?
I noticed Bressier Messier mount as one of the mount options, and when I tried it it seems to connect. When I bring up the mount control and press an arrow button I get an error saying the command only works when mount is tracking.
I have pressed "Stop" on the HC, and the display now shows Tracking ON. But no change in Ekos/Kstars.
I have not done a GOTO or alignment or anything. This mount is sitting on my patio and I'm just trying to see if I can control it. My plan is to polar align it and then use plate solving.
My wife's CG5 is a bit fiddly in that before it will talk she has to use previous alignment or something to that effect to bypass the alignment part. I don't see that on the HC.
So now what?
The clicked current and write is an Ekos thing (Indi control panel, mount, site management, park position "Current" "Default" "Write Data" "Purge Data". I presumed you can move the mount to a park position, click current, then write data and it should make that the park position. I *think* this is actually for custom park positions.
When I connect to the mount, it shows up at Polaris. But there is a feature under Eqmod where you can right click anywhere on the screen, select Eqmod mount, then Goto & Set as Park Position. When I did this, the mount would slew to some place way way away from Polaris. I don't know why.
The good news, apparently, is that I reprogrammed the AstroEQ controller to invert DEC, and the mount now appears to be slewing in the correct direction. I had assumed inverting DEC in Indi control panel would have done this, but apparently not. Hopefully, skies will be clear for real testing!