Closed Hely0n closed 1 year ago
I did a fresh reinstall on another Pi and it's the same and I found out it's a issue from ustreamer: https://github.com/pikvm/ustreamer/issues/198
Is there some workaround to use until they fix it? Maybe an alternative to ustreamer or the whole crowsnest that's compatible to Mainsail/Moonraker
Thanks to the swarm intelligence on the discord server, we have a workaround!!
That one will come, one day... I am bit busy right now but yeah, there is already an experimental branch ...
But..
THERE IS ABSOLUTLY NO SUPPORT FOR OTHER THAN THE STABLE VERSION!
Thanks in Advance
Talk about timing - I've been trying to get my Pi Cam 3 working for two days with no luck. This might explain it
Yeah for me it was this whole day, until i looked at the discord channel. Just try out https://github.com/roamingthings/spyglass, it's very easy. I added it as a systemctl service for autostarting. One day Crowsnest is fixed and we can switch back, as there are some drawbacks like no adaptive mjpeg.
I might give that a try but, until then, I think I might just reinstall my trusty logitech until crowsnest is back on its feet.
Please note, this is not an issue with crowsnest by any means. this is an issue with the newer cameras that arent able to use the old libraries(sony sensor based cameras like the pi cam 3) usb cameras should not have any issues, even using a sony sensor. Its a flaw in the way raspbian buster handles camera devices on csi now, specifically related to raspberry. this is why libcamera works. Libcamera was created to be able to use these new cams, by the raspberry pi foundation.
For more information, please see this issue: https://github.com/mainsail-crew/crowsnest/issues/67
Credits to @ayucam for finding this issue with the system itself, and working to implement ways around it. Credits to the mainsail team for their understanding of it and trying to work around it.
on this website, these guy susceffuly make work the pi cam 3 by installing a streamer in bullseye. You can give it a try. The final working method is the post # 72 Skip the first step, as it is an octoprint image.
https://community.octoprint.org/t/pi-camera-v3-imx-chipset-based-cameras-not-working/49022/72
There is already a sideproject for raspicam v3 ...
But at some point it will find its way to crowsnest ...
Thanks for the workaround for raspicam V3.
I found one instruction missing from this thread and https://github.com/roamingthings/spyglass:
You have to re-enable libcamera in boot config
sudo vi /boot/config.txt
Under ## Disable libcamera (interferes with ustreamer, when using raspicams) change to 1
camera_auto_detect=1
Any news on an update for it ? i can't get it to work in spyglass... and want multi cam
Yes, I am almost done with develop branch using camera-streamer. We found 2 little bugs, that I will fix during this week. But you could try it if you are interessted. Cannt give support yet, but it works somehow/somewhat ...
I'm having problems with spyglass too. Any updates on solving this issue?
Hi , any news on this ? I just bought a Pi Cam 3 and didnt check it wouldnt work :(
I'm having problems with spyglass too. Any updates on solving this issue?
As for now - no
pi@mainsailos:~ $ libcamera-hello
Preview window unavailable
[0:01:57.680285034] [1433] INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[0:01:57.699442216] [1434] ERROR V4L2 v4l2_device.cpp:352 'imx708': Unable to set controls: Device or resource busy
[0:01:57.712827110] [1434] INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to ``Unicam device /dev/media4 and ISP device /dev/media1
[0:01:57.713162200] [1433] INFO Camera camera.cpp:841 Pipeline handler in use by another process
ERROR: *** failed to acquire camera /base/soc/i2c0mux/i2c@1/imx708@1a ***
I got this
pi@mainsailos:~ $ libcamera-hello
Preview window unavailable
[0:01:57.680285034] [1433] INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[0:01:57.699442216] [1434] ERROR V4L2 v4l2_device.cpp:352 'imx708': Unable to set controls: Device or resource busy
[0:01:57.712827110] [1434] INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to
Unicam device /dev/media4 and ISP device /dev/media1`
[0:01:57.713162200] [1433] INFO Camera camera.cpp:841 Pipeline handler in use by another process`ERROR: *** failed to acquire camera /base/soc/i2c0mux/i2c@1/imx708@1a ***
I got this
Did you find a solution for this? I've got the same issue... "Device or resource busy".
Pipeline handler in use by another process
shutdown/stop all other services which try to open your webcam...
Just updated crowsnest to let it replace spyglass again, but it doesn't work. I managed to get it working by logs (it says ... DONE! Starting camera-streamer with Device /dev/video0 ...) But there is no image either in mainsail, nor on the mobileraker App and if I call the page manually, it says "server error", while the logs don't change and it seems like everything works.
Moonraker says "HttpException: Stream returned 500 status"
Okay you have to replace the "device" parameter in the config to the one that gets listed in the log manually. Now it works, but I think this should happen automatically and the logs shouldn't say that everything is okay 😁.
But otherwise, well done guys! I can imagine how much work was involved to make this update.
how was your setup? my cam still doesn't work
Okay you have to replace the "device" parameter in the config to the one that gets listed in the log manually. Now it works, but I think this should happen automatically and the logs shouldn't say that everything is okay 😁.
But otherwise, well done guys! I can imagine how much work was involved to make this update.
I reinstalled Mainsail OS from scratch to get mine to work. Just saved my config files, reimaged, installed Spyglass and it was all hunky-dory.
@TacoLococo you don't need spyglass with the new mainsailOS, because camera-streamer also support v3 cams...
Ahoi!
It looks like this ticket is a request for help (or similar). Many helpful people will not see your message here and you are unlikely to get a useful response.
We use github to handle bugreports, feature requests and planning new releases.
Please use our Discord-Server for help: discord.gg/mainsail
This ticket will be automatically closed.
Fair wind and a following sea! ~ Your friendly MainsailGithubBot
PS: I'm just an automated script, not a real sailor.
Hi, I had been following this closely and had been impacted by this.
There is now a fix in Crowsnest that supports Pi Camera Module 3. I prefer to use this option as it fully supports Obico where the spyglass option doesn't seem to.
FIX: Update Crowsnest as per guide here: https://crowsnest.mainsail.xyz/faq/upgrade-from-v3-to-v4
NOTE if you upgrade from Mainsail GUI, you will have to manually uninstall the old version, read the guide very carefully!
Hope this helps someone!
What happened
I bought the new Raspberry Pi Camera Model 3 and realized, it wasn't detected. I found out that the cam was just released 3 weeks ago, so i made an "apt update && apt full-upgrade" and it indeed updated some libcamera stuff.
crowsnest stopped working afterwards and after running the uninstall.sh and then "make install" again (with freshly pulled as from today), it was detected and shows some FPS in mainsail, but it says "no Signal" on the image.
libcamera-still worked, so the camera is okay.
Is it normal to have many /dev/video* devices with different numbers? Maybe the culprit is here?
While the crowsnest.log seems to act like everything is fine,
"systemctl status crowsnest.service"
says this:
What did you expect to happen
The new Raspberry Pi camera works plug & play like always, at least after system upgrade.
How to reproduce
Just try to use a raspberry pi camera 3.
Maybe the error is somewhere else but as I ordered the cam because my old Raspicam v2.1 broke by trying to fit it in an enclosue (so not software related damage) and I can't test it now.
Additional information
crowsnest.log, just in case: