#[SOLVED] Rpi Camera 3 Wide - No video or image
156 messages Β· Page 1 of 1 (latest)
Just to mention, I do have c920 cam, which works fine. Please help me to get the rpi 3 cam working as well.
Sry I somehow overlooked this issue or maybe just forgot about it....
Run cat /boot/config.txt > ~/printer_data/config/boot_config.txt and download the boot_config.txt inside the machine tab of Mainsail
I am IT architect and I am good with Linux, I will provide the boot config shortly
Here it is, i followed the guide to disable the legacy support from v3
Are you using a touchscreen?
Yes, DSI one
Then we found the problem ^^
Not really incompatible but the pi isn't capapble of using both fully at the same time with the new camera stack
Try to set vc4-kms-v3d instaed of vc4-fkms-v3d and maybe the cam will work again
But your touch and rotation of display could be gone then
Well haha, my touch was not working with the default driver
I see
So either the screen or the camera
We can try something first
Run sudo rpi-update pulls/5479. There was an update for the kernel that might help with the problem
With the camera problem ?
Yes
Yup i found the issue on gh
Another thing to try would be this comment: https://github.com/ayufan/camera-streamer/issues/21#issuecomment-1294750888
Okay, thanks a bunch, i do have an ongoing print, as soon as it finishes, i will test both and report back.
So on the first one, perhaps im on the kernel which has this merged already, because its failing to aquire it.
It got merged with 6.1.29, just run the command again. I think this happened the first time
Tired 3 times, same story
Ok, maybe try out sudo rpi-update pulls/5476
But I'm wondering why the artifact should be gone
*gone/changed
Hmm same thing 404
Ok, let me check real quick. I will try to find a working one
Ok, thank you !
This one will bring you to 6.1.29: sudo rpi-update 505fcd158a
It works, i will reboot and test
how does this url: /webcam/webrtc need to change when using two cameras
Yes i am
Those are also shown at the top of crowsnest.conf
Send a crowsnest.log
in debug ?
Yes
Could not set AF_TRIGGER - no AF algorithm or not Auto
Failed to start streaming: Input/output error
The above two shows repeatetly
That shows only for the v3
The Top cam at /webcam/weebrtc should work
Oh, sry thought right now you got problems with just the second stream.
Did you already try to set kms, if that might help and the screen still works correct
Let me try that, although my touchscreen is waveshare 4.3 and not 7 inch
im not sure if it matters for the overlay
The display works, but the camera dissapeared
Thats how i set it
Yup i got it myself as well
Just rebooted with the change
Heyyy
And the display and touch still works
Wonderful, would have never gotten this far by myself !
Thank you for all the help and pointers in the right direction ! Hopefully this issue will help someone else as well.
I hope so too π
I will add the correct command to my notes for the future ^^
Thanks again ! I will close the ticket π
[SOLVED] Rpi Camera 3 Wide - No video or image
Close this post π
Right click or top right three dots
@autumn matrix did you have to change the crowsnest.cfg?
His config (can be found inside the log):
[cam Front]
mode: camera-streamer
enable_rtsp: false
rtsp_port: 8554
port: 8081
device: /base/soc/i2c0mux/i2c@1/imx708@1a
resolution: 1920x1080
max_fps: 15
This problem is about using a touchscreen. If you don't have a touchscreen, then you should open a new post and I will help you there.
hmm. i think i should have all the settings in boot.txt and crowsnest.cfg from above but no dice.
libcamera-hello does nothing. libcamera-jpeg -o pic.jpg does snap a picture
i could be missing some dependancies but dunno how i'd know. i had to rebuild libcamera from scratch because i couldnt even get libcamera-jpeg to work
do I need spyglass π€
I have the same problem.
Either the camera or the touch works. Both together do not work.
did you try https://github.com/roamingthings/spyglass
i haven't yet
apparently there's been talk about it in this discord, found it just googling
no.
I've already read about it too.
I'll take a look at it
i do have a usb cam and that works fine but the image quality is garbage and picam takes up way less space
oh ok.
I have a USB c922 and a picam v3.
Or I take the picam V1.3 again, this one works
I can assure you that you will get the same problems ^^
You read about this on this discord because crowsnest didn't yet have camera-streamer integrated at the beginning of this year, when then module v3 came out. That's why roamingthings and me started that project.
spyglass only got mjpg support and camera-streamer got mjpg and webrtc support. So I recommend camera-streamer. The only downside of camera-streamer is that the image is a bit dark somehow. So if you don't have enough lighting, you might want to have a look at spyglass.
i'd like to get video feed for starters :P
Quick explanation then: WebRTC > MJPEG
WebRTC takes a lot less bandwidth than MJPEG and can lead to higher framerates at higher resolutions if your network setup isn't the ebst
And I see right now that you sent some messages yesteerday. I somehow didn't get them, sry ^^
What screen are you using?
7.9inch Capacitive Touch Screen LCD, 400Γ1280, HDMI, IPS, Toughened Glass Cover
I never had such a problem π€
module 3 has been a headache even in just raspberry os :P
Rebuilding libcamera manually is never a good idea. You should always use the packages from the repos.
it wouldn't even snap a still with libcamera-jpeg
although that could be something else
because it still doesnt if i go back 1 directory from home
That's a waveshare, too. I've already got told that those can be picky sometimes
Set log_level: debug inside your crowsnest.conf and send a new log
You can also set delete_log: true to delete your old logs
mm i thought i had the same screen as marin but perhaps not
but the the log is giving me proper errors it seems
Also another thing. You have a way newer kernel ^^
OP never linked a screen or didn't even mention the vendor, if I skipped correctly over the post again
I let OP update to 6.1.29. That was working for him. To be precise: sudo rpi-update 505fcd158a
I cannot see any errors. Those are all default output
Maybe π€·ββοΈ
Hard to tell what's going on, but most likely they shouldn't have breaked it again
Getting DSI and CSI working together is just annoying.....
What do you mean with that?
Octoprint and screen?
no screen either
PiCam 1.2 was OV5647? There are a lot of fakes out there and those will only work with the legacy stack
but who knows, maybe that wont work either
The picam module v3 will most likely only work without a screen. If there is no screen, there shouldn't be much problems. With screen most problems occur
that's what i gathered
i give up. please ping me if this gets solved some day π
I cannot ping you, as this isn't something we can fix. This is some kernel problem.
If you need help with setting up only a CSI cam without DSI screen then just create a new post and I will help you there.
Also this is heavily depending on the used screen. As long as I don't own that specifc screen I couldn't even know if it's fixed or not
I know it sucks, but we sadly cannot do anything π¦
Just coming across this a year later, but I assume that the status is the same? Tons of suggestions all over the internet but this is the first time that I've come across the news that touchscreen + picam3 is a no go. Been going crazy trying to try all the possible combinations of config dtoverlays or crowsnest configs, but if this is just not possible i guess i just gotta switch back to an older picam
A year later, this topic got more complex π
Bookworm got released and is quite stable now. A lot of people report that they don't have any problems with picams+screen and Bookworm. So that might be an option.
But currently there is also an option with webrtc and Fluidd, so make sure that it's not just a webrtc issue in Fluidd, if you are using Fluidd
Of course it got more complex. Thanks for the info. Currently using mainsail, trying to get this combination of rpi4+cam3+btt 4.3β touch screen to work. Donβt remember what version of the os Iβm running so Iβll have to check that tonight.
Just an update for posterity I guess - confirmed i'm running Bookworm but still can't find a combination of things that will work. Now that I know what to look for, I believe that there is just simply an i2c conflict for raspberrypis 0-4 trying to use the current camera stack and a screen at the same time. I think (but haven't confirmed) that you can try to use the legacy camera stack and get success.
As a detail incase somehow my issue is different and someone has a solution that I haven't tried, this is the only error that I see in my crowsnest.log:
[0:02:53.502331611] [2439] [1;31mERROR [1;37mV4L2 [1;34mv4l2_videodevice.cpp:2026 [0;32m/dev/video1[31:cap]: [0mFailed to start streaming: Input/output error
device/libcamera/buffer_list.cc: CAMERA:capture: Failed to start camera.
I think (but haven't confirmed) that you can try to use the legacy camera stack and get success.
Nope, that won't work with a picam3
As you are running Bookworm, did you already try to set disable_fw_kms_setup to 0?
I also recommend to sent the /boot/firmware/config.txt that I can check your current settings
Hadn't come across disable_fw_kms_setup as a suggestion - i assume in config.txt?
Yes, in config.txt
That's why I asked you about the OS, that I can give suggestions for it
Gotcha. disable_fw_kms_setup didn't appear to change anything. I've tried with and without vc4-kms-v3d, and the only thing that did was either disable or flip my touchscreen.
Attached should be config.txt and crowsnest.log.
Something more or less important, maybe they fixed it already, but never set some settings twice. E.g. the legacy stack had some bug that was caused by setting the setting twice with different parameters
So delete the lower disable_fw_kms_setup=0 and change the first occurence of it. Also remove the dtoverly=imx708. You don't need it, as you are using camera_auto_detect=1
Furthermore set display_auto_detect=1 to 0 if you are defining the screen directly. Also make sure that it's the correct overalay for the touchscreen
After you deleted the dtoveraly (and restarted ofc) send the output of libcamera-hello --list-cameras just as a sanity check for me
k. Didn't notice the first disable_fw line. Removed the extra, set the first one to 0. Set display_auto_detect to 0. Removed imx708 dtoverlay. No changes, log still shows the same input/output error.
Available cameras
-----------------
0 : imx708_wide [4608x2592 10-bit RGGB] (/base/soc/i2c0mux/i2c@1/imx708@1a)
Modes: 'SRGGB10_CSI2P' : 1536x864 [30.00 fps - (65535, 65535)/65535x65535 crop]
2304x1296 [30.00 fps - (65535, 65535)/65535x65535 crop]
4608x2592 [30.00 fps - (65535, 65535)/65535x65535 crop]
Then the last few things are combinations of disable_fw_kms_setup 0 or 1 with either dtoverlay=vc4-kms-v3d, dtoverlay=vc4-fkms-v3d or none of those two
dtoverlay=vc4-kms-v3d or dtoverlay=vc4-fkms-v3d will turn around your screen and/or disable touch. Sadly that's like the "best" thing some people can get, if they want both a picam and a screen
Ok. i'll play around with combinations and see what i can get. I appreciate your time helping me out
Update! Asked on the official pi forums for advice and the response was "you shouldn't have to do anything for the touchscreen and the camera to work. stop messing with config.txt!" So, i reset everything back to default values and was able to successfully get the camera and screen to work at the same time. Only problem was that the touchscreen was flipped. With the new knowledge of what all has changed in bookworm (which is way more than i thought!), I read through the official docs on how to correctly rotate a touchscreen.
For reference this is using a raspberryPi 4B, a BigTreeTech TFT4.3 2.1 touchscreen, and a RaspberryPi Camera Module 3 Wide.
Here's what was needed:
config.txt default values
In config.txt set:
display_auto_detect=0
dtoverlay=vc4-kms-dsi-7inch,invx,invy
AND in cmdline.txt append to the end of the line
video=DSI-1:800x400@60,rotate=180
Both of those changes were necessary to have the display AND the touch inputs rotated and working correctly. Documented here:https://www.raspberrypi.com/documentation/accessories/display.html#rotate-screen-without-a-desktop.
Hope this helps anybody who comes across it.
Thanks for reporting back on it π
About the default values I already knew that they are good normally, but that didn't solve rotation problems. I never really messed with the rotation on Bookworm, but I never knew about that guide, as you are the first one bringing it up (you didn't even find it yourself ^^)