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.
Thank you all for your reply. Good to know that others are able to compile on Pi.
I was trying to build kstars from latest git on 2GB Pi4 and looks like OS is running out of memory so either the build fails or the OS crashes.
If I remember correctly, I was able to build kstars on 1GB Pi3 in the past.
Am I missing something?
Is it possible to cross-compile kstars on PC for Pi?
Here are couple of commands to create a script:
echo "indiserver -v indi_lx200_OnStep indi_sbig_ccd indi_asi_ccd indi_sx_wheel" > ~/indi.sh
chmod 777 ~/indi.sh
With Uno and Shield, even a box is available off the shelf:
It is better to run the drivers outside of kstars, especially if it is prone to crashing.
I just wrote a shell script that starts all my INDI drivers.
Here is the project documentation for the focuser which supports this combination:
You need to find this option: "L293D Shield + UNO"
You would have to write an INDI driver to translate focusing commands to G code. Possible but I think not worth it.
There is a much simpler option for focuser hardware, available for MyFocuserPro:
Arduino Uno + Motor Shield + NEMA 17 motor.
Motor Shield just plugs into the Arduino board, no soldering whatsoever and very compact.
There are even project boxes available for this combo.
I built several focusers using this approach, they all work very well.
I believe it is not possible to install Ubuntu packages on Astroberry as they are based on different OS.
I prefer running Kstars on Ubuntu as it receives frequent updates from Ubuntu PPA repositories and you can switch between stable and nightly releases.
Here is a script which builds a fully functional system based on Ubuntu automatically:
You can run the whole script or only install individual components, e.g.
to install vnc only.