×

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: 200
  • Thank you received: 18
I rebuild indi and redid setup and now camera does connect but after a few images it stops:

Aug 13 12:55:41 allsky [INFO] MainProcess allsky.run() #741: Total time since last exposure 15.0057 s
Aug 13 12:55:45 allsky [INFO] MainProcess indi.newMessage() #218: new Message 2022-08-13T18:55:45: [ERROR] Exposure failed after 3 attempts.
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.run() #607: Camera last ready: 22.3s
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.run() #608: Exposure state: ALERT
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.detectNight() #853: Sun altitude: 68:37:59.4
Aug 13 12:55:49 allsky [INFO] MainProcess allsky.detectMoonMode() #870: Moon altitide: -54:51:10.5, phase 95.7%
Aug 13 12:55:49 allsky [INFO] MainProcess indi.getCcdTemperature() #422: Sensor temperature: 46.6
Aug 13 12:55:49 allsky [INFO] MainProcess allsky._queueManualTasks() #1441: Checking for manually submitted tasks
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.run() #607: Camera last ready: 32.3s
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.run() #608: Exposure state: ALERT
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.detectNight() #853: Sun altitude: 68:38:17.1
Aug 13 12:55:59 allsky [INFO] MainProcess allsky.detectMoonMode() #870: Moon altitide: -54:52:39.1, phase 95.7%
Aug 13 12:55:59 allsky [INFO] MainProcess indi.getCcdTemperature() #422: Sensor temperature: 46.6
Aug 13 12:55:59 allsky [INFO] MainProcess allsky._queueManualTasks() #1441: Checking for manually submitted tasks
Aug 13 12:56:09 allsky [INFO] MainProcess allsky.run() #607: Camera last ready: 42.3s
1 year 7 months ago #85325

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

  • Posts: 200
  • Thank you received: 18
It seems to work OK when I bring it inside - maybe a temperature issue?

Temp was a red herring, it looks like usb cable problem.
Last edit: 1 year 7 months ago by Thomas Mason. Reason: Updated to correct issue
1 year 7 months ago #85328

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

  • Posts: 255
  • Thank you received: 65
Hello All,

I just released a new version of indi-allsky to support some cameras that are not compatible with INDI on the Raspberry Pi platform. I still consider INDI to be my primary platform, but I think there is value in supporting alternate interfaces. Some of these cameras are considerably cheaper than dedicated astronomy cameras so they are ideal for all sky camera deployments.

Currently, the Raspberry Pi HQ camera is only supported in INDI on the Raspbian 10 32-bit platform. Unfortunately, the Raspi Hq camera support is via libmmal which is not compatible with 64-bit platforms. It also does not appear to build properly on Raspbian 11 32-bit, so there is currently no support for the HQ camera on the latest Raspberry Pi platform.

The Raspi HQ camera (imx477) is supported via libcamera. There is also a new camera, the Waveshare imx378 which should work, as well. Dark frames are fully supported on these cameras.

github.com/aaronwmorris/indi-allsky
The following user(s) said Thank You: Jasem Mutlaq
1 year 7 months ago #85487

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

Thank you Aaron. I was planning to take the plunge and develop indi-libcamera but I was hoping someone would start this and that didn't happen yet. Do you think we can collaborate on this? I can create the skeleton and now since you have experience with this perhaps it would be easy to quickly develop this driver.
1 year 7 months ago #85489

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

  • Posts: 62
  • Thank you received: 1
Hello Aaron,

I installed your Indi-allsky sw on a Raspian 10 32-bit sd card on a Raspi 3 and connected the raspy HQ camera. As driver I selected Indi_rpicam.

The indiserver service is running, however the Indi-allsky service fails with

● indi-allsky.service - Indi AllSky Service
Loaded: loaded (/home/pi/.config/systemd/user/indi-allsky.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Sat 2022-08-20 12:17:59 CEST; 6s ago
Process: 801 ExecStart=/home/pi/indi-allsky/virtualenv/indi-allsky/bin/python3 allsky.py --config /etc/indi-allsky/config.json --log syslog run (code=killed, signal=SEGV)
Main PID: 801 (code=killed, signal=SEGV)
Aug 20 12:17:59 raspi-allsky python3[801]: 1.5499999523162841797
Aug 20 12:17:59 raspi-allsky python3[801]: </oneNumber>
Aug 20 12:17:59 raspi-allsky python3[801]: <oneNumber name="CCD_BITSPERPIXEL">
Aug 20 12:17:59 raspi-allsky python3[801]: 16
Aug 20 12:17:59 raspi-allsky python3[801]: </oneNumber>
Aug 20 12:17:59 raspi-allsky python3[801]: </setNumberVector>
Aug 20 12:17:58 raspi-allsky python3[801]: [INFO] MainProcess indi.newSwitch() #218: new Switch CONNECTION for device RPI Camera
Aug 20 12:17:59 raspi-allsky python3[801]: [INFO] MainProcess indi.newSwitch() #218: new Switch DEBUG for device RPI Camera
Aug 20 12:17:59 raspi-allsky systemd[677]: indi-allsky.service: Main process exited, code=killed, status=11/SEGV
Aug 20 12:17:59 raspi-allsky systemd[677]: indi-allsky.service: Failed with result 'signal'.

What is wrong?

Thank you,
Kurt
1 year 7 months ago #85490

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

  • Posts: 255
  • Thank you received: 65
Let me put my HQ camera on my Raspi 3 in a bit here and I will test it out. I have only ever used mine on a Raspi 4.
1 year 7 months ago #85503

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

  • Posts: 255
  • Thank you received: 65

I would love to be able to help, but for this iteration, I just settled on using the libcamera-still command to generate images instead of using the C or Python bindings. I was very interested in using the Python bindings, but the Python module is not yet installable via the normal pythonic way (pip/virtualenv).

I had to deal with the libcamera-still command generating DNG files for raw data and I just hard coded the bayer pattern in my code for now.
1 year 7 months ago #85504

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

  • Posts: 255
  • Thank you received: 65
I did do one thing that I thought was creative, but is really only useful in my use case. For the libcamera integration, indi-allsky thinks it is talking to a normal indiserver.

indi-allsky uses the pyindi-client to interact with INDI. Therefore, I had to write a fake pyindi-client class to emulate the behavior of this module. indi-allsky still calls functions like connectServer(), but they do not do anything.
1 year 7 months ago #85505

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

  • Posts: 62
  • Thank you received: 1
OK, but does this mean that for the time being I cannot use my configuration?
1 year 7 months ago #85506

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

  • Posts: 62
  • Thank you received: 1
The sd card from my raspy 3 also fails when used in my raspy 4.
1 year 7 months ago #85509

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

  • Posts: 255
  • Thank you received: 65
I am getting the same error with my Rpi3. I need to go check on my Rpi4, maybe I am running an older version of indi.
1 year 7 months ago #85510

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

  • Posts: 30
  • Thank you received: 2
So according to the github page the rpi HQ camera is supported witg libcamera on Bullseye 64 bit when compiled on device.

Is there a downside to this or is it fully supported by indi-allsky when done this way?
Last edit: 1 year 7 months ago by Bill. Reason: More info added
1 year 7 months ago #85514

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

Time to create page: 1.505 seconds