mars

Please run the following commands and take a screenshot: cd ~/Projects/indi git log indiserver cd ~/Projects/indi-3rdparty git log From the error message, it seems that indilib is not 2.0.9 (but it is unclear whether the file version is wrong or the installation is wrong).

I believe there are a few points that need to be clarified.: This is the complete set of steps and scripts, just like the pictures provided before, starting from the burning of the SD card, and you should also start from this step (this is to completely eliminate old environmental factors). There are two ways to install indi-3rdparty, full installation and partial installation. To debug this issue, only one driver is installed in the script, so you should follow the content in the script. (You will...

The issue you encountered should be due to the master version being too active in development. I have selected a specific version in the script (both INDI and 3rd party need to use the same version). I have documented the scripts used You can skip the part about modifying the /etc/apt/sources.list file; I had to change the mirror myself because the network was too slow.

This issue appears to be related to a commit from this month; I need to set up a new system to verify it.

I understand that from the phenomena you've observed, it does seem like an SDK error, but I'm looking at the logs from execution. The logs show that the incorrect API was called, and it was called in a very strange way (half right, half wrong). This kind of issue typically occurs in some temporary versions during the development phase, and previous logs also indicate that the SDK at that time was a temporary version, not a released version. So it's clear that the error occurred before the SDK. Moreover,...

I understand that from the phenomena you've observed, it does seem like an SDK error, but I'm looking at the logs from execution. The logs show that the incorrect API was called, and it was called in a very strange way (half right, half wrong). This kind of issue typically occurs in some temporary versions during the development phase, and previous logs also indicate that the SDK at that time was a temporary version, not a released version. So it's clear that the error occurred before the SDK. Moreover,...

I understand that from the phenomena you've observed, it does seem like an SDK error, but I'm looking at the logs from execution. The logs show that the incorrect API was called, and it was called in a very strange way (half right, half wrong). This kind of issue typically occurs in some temporary versions during the development phase, and previous logs also indicate that the SDK at that time was a temporary version, not a released version. So it's clear that the error occurred before the SDK. Moreover,...