Hi,

Using indiweb within a virtual environment on top of a Debian 12 based machine, the console displays this error :

$ indi-web -x /usr/local/share/indi -v -l ~/indi-web.log
Traceback (most recent call last):
  File "/home/jaq/indiweb/bin/bottle.py", line 876, in _handle
    return route.call(**args)
           ^^^^^^^^^^^^^^^^^^
  File "/home/jaq/indiweb/bin/bottle.py", line 1759, in wrapper
    rv = callback(*a, **ka)
         ^^^^^^^^^^^^^^^^^^
  File "/home/jaq/indiweb/lib/python3.11/site-packages/indiweb/main.py", line 395, in get_indihub_status
    is_running = indihub_agent.is_running()
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/jaq/indiweb/lib/python3.11/site-packages/indiweb/indihub_agent.py", line 57, in is_running
    if self.__async_cmd:
       ^^^^^^^^^^^^^^^^
AttributeError: 'IndiHubAgent' object has no attribute '_IndiHubAgent__async_cmd'

Here is the package list :
$ pip list
Package            Version
------------------ --------
bottle             0.12.25
certifi            2024.2.2
charset-normalizer 3.3.2
idna               3.6
importlib_metadata 7.1.0
indiweb            0.1.8
pip                23.0.1
psutil             5.9.8
requests           2.31.0
setuptools         66.1.1
urllib3            2.2.1
wheel              0.38.4
zipp               3.18.1

Not a real impediment for me, as I only use the server, not the hub. But I think it is worth having a look.
Clear skies,

Dahu

Read More...

Just re-compiled a fresh indilib, and ran a test against an Esatto3 focuser, using CCDCiel as the Indi client : on my side, the external temperature sensor issue is fixed, as the temperature is updated every 5 or 6 seconds.
Thanks to the developper(s).

Dahu

Read More...

I have noticed the same behaviour with 2 different focusers (an Esatto2 and an Esatto3), with of course 2 different temperature sensors. Not only I see the defect with Kstars, but also with CCDCiel . The motor temperature is updated on a regular basis, while the outside temperature is stuck to its initial value.
I would tend to think the Indi driver is the culprit.

Dahu

Read More...

I did : using an Esatto 3 device, which embeds the latest firmware (named as 03-03-07), and the indi_esatto_focus driver. Everything (but the temperature report) is OK. For temperature, I am not sure the issue is software-related, maybe my external sensor has some trouble. But all the main functionalities are up and running.
However, I have not tested with a SestoSenso type of focuser.
Thanks a lot.

Dahu

Read More...

Hi all,

I have just pulled and re-compiled the latest code of indi. And the good new is that the latest commit on the indi repo (d3e66830369ca1b569119e0e92f0680c4717e791) seems to have fixed the issue. Using either Ekos or CCDCiel, I have been able to capture images with my QSI camera.
Warm thanks to those who made that happen.

Dahu

Read More...

Hi Jasem,

Here are the logs. As far as I understand, there is a segmentation fault somewhere.

Best regards,
Dahu

PS : ekosdebugger is really a helpful app. Thanks for that.

Read More...

Hi all,

Having recently upgraded my pillar PC to Ubuntu 22.04, and updated the indi packages accordingly, I am currently facing a blocking issue with the indi_qsi_ccd module : it always crashes at the end of image acquisition. The camera (QSI-632) seems to work correctly, as I can see the shutter open and close for the scheduled duration.

To make sure, I have also compiled the indi library and its third-party modules, but I get the same faulty behavior. and I also get the very same error when using the CCDCiel indi client.

Maybe related, there is another issue, as the log reports :

Error: put_BinX() failed. 0x80040409:Invalid Bin Size.
I have wiped the "QSI CCD_config.xml" file to get a brand new one, but no luck.

Attaching a few logs just in case.
Dahu

Read More...

Hello Wildi,

Thank you for having looked in depth at my logs. I have done some more trials.

Regarding the "Can not change park position while slewing or already parked..." error issue, it happens ... or not. I mean, either there is no error, and writing park data works correctly. In the opposite, if this error appears, then there is no way to workaround it, even by waiting for minutes hoping for the mount to "stabilize". I suspect that I felt in the "noisy" value trap. Maybe a "if (dx < 1e-3 && dy == 1e-3) " parking condition may fix that, or something similar.

For the Park3 final issue, I have not been able to reproduce it clearly. So we may forget about it.

Regarding the timezone, all my set-up (PCs, software, AP mount handset, etc..) is always set in UTC time. This simplifies greatly all the configuration. The AP sidereal time is identical to my software ones, no inconsistency.

Kind regards,
Dahu

Read More...