Closed ambersun1234 closed 5 years ago
Hi,
You have a typo at pipe = ts.pipeline()
so its not ts
, its rs
, so change it to: pipe = rs.pipeline()
@eMrazSVK It is just a typo of the article. I've updated the article.
Maybe try to look at this #1091
Does your device get recognized as an USB3 device? You can check with dmesg
command.
@eMrazSVK
Result from dmesg
is as follows
[ 521.694928] usb 2-1: New USB device found, idVendor=8086, idProduct=0b3a
[ 521.694973] usb 2-1: Product: Intel(R) RealSense(TM) Depth Camera 435i
[ 521.694988] usb 2-1: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435i
[ 521.769346] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[ 521.780799] uvcvideo 2-1:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[ 521.790553] uvcvideo 2-1:1.0: Entity type for entity Processing 2 was not initialized!
[ 521.798602] uvcvideo 2-1:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[ 521.808900] uvcvideo 2-1:1.0: Entity type for entity Camera 1 was not initialized!
[ 521.816943] input: Intel(R) RealSense(TM) Depth Ca as /devices/3530000.xhci/usb2/2-1/2-1:1.0/input/input5
Not sure how to extract some useful information from dmesg
, so I just copy some lines that looks improtant. I cannot tell whether the device get recognized as USB3 device or not, so I tried another method.
I get this:
Couldn't open device, some information will be missing
bcdUSB 3.20
bcdDevice 50.ad
bcdUVC 1.50
bcdUVC 1.50
bcdHID 1.10
According to the article, it is clear that realsense get recognized as USB3 device.
Could this type of issue related with realsense's firmware?
@ambersun1234 You can see in the dmesg (after reconnecting the camera) something like New SuperSpeed device. High Speed is USB2 and Super Speed is for USB3. That's how you can find out. But method you used seems legit. Did you use some kind of USB hub or are you directly connecting it to Jetson? Are you using some kind of 3rd party carrier board? Try changing the cable maybe. But thats just some suggestions I would try at first.
@eMrazSVK
I connect realsense
and tx2
via the cable which is provided along with realsense. I didn't use any 3rd party carrier board.
The only thing I have connected is just realsense
and tx2
.
As for the software part, I only install opencv
from source, and update tx2
via jetpack
.
Not sure those operations will effect realsense
or not.
I've got another realsense
here, so maybe I'll just changing the camera and the cable then do AB test to find out the reason instead, and maybe update realsense's firmware
if nothing changed.
@ambersun1234 hello, Based on the input the SDK may not recognize the connected realsense devices:
Assertion `profile->_multistream.get_profiles().siz() > 0' failed.
Please perform the following:
Verify that you have the udev rules installed as required:
./scripts/setup_udev_rules.sh
Build and run SDK's rs-enumerate-devices
tool and share the output.
@ev-mp
I've run ./scripts/setup_udev_rules.sh
rs-enumerate-devices
result is as follows
Device info:
Name : Intel RealSense USB2
Serial Number : 843112073092
Firmware Version : 05.10.13.00
Recommended Firmware Version : 05.11.06.250
Physical Port : /sys/devices/3530000.xhci/usb1/1-2/1-2:1.0/video4linux/video1
Debug Op Code : 15
Advanced Mode : YES
Product Id : 0AD6
Usb Type Descriptor : 2.1
Product Line : D400
Asic Serial Number : 903223053275
Stream Profiles supported by Stereo Module
Supported modes:
stream resolution fps format
Infrared 1 1280x720 @ 6Hz Y8
Infrared 1 1280x720 @ 4Hz Y8
Infrared 1 640x480 @ 30Hz Y8
Infrared 1 640x480 @ 15Hz Y8
Infrared 1 640x480 @ 6Hz Y8
Infrared 1 640x480 @ 4Hz Y8
Infrared 1 480x270 @ 60Hz Y8
Infrared 1 480x270 @ 30Hz Y8
Infrared 1 480x270 @ 15Hz Y8
Infrared 1 480x270 @ 6Hz Y8
Infrared 1 480x270 @ 4Hz Y8
Depth 1280x720 @ 6Hz Z16
Depth 1280x720 @ 4Hz Z16
Depth 640x480 @ 30Hz Z16
Depth 640x480 @ 15Hz Z16
Depth 640x480 @ 6Hz Z16
Depth 640x480 @ 4Hz Z16
Depth 480x270 @ 60Hz Z16
Depth 480x270 @ 30Hz Z16
Depth 480x270 @ 15Hz Z16
Depth 480x270 @ 6Hz Z16
Depth 480x270 @ 4Hz Z16
I connect realsense
with tx2
via provided cable on USB3.0, but it seems that realsense
get recognized as USB2.0.
By the way, I don't have extra realsese
for AB test.
Should I update realsense
's firmware? Because I found some case that may cause error.
Thanks.
For someone who encounter with the same issue.
My realsense
have the firmware version with 5.10.13
, I tried to change the firmware down to 5.10.03
, and everything work like a charm.
Issue Description
I had build the source code from github( f112ed7 ), and successfully installed on tx2, using the following command
When I use pyrealsense2 in python, something weird happened. And by the way i had put
librealsense2.so
&pyrealsense2.cpython-36m-aarch64-linux-gnu.so
under the same working directory. Part of my python code is as followsIt works fine in the first 2 lines, but when it runs to the third line, I got this error
Has someone run into the same problem? Need some help guys!