I’m trying to stream 2 B0196 USB/UVC cameras over UV4L on a Raspberry Pi 3B+.
After installing the related UV4L Raspicam and UVC modules (Raspicam module seems to be required), the Pi recognizes the devices and I can start the UV4L server but the stream (1 camera) contains no image(s).
Same result after removing 1 camera.
I see some info on the web regarding UVC and Linux, but not Raspbian. And I’m unsure how to get both cameras working - docs on the web are not clear.
The uvc-utils module is installed with the aforementioned modules, as per the Arducam docs.
Note that I have had success with the RPi camera without UVC, so I am a bit familiar with UV4L.
Any online references / resources I can look at, or suggestions on how to troubleshoot this?
Seems UV4L doesn’t work properly on a Pi without the uv4l-raspicam module, even though I’m using uvc.
So, using the latest RPI image on a 3B+, I installed the UV4L core, server and raspicam related modules as per the instructions on the UV4L project site.
I then installed the uv4l-uvc module.
I confirmed module responses on your uvc page. With 2 B0196 connected, using ‘lsusb’ I can see both B0196s, and with ‘v4l2-ctl --list-devices’ I can see many devices, including dev/video0/1 and dev/video2/3.
I started the UV4L server using the uvc driver with the following (basic) command…
uv4l –driver uvc –device-id 001:004
Loading the Pi’s IP into a browser, I can see the UV4L info screen, but when I load /stream, or /stream/video.h264, I see a blank screen. No stream.
After attempting to view in the browser, ‘v4l2-ctl --list-devices’ no longer raises the devices.
Given these challenges, I haven’t yet attempted to troubleshoot a second B0196. Just trying to get one working first.
Seems UV4L doesn’t work properly on a Pi without the uv4l-raspicam module, even though I’m using uvc.
So, using the latest RPI image on a 3B+, I installed the UV4L core, server and raspicam related modules as per the instructions on the UV4L project site at https://www.linux-projects.org/uv4l/installation/
Seems UV4L doesn’t work properly on a Pi without the uv4l-raspicam module, even though I’m using uvc.
So, using the latest RPI image on a 3B+, I installed the UV4L core, server and raspicam related modules as per the instructions on the UV4L project site at https://www.linux-projects.org/uv4l/installation/
Seems UV4L doesn’t work properly on a Pi without the uv4l-raspicam module, even though I’m using uvc.
So, using the latest RPI image on a 3B+, I installed the UV4L core, server and raspicam related modules as per the instructions on the UV4L project site at https://www.linux-projects.org/uv4l/installation/
Thanks bin,
I have removed the links in an effort to get this posted.
Seems UV4L doesn’t work properly on a Pi without the uv4l-raspicam module, even though I’m using uvc.
So, using the latest RPI image on a 3B+, I installed the UV4L core, server and raspicam related modules as per the instructions on the UV4L project site.
I then installed the uv4l-uvc module.
I confirmed module responses on your ‘UVC Cameras on Linux – Command Line Operations’ page. With 2 B0196 connected, using ‘lsusb’ I can see both B0196s, and with ‘v4l2-ctl --list-devices’ I can see many devices, including dev/video0/1 and dev/video2/3.
I started the UV4L server using the uvc driver with the following (basic) command…
‘uv4l –driver uvc –device-id 001:004’
Loading the Pi’s IP into a browser, I can see the UV4L info screen, but when I load /stream, or /stream/video.h264, I see a blank screen. No stream.
After attempting to view in the browser, ‘v4l2-ctl --list-devices’ no longer raises the devices.
Given these challenges, I haven’t yet attempted to troubleshoot a second B0196. Just trying to get one working first.
The device-id value (0c45:6366) is incorrect (in my experience). It should be the bus:dev values, so device-id 001:009. There are other device-[] options but I haven’t tried those.