×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

New All Sky camera management software: indi-allsky

  • Posts: 17
  • Thank you received: 0
Also unable to correctly stop indi.allsky. When i send the "systemctl --user stop indi-allsky" command, it takes minutes, and after that i see the status:
pi@indi-allsky:~ $ systemctl --user status indi-allsky
● indi-allsky.service - Indi AllSky Service
     Loaded: loaded (/home/pi/.config/systemd/user/indi-allsky.service; enabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Sun 2022-06-12 16:07:53 CEST; 1min 17s ago
    Process: 668 ExecStart=/home/pi/indi-allsky/virtualenv/indi-allsky/bin/python3 allsky.py --config /etc/indi-allsky/config.json --log syslog run (code=killed, signa>
    Process: 1738 ExecStop=/bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
   Main PID: 668 (code=killed, signal=KILL)
        CPU: 12.873s
 
Jun 12 16:07:45 indi-allsky python3[668]: [INFO] MainProcess allsky._queueManualTasks() #1423: Checking for manually submitted tasks
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: State 'stop-sigterm' timed out. Killing.
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: Killing process 668 (python3) with signal SIGKILL.
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: Killing process 1264 (python3) with signal SIGKILL.
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: Killing process 1265 (python3) with signal SIGKILL.
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: Killing process 1266 (python3) with signal SIGKILL.
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: Main process exited, code=killed, status=9/KILL
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: Failed with result 'timeout'.
Jun 12 16:07:53 indi-allsky systemd[632]: Stopped Indi AllSky Service.
Jun 12 16:07:53 indi-allsky systemd[632]: indi-allsky.service: Consumed 12.873s CPU time.

Also i see that video0 device is busy maybe:
pi@indi-allsky:~ $ v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
        /dev/video10
        /dev/video11
        /dev/video12
        /dev/video18
        /dev/video31
        /dev/media2
 
bcm2835-isp (platform:bcm2835-isp):
        /dev/video13
        /dev/video14
        /dev/video15
        /dev/video16
        /dev/video20
        /dev/video21
        /dev/video22
        /dev/video23
        /dev/media0
        /dev/media1
 
Cannot open device /dev/video0, exiting.

After complete reboot i have the same. My camera is dead?
1 year 9 months ago #83535

Please Log in or Create an account to join the conversation.

  • Posts: 17
  • Thank you received: 0
Camera seems to be ok. Connected to my Windows 10 system i got picture with SharpCap.
1 year 9 months ago #83536

Please Log in or Create an account to join the conversation.

  • Posts: 114
  • Thank you received: 17
Laszlo,
If this is the USB 2 type ASI 120 MC model it will no longer work with Linux operating systems. You will need one of the newer USB3, ASI120 MC-S cameras or USB C, ASI120 mini for it to work.

Hope this helps

Alan
1 year 9 months ago #83538

Please Log in or Create an account to join the conversation.

  • Posts: 17
  • Thank you received: 0

Until today at 13h it was working. I have the ASI 120 MC (black USB connector on the side).
1 year 9 months ago #83539

Please Log in or Create an account to join the conversation.

  • Posts: 114
  • Thank you received: 17
Laszlo,

Yes it will sort of work, especially if you have got the compatible firmware "asi120mm-compatible.iic" installed it will show some sort of image, but it will be mainly broken & distorted and the exposure controls don't fully work, There are a few threads about this subject on the forum. It would be worth a search through and have a read up on it.

Regards

Alan
1 year 9 months ago #83540

Please Log in or Create an account to join the conversation.

  • Posts: 3
  • Thank you received: 0
Is it possible to use an IMX-291 camera from those sold on Aliexpress? I'm trying to make one work but I think the driver I chose in the installation ( 24 indi_sony_ccd) is a wrong option.
1 year 9 months ago #83561
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 255
  • Thank you received: 65

I think you would use the indi_v4l2_ccd server.
1 year 9 months ago #83583

Please Log in or Create an account to join the conversation.

  • Posts: 3
  • Thank you received: 0
Thanks. I will try your suggestion.
1 year 9 months ago #83598

Please Log in or Create an account to join the conversation.

  • Posts: 83
  • Thank you received: 9
Aaron,
I appreciate all the hard work you have done to create this package! I just installed Indi AllSky on an Astroberry server running on a Raspberry PI 4. The installed seemed to go just fine. It was a clean install of Astroberry and Allsky. I started the service just as described in the install section of the readme file, no errors. Where things go off the rail is when I try to access the application with the Raspberry PI using raspberrypi.local/ I get the Astroberry log on page. what am I doing wrong??
1 year 9 months ago #83670

Please Log in or Create an account to join the conversation.

  • Posts: 2247
  • Thank you received: 223
Unable to install this tool on an Odroid C4 running Ubuntu 20.04LTS

heidenrod@heidenrod-obs:~/indi-allsky$ ./setup.sh
###############################################
### Welcome to the indi-allsky setup script ###
###############################################


Distribution: Ubuntu
Release: 20.04
Arch: aarch64

INDI_DRIVER_PATH: /usr/bin
INDISERVER_SERVICE_NAME: indiserver
ALLSKY_SERVICE_NAME: indi-allsky
GUNICORN_SERVICE_NAME: gunicorn-indi-allsky
ALLSKY_ETC: /etc/indi-allsky
HTDOCS_FOLDER: /var/www/html/allsky
DB_FOLDER: /var/lib/indi-allsky
DB_FILE: /var/lib/indi-allsky/indi-allsky.sqlite
INSTALL_INDI: true
HTTP_PORT: 80
HTTPS_PORT: 443

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
fcitx-frontend-qt5 : Depends: libqt5gui5 (>= 5.9.0~beta) but it is not going to be installed or
libqt5gui5-gles (>= 5.9.0~beta) but it is not going to be installed
fcitx5-module-quickphrase-editor : Depends: libqt5gui5 (>= 5.7.0) but it is not going to be installed or
libqt5gui5-gles (>= 5.7.0) but it is not going to be installed
libfcitx-qt5-1 : Depends: libqt5gui5 (>= 5.7.0) but it is not going to be installed or
libqt5gui5-gles (>= 5.7.0) but it is not going to be installed
libqt5svg5 : Depends: libqt5gui5 (>= 5.12.8+dfsg~) but it is not going to be installed or
libqt5gui5-gles (>= 5.12.8+dfsg~) but it is not going to be installed
libqt5widgets5 : Depends: libqt5gui5 (>= 5.12.5) but it is not going to be installed or
libqt5gui5-gles (>= 5.12.5) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.


The script exited abnormally, please try to run again...
Last edit: 1 year 9 months ago by Gonzothegreat.
1 year 9 months ago #83682

Please Log in or Create an account to join the conversation.

  • Posts: 2247
  • Thank you received: 223
looks like the following fixed it:
# apt remove fcitx-frontend-qt5 fcitx5-module-quickphrase-editor libfcitx-qt5-1 libqt5svg5 libqt5widgets5
I had to remove them first...
1 year 9 months ago #83683

Please Log in or Create an account to join the conversation.

  • Posts: 2247
  • Thank you received: 223
I see that the tool uses Apache, it might be a good idea to also provide an Nginx version.
1 year 9 months ago #83684

Please Log in or Create an account to join the conversation.

Time to create page: 0.726 seconds