We are using a dual cameras AR0230 connected via USB. One of the cameras intermittently gets “stuck” and we have no way of reproducing the issue. This doesn’t happen often, but when it does, we typically swap out either the USB cable, the camera, or both, or we reboot the device. And one out of the 4 methods we use will typically fix the issue and it never occurs again. This issue happens across all of our devices, we have multiple Jetson Xavier machines, but it’s hard to diagnose since we can’t reproduce the error.
Can anyone help me out?
Please share information of v4l2-ctl --list-formats-ext -d /dev/videoX for reference. For launching v4l2 source, we support gstreamer and jetson_multimedia_api. Which frameworks do you use?
We are using gstreamer framework. And this is the v4l2
@DaneLLL any ideas or suggestions?
Please refer to Jetson Nano FAQ
Q: I have a USB camera. How can I launch it on Jetson Nano?
And see if you can launch the cameras in gstreamer commands.
If the cameras are USB2 cameras, it is possible to hit bandwidth constraint as discussed in
connected more than two usb cameras problem on deepstream-app (Jetson Nano Dev Kit) - #12 by DaneLLL
how do you launch the cameras in gstreamer commands? @DaneLLL
THis is a huge issue for our company because we have nearly 1000 camera systems out in the field using AR0230 and the nvidia jetson. We can’t simply switch to a different image sensor. Is there any other solutions?
we are running nvidia jetson xavier nx
This is constraint of hardware bandwidth. Please use USB3 cameras so that you can have 5Gbps bandwidth.
What if using a USB3 camera isn’t an option for us? We have deployed hundreds of cameras already in the field and to go back to swap out the cameras would be a logistical nightmare.
Are there any other solutions possible via a driver?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.