Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't recgonize T265 fully, RS2_USB_STATUS_NO_DEVICE #2933

Open
Sergiossrr opened this issue Nov 21, 2023 · 1 comment
Open

can't recgonize T265 fully, RS2_USB_STATUS_NO_DEVICE #2933

Sergiossrr opened this issue Nov 21, 2023 · 1 comment

Comments

@Sergiossrr
Copy link

Sergiossrr commented Nov 21, 2023

I run a docker in my centos, to use t265
docker system information :
ubuntu18.04 5.10.0 aarch64

when i plug the t265 ,dmesg

[ 79.490967] usb 1-1.3: USB disconnect, device number 3
[ 86.689409] usb 1-1.1: new high-speed USB device number 4 using xhci-hcd
[ 86.803557] usb 1-1.1: New USB device found, idVendor=03e7, idProduct=2150, bcdDevice= 0.01
[ 86.803659] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 86.803696] usb 1-1.1: Product: Movidius MA2X5X
[ 86.803730] usb 1-1.1: Manufacturer: Movidius Ltd.
[ 86.803761] usb 1-1.1: SerialNumber: 03e72150

lsusb

Bus 002 Device 003: ID 8087:0b37

i find a solution ,but it's not good

vim /etc/udev/rules.d/99-realsense-libusb.rules
udevadm control --reload-rules && udevadm trigger
roslaunch realsense2_camera rs_t265.launch  //after run this order ,udevadm may works

then dmesg

[ 202.285933] usb 1-1.1: USB disconnect, device number 4
[ 202.526166] usb 2-1.1: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd
[ 202.544518] usb 2-1.1: New USB device found, idVendor=8087, idProduct=0b37, bcdDevice=ff.ff
[ 202.544554] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 202.544566] usb 2-1.1: Product: Intel(R) RealSense(TM) Tracking Camera T265
[ 202.544577] usb 2-1.1: Manufacturer: Intel(R) Corporation
[ 202.544588] usb 2-1.1: SerialNumber: 121222110845

lsusb

Bus 002 Device 003: ID 8087:0b37 Intel Corp.

after these orders, i can recgonize t265 but i still can't run roslaunch realsense2_camera rs_t265.launch error inf:

21/11 10:31:11,558 ERROR [547205673344] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_NO_DEVICE
21/11 10:31:11,563 ERROR [547205673344] (librealsense-exception.h:52) Unable to open device interface
[ WARN] [1700533871.569595660]: Device 1/1 failed with exception: Unable to open device interface
[ERROR] [1700533871.569803910]: The requested device with device name containing t265 is NOT found. Will Try again.
21/11 10:31:11,569 WARNING [547205673344] (rs.cpp:310) null pointer passed for argument "device"

then i restart docker ,it works.

I think problem is about udevadm control --reload-rules && udevadm trigger in docker.
Please give me some advice or solutions @MartyG-RealSense

@athnzc
Copy link

athnzc commented Feb 13, 2025

Hello @Sergiossrr , I have a few suggestions: 1) make sure the camera is recognized on the host i.e. outside Docker (e.g. with rs-enumerate-devices, or dmesg) 2) if yes, launch a Docker container with the --privileged parameter (e.g. docker run -it --privileged <image name>:<tag> bash) which gives Docker access to most host resources 3) check if the camera is recognized with rs-enumerate-devices or dmesg (--privileged argument enables using dmesg) 4) check the versions of RealSense SDK and realsense ros wrapper if they are compatible and make sure you have installed them in a consistent way, for example, if you have built the SDK from source, the ROS wrapper should also be built from source. Since you are working on an ARM architecture, building from source is preferable. Also run the ./setup_udev_rules.sh before building the SDK.

Note that using --privileged is generally avoided but I think it will help with debugging the problem. Afterwards you could check the --device option which gives access to a specific host device from the container which I think is more secure than using --privileged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants