because while i run detectnet.py with /dev/video1 it shows an error about not capture (don’t remember clearly right now sorry.) and after that the camera is open and detecting objects but after that camera is freezing.
Hi,
You may try the latest JP4.4.1(r32.4.4). Generally USB cameras support YUV422 such as UYVY, YUYV. If you see the formats in v4l2-ctl command, you can try to launch the camera through gst-launch-1.0.
If you want to install the ZED SDK, you would download it from StereoLabs. Note there is a dedicated section for Jetsons.
For JetPack4.4, you may try this.
Additional note:
The modes listed look surprizing. In my case I get:
You may have to update camera firmware. Do that from host with a recent ZED SDK.
Also be sure not to go through a USB hub limiting bandwith nor micro-USB port. Try to have ZED only in the full size USB connector, and connect keyboard and mouse through a USB hub into micro-USB or remote command from ssh.
In my case (using a Xavier NX here):
lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 10000M
|__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 10000M
|__ Port 1: Dev 4, If 0, Class=Video, Driver=uvcvideo, 5000M
|__ Port 1: Dev 4, If 1, Class=Video, Driver=uvcvideo, 5000M
...
`
Micro-USB port of TX2 is USB2 only. Can be ok for mouse and keyboard, but ZED requires much more bandwidth so you should reserve full size USB port being USB3 for ZED only.
The ZED SDK is not mandatory, but it gives some dedicated tools and libraries.
thank you for your help.
Connect zed to jetson own normal usb port its working but when the camera is opening terminal shows error and i close the right camera of zed and works clearly
The image freezes when I raise my hand from the right camera.
And check the camera formats still same thing appeared
You may post the errors you’re seeing.
Note that gstreamer logs some messages even in normal case (and can issue tons if you play with GST_DEBUG, but that’s out of scope).
I’d suggest to first try with low resolution and framerate. For example :
gst-launch-1.0 v4l2src device=/dev/video1 ! video/x-raw, format=YUY2, width=1344, height=376, framerate=15/1 ! xvimagesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
I can see both images side by side as ZED camera provides both images stitched into a large one, until I interrupt with Ctrl-C:
^Chandling interrupt.
Interrupt: Stopping pipeline ...
Execution ended after 0:00:21.005102485
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...
Do you see anything different ?
Do you mean the issue is only related to luminosity of right camera ? It would help to get the specific error messages.
It might be a HW issue with the camera (did you uprgrade firmware from host ?), signal issue with cable or connector, or power issue since ZED is only powered from USB (if you have other power consuming devices, you may try to unplug these for testing).
I don’t have such problem with my ZED and NX, but I remember some years ago with TX1/TX2 it was sometimes required to disable usbcore_autosuspend from boot for not having troubles with USB. Not sure this is still relevant for JP4.4.