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

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.

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.

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.

OK, but does this mean that for the time being I cannot use my configuration?

The sd card from my raspy 3 also fails when used in my raspy 4.

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.

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?

No downsides other than you have to build indi even though you do not use it. The libcamera support is transparent to the user.

You may want to forgo using Raspian 10 and just use the libcamera support on Raspian 11 64-bit instead.

I guess this is confusing since Raspbian 11 already has libcamera support.

Would it be safe to say for Raspbian 11 arm64:
Compile indi with build_indi.sh for indilib supported cameras
OR
Use libcamera for Raspberry PI HQ camera ?

---Answered own question:

Ah, that would be a NO, build_indi.sh is required regardless.
Thanks

It's alright, I started development of the indi-libcamera driver now. Hopefully in a couple of weeks we'll have something usable.