Yeah, I did that, but it feels a bit hacky that I can't set the backlash to its true value, and then add some overscan on top.
Thanks.
Read More...
Same here. Upgrading to Sonoma solves the problem. A bit weird that kstars is the app that is most demanding with my keeping things up to date, but it is what it is.
Read More...
FWIW, in a Bookworm Raspberry Pi OS aberration inspector crashes Kstars all the time and the way around it is to launch Kstars from the command line first setting XDG_SESSION_TYPE=x11.
First seen here: www.indilib.org/forum/ekos/14456-aberrat...rashing-on-rpi4.html
Read More...
It seems to have done the trick. Can you please explain why that would help? What's the big difference between launching from shell with that variable set vs double click on the application icon?
Read More...
I have a Raspberry Pi 4 with 8Gb RAM, which should be plenty for kstars/ekos, but I find the aberration inspector crashing ekos everytime. It does the AF run, then it just dies. No warning, nothing in the logs.
How can I produce a debug log to submit a bug report?
Setup:
- Raspberry Pi 4 64bits, 8Gb RAM
- Sandisk Extreme 64Gb card
- Raspberry Pi OS (Bookworm)
- Kstars 3.6.9 built from source using script from gitea.nouspiro.space/nou/astro-soft-build.git
- Indi 2.0.6
- Drivers: iOptron iEQ45 (Zeq45); Altair CCD; Pegasus Focus Cube; Pegasus Pocker Power Advance; Starlight Xpress
Steps to reproduce:
- Open kstars, start indi;
- go straight to focus tab, enable mosaic mask (leave default settings), run aberration inspector.
Read More...
I have an Edge HD, known for it's substantial backlash, and a pegasus focus cube with 11510 steps per revolution. All maths done right and my focuser moves a whopping 23 steps per micron! I measured the backlash at between 1500 and 1750 steps, which sounds absolutely ridiculous, but when you add the 23 steps/micron scale it amounts to a very reasonable 65 to 75 microns, which isn't a lot, actually. But in Indi and especially in Kstars' autofocus settings I see that the most I can set backlash to is 1000. Am I missing something? How can I set the backlash to 1750 and keep it that way? Even if I set it in the driver settings as soon as I go to the auto focus settings it will go back to 1000.
Read More...
Yeah, that's what I did, but it takes quite a while to build everytime I want to upgrade, a simple apt upgrade would be quicker 
Too bad the astroberry repository seems to be stale.
Read More...
Hello there!
I'm building a raspberry pi image from scratch using Bookworm as a base, but I can't figure out how to install indi+kstars without making a mess of my distro. The Astroberry packages only have Kstars 3.6.0, a bit old for my purposes, and the Ubuntu repos require libc6 2.38 or greater, and Bookworm has 2.36.
Am I forced to choose between a build from source code or making a frankendebian?
Thanks!
Read More...
I know this is quite an old thread, but it may be helpful to others as the issue also affects me and it's still ongoing.
I have a 183C Pro TEC and a GPCAM2 290m and on Ekos I get timeouts all the time. Can't get any exposures out of the 290m and the 183C is reporting temperature errors and connections time out often.
I've filed an issue with Altair, as both cameras work great out of the box in Altair Capture (both Mac and Windows) and it turns out there are some issues in the Altair Indi driver. They seem to be old issues, so it's likely these woes are all coming from there.
The good news is that they have now been identified and Altair is working on a fix for their Indi driver.
Read More...