Issues issues issues

[Shand359]

I have tried again to get the allsky to work. I have taken a 2 month break to cool myself down and hopefully start a fresh... since my last attempt i cannot even get a live image on screen. at least beforehand i could get this for a few hours..... When i checked the log, all it shows is:

STARTING EXPOSURE at: 2022-04-13 20:01:44 @ 1.0 sec
Apr 13 20:01:44 allsky allsky.sh[3049]: > Capture command: raspistill --output '/home/pi/allsky/tmp/image-20220413200144.jpg' --thumb none --burst -st --timeout 10 --nopreview --mode 3 --exposure off --shutter 1000000 --analoggain 4 --awb off --awbgains 1,2 --vflip --saturation 50 --brightness 100 --quality 95
Apr 13 20:01:44 allsky allsky.sh[6048]: sh: 1: raspistill: not found
Apr 13 20:01:44 allsky allsky.sh[3049]: >>> Unable to take picture, return code=32512, r=127
Apr 13 20:01:44 allsky allsky.sh[3049]: xxxx Got signal 127 in capture_RPiHQ.cpp

repeating over and over....

[EricClaeys]

@Shand359 Are you on Buster or Bullseye?
Buster uses the raspistill command to take the pictures, but for some reason it's not installed on your Pi. I will check later if the Allsky installation is supposed to install it.

[Shand359]

I have Bullseye.... I was playing about yesterday and i now have the camera, timelapse and keograms working as intended. I just need to try and get some steps to install a dew heater correctly so it only runs when needed as opposed to all the time.... for the future id like to add a motor for focusing the lens from the pi....

[Shand359]

Thank you however i found the issue..... my ribbon cable had a break in it..... sorry about that

[EricClaeys]

@Shand359 Not sure how a bad cable can cause a command not to be found, unless you are on Bullseye and the libcamera-still command didn't work due to the cable, so Allsky assumed you were using raspistill, which isn't on Bullseye.

[Shand359]

i honestly dont know. all i know is that the cable attached meant the camera was not detected. When i change it out and replaced it the camera was picked up straight away.... god knows

[EricClaeys]

@Shand359 I looked at the code and if the libcamera-still command is not found, or does not work (as in your case), it assumes raspistill exists(which it doesn't on Bullseye).
I put a change request in to check if raspistill exists, and if it doesn't, to output an error message and quit. That will be a lot less confusing.
Thanks for finding that bug!