Recommend Jetpack version and ZED version on TX2

Which Jetpack version and ZED sdk version should i use. My Jetson TX2 is:

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.

And the Gstreamer doesn’t work for rtsp

Hi,
Please refer to Jetson Nano FAQ
Q: I have a USB camera. How can I lauch it on Jetson Nano?

See if you can launch the camera through gstreamer pipeline first.

Thank you but in this faq, there is not
Which jetpack should be installed on the page?

thank you but which jetpack version should i install, camera is freezing while run detectnet or etc.

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.

This is ZED Camera

You would already be able to use your ZED camera from V4L API. For example, using gstreamer:

gst-launch-1.0 v4l2src device=/dev/video1 ! xvimagesink

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:

v4l2-ctl -d /dev/video1 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
	Index       : 0
	Type        : Video Capture
	Pixel Format: 'YUYV'
	Name        : YUYV 4:2:2
		Size: Discrete 2560x720
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.067s (15.000 fps)
		Size: Discrete 1344x376
			Interval: Discrete 0.010s (100.000 fps)
			Interval: Discrete 0.017s (60.000 fps)
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.067s (15.000 fps)
		Size: Discrete 3840x1080
			Interval: Discrete 0.033s (30.000 fps)
			Interval: Discrete 0.067s (15.000 fps)
		Size: Discrete 4416x1242
			Interval: Discrete 0.067s (15.000 fps)

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
...
`
1 Like

Thank Honey Patouceul for sharing experience.

Without install ZED SDK, it was working well, and now that code you give

gst-launch-1.0 v4l2src device=/dev/video1 ! xvimagesink
is working but little bit slow.

And i have a ZED flash disk.
should i install that SDK on the flash disk or new SDK?

and

sadsavunma@sadsavunma-desktop:~$ jetson_release -v
 - NVIDIA Jetson TX2
   * Jetpack 4.4.1 [L4T 32.4.4]
   * NV Power Mode: MAXP_CORE_ARM - Type: 3
   * jetson_stats.service: active
 - Board info:
   * Type: TX2
   * SOC Family: tegra186 - ID:24
   * Module: P3310-1000 - Board: UNKNOWN
   * Code Name: quill
   * Boardids: 3310:0000:A0
   * CUDA GPU architecture (ARCH_BIN): 6.2
   * Serial Number: 0323117055388
 - Libraries:
   * CUDA: 10.2.89
   * cuDNN: 8.0.0.180
   * TensorRT: 7.1.3.0
   * Visionworks: 1.6.0.501
   * OpenCV: 4.1.1 compiled CUDA: NO
   * VPI: 0.4.4
   * Vulkan: 1.2.70
 - jetson-stats:
   * Version 3.0.2
   * Works on Python 3.6.9
sadsavunma@sadsavunma-desktop:~$

it was showing like here:

i installed the ZED SDK that you suggest
here

and checks the camera
v4l2-ctl -d /dev/video1 --list-formats-ext
with Putty it shows

but while check on Jetson
i have to connect zed camera via micro usb, because zed does not work via usb duplicator

it shows this and found a new way connect with normal USB and check and this image is coming, even check on Putty

and while run the ZED_Diagnostic
it shows
Camera Test:
ZED camera make sure the camera is plugged in or try another USB 3.0 port

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.

1 Like

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.

1 Like

Thank you for your help