I upgraded driver from the stable builds and crashes as soon as client connects with this error:
Driver indi_lx200_OnStep: *** stack smashing detected ***: terminated
Has anyone seen this?
Ah, sounds like there is no need to convince you
I think just showing the corners would be super helpful.
I was not aware about this feature, I will try it.
Here is the bible for collimating RC telescopes:
and here is the image on page 14 that would be great to see in viewer in the collimation mode. Of course, the red lines would be difficult to produce and the numbers are redundant.
I think it would be nice to have some kind of a zooming control, where if it is 1, then the preview is as usual, but once you start increasing the value, the corners would be gradually magnified.
Unfortunately, kstars is prone to crashes. It is much better now than it used to be, but still, it happens once in a while.
You can try CCDCiel.
In my experience, it is more stable than Kstars and is very similar in terms of features.
I think it would be very nice to have a feature for assisting with the collimation, where the image preview screen would show corners of the image at 1:1 scale, so the user can see the quality of the stars in the corners all at once, without navigating the viewer.
Would it be possible to prioritize PEC Import/Export?
Also, there is an issue that I am running into once in a while during precision slewing, where if the mount needs to slew very little (~ 1' ), it gets stuck and I have to stop the slewing using the INDI panel.
Any thoughts on how to solve this?
It is much simpler to get cr3 working for CCDciel.
Technically it is possible to do what you want - INDI is using xml for communicating between clients and servers, so you could implement a client on ESP32, but I think you need to rethink your approach.
Here is what I normally do when I need to figure out names of INDI drivers, present on the system: just type indi in the command prompt and press tab a couple of times.
You will get the list of available drivers as a completion.
You can try to figure out how to get INDI drivers from Astroberry, which is also Raspbian based.
I believe Astroberry has some kind of repository for the packages, but I have no idea where it is because I am using Ubuntu.
Here is a script for setting up Ubuntu with all astro software:
I am curious, why do you want to keep ASI software and not switch to Ubuntu or Astroberry?
INDI drivers depend on shared INDI libraries, so you will have to remove the existing INDI stack and then install a new one in case if some of the required drivers are missing.
Can you see what kind of Linux ASIAir is running?
If it is based on Ubuntu, then it should be a fairly straightforward process, considering that you can use INDI PPA for getting the INDI stack.
Hopefully, they did not make any proprietary enhancements to INDI which would prevent their apps from talking to mainstream INDI drivers.
I've made several changes to the script over the past few months:
1. Repaced x11vnc by RealVNC. Issue with x11vnc is that it is slow and prone to having corrupt display. RealVNC is great, but it was challenging to install. You will get RealVNC if you install from scratch, or if you already have a working system, follow the steps below:
2. mate desktop is installed by default
I am also seeing similar issue, I had to downgrade INDI.
Here is a script that installs the full imaging stack:
Installs most commonly used Astrophotography software:
Astrometry with sextractor
ASTAP plate solver, which is much faster than astrometry
Sets up Wireless Access Point. Default name is RPI and password is password but can be changed in the script. Once connected to WAP, IP address of PI is 10.0.0.1
Sets up x11vnc to be started automatically
Configures screen to be 1920x1080 for headless operation
Defaults to KDE Desktop, but Gnome and Mate can also be installed
Syncthing for syncing images into processing PC
Latest Libraw with Canon CR3 support. At this point, only CCDCiel is working with this library, Ekos crashes with it
Full headless operation
Is anyone using PEC with INDI?
I tried recently and it did not work as expected: I recorded one worm rotation and after PEC started playing, I did not see any change in terms of periodic error.