How about nix package manager? I believe it has recent version of INDI and should be available for Debian. Best part is that it supports very easy rollbacks which is very useful in case if some issue was introduced after an update.
1. Try to run indi drivers outside of kstars
2. Try using USB 2 port if you have it
Interesting, thanks for sharing. Was it wsl or wsl2?
I did not try this myself, but in theory Nix should be able to solve this problem. All updates there are atomic and can be easily reverted.
It works on most distros.
Instead of using USB dongle, I decided to use PCIe card, inserted into m.2. I used couple of different Intel based WfFi cards and both of them worked. I think USB also should work, but I decided that it is more important to have higher speed of WiFi as opposed to disk, so used the PCIe card for Wifi.
My script already installs everything for Access Point, all you need to do is to modify /etc/create_ap.conf to point to correct device names for ethernet and wireless adapter.
I recently updated my system and Touptek INDI driver seems to be changed dramatically:
- Now it takes offset between 1 and 31 only
- If does not show parameter for switching between high and low gains
- gain parameter does not switch between low and high gain as it used to be
Looks like now I am supposed to switch between low and high gain using INDI control panel.
Is this expected?
I much prefer the old way of doing things because i was able to switch between low and high gain just by using the gain value.
Make sure to reboot after running this command (it is an overkill, but just to be safe).
I run 3 rigs now using this board. Pretty much all of them are using:
1. OnStep mount controllers which also drives focuser
2. ASI174 or ASI120 guide camera
3. Touptek IMX571 mono camera
4. SX Filter Wheel
Touptek camera has an internal hub, which I am using for running filter wheel and guider.
I don't need to use a separate USB hub and I even have a spare USB port.
I encountered couple of issues:
1. Once in a while I had issues with running main camera using USB3 port, so I normally use USB2 port for camera.
2. There was a weird issue where one of the rigs was not able to connect to the main camera. It turned out that a DC/DC converter from 12v to 5v was at fault. No idea why, because rest of the things were working just fine. Maybe it was not strong enough or had poor signal. Once I replaced it, all is working fine.
So some suggestions are:
1. Use separate power supplies for powering different components
2. Try using USB2 port for camera and also use USB2 cable
3. Try to get rid of USB hub, at least temporarily, I always had problems with USB hubs, especially 7 port ones
4. If you have issue with serial connection, you need to make your user as part of dialout group. You can find command in my Makefile
5. I also use tightvnc, see my script how it is installed
Amazon now has Orange Pi 5 4GB model for just $88 delivered in couple of days. There is also a very nice case available on Aliexpress for $15 shipped m.aliexpress.us/item/3256805091935722.ht...764070210011713847_1
I use tightvnc and it runs great. You can see my script how to install it.
There was a comparison of RPI4 vs OPI5 posted yesterday: www.phoronix.com/review/orange-pi-5/2
TLDR: Across 169 different benchmarks I ran with the Orange Pi 5, this single board computer came out to delivering 2.85x the performance of the Raspberry Pi 400 overall