Cannot run D435i or T265 camera. "failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS" #1408

hamsterasu · 2020-09-20T17:21:44Z

Hi,
I followed the instructions to install debian package of the ROS wrapper using sudo apt-get install ros-melodic-realsense2-camera. From what is said on the README, it says that by installing the debian package,

This will install both realsense2_camera and its dependents, including librealsense2 library.

So from my understanding of this, I do not have to install anything else, ie. librealsense2.

However, when I run roslaunch realsense2 rs_camera.launch while D435i is connected, i get this error:

 21/09 00:29:45,089 ERROR [140173394786048] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 21/09 00:29:45,110 WARNING [140173428356864] (rs.cpp:304) null pointer passed for argument "device"
[ WARN] [1600619385.110816284]: Device 1/1 failed with exception: failed to set power state
[ERROR] [1600619385.110863734]: The requested device with  is NOT found. Will Try again.
[ INFO] [1600619391.122466749]:  
 21/09 00:29:51,127 ERROR [140173403178752] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 21/09 00:29:51,149 WARNING [140173428356864] (rs.cpp:304) null pointer passed for argument "device"
[ WARN] [1600619391.149189828]: Device 1/1 failed with exception: failed to set power state
[ERROR] [1600619391.149264654]: The requested device with  is NOT found. Will Try again.

When I run dmesg, i see this:

[ 8160.342817] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/input/input30
[ 8160.344196] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[ 8160.346105] uvcvideo 1-12:1.3: Entity type for entity Processing 7 was not initialized!
[ 8160.346109] uvcvideo 1-12:1.3: Entity type for entity Extension 8 was not initialized!
[ 8160.346112] uvcvideo 1-12:1.3: Entity type for entity Camera 6 was not initialized!
[ 8160.426289] hid-sensor-hub 0003:8086:0B3A.0008: No report with id 0xffffffff found
[ 8160.528972] audit: type=1107 audit(1600619701.599:132): pid=864 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal"  bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.15" mask="receive" pid=8840 label="snap.spotify.spotify" peer_pid=874 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[ 8165.584965] hid-sensor-hub 0003:8086:0B3A.0008: No report with id 0xffffffff found
[ 8169.170915] hid-sensor-hub 0003:8086:0B3A.0008: No report with id 0xffffffff found

When I run roslaunch realsense2_camera rs_t265.launch for t265 camera, i also get an error:

 21/09 00:59:07,679 ERROR [139917231736576] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 21/09 00:59:07,679 ERROR [139917231736576] (tm-boot.h:42) Failed to open T265 zero interface
[ WARN] [1600621149.688932423]: No RealSense devices were found!
 21/09 00:59:15,700 ERROR [139917231736576] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 21/09 00:59:15,700 ERROR [139917231736576] (tm-boot.h:42) Failed to open T265 zero interface

I have attached the full console messages for your viewing.

Full console messages:
d435i_dmesg.txt
d435i_error.txt
t265_dmesg.txt
t265_roslaunch.txt

The text was updated successfully, but these errors were encountered:

RealSenseSupport · 2020-09-23T01:56:03Z

@hamsterasu Could you please try if you can run realsenseviewer and start streaming with D435i and T265 successfully? Also what's your platform? And kernel version? Thanks!

hamsterasu · 2020-09-23T09:13:16Z

it says "realsense-viewer: command not found" when i run realsense-viewer

My kernel version is 5.4.0-47-generic. Platform is Intel® Core™ i7-10875H CPU

RealSenseSupport · 2020-09-24T05:53:21Z

@hamsterasu I reproduced the issue and found one solution. Could you please check if you have 99-realsense-libusb.rules under /etc/udev/rules.d/ ? If not, please copy https://github.com/IntelRealSense/librealsense/blob/master/config/99-realsense-libusb.rules to /etc/udev/rules.d/ before connect the cameras. After that you can connect the camera and execute the ros launch.

hongtaowu67 · 2020-09-26T18:03:48Z

It works in my case after including the 99-realsense-libusb.rules in /etc/udev/rules.d/.

RealSenseSupport · 2020-09-27T01:04:01Z

@hongtaowu67 Thanks for your feedback! Glad to hear this works for you.

hamsterasu · 2020-09-27T10:43:34Z

@RealSenseSupport Your solution works for me too! Thanks! I am closing this issue

Shunichi09 · 2020-10-01T07:14:35Z

@RealSenseSupport I got the same problem when I was using docker.
I also tried to solve it by your suggestion (i.e. including the 99-realsense-libusb.rules in /etc/udev/rules.d/.) but it did not work for me...
Are there any solutions ??

I checked realsense-viewer did work and got RGB-D images, although there was error message.
Finally, I updated the firmware of realsense to 5.12, I got same error.

 01/10 17:41:38,038 ERROR [139670256056064] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 01/10 17:41:38,039 ERROR [139670256056064] (fw-update-device.cpp:128) access failed for 8086:adb uid: 2-7-10
 01/10 17:41:38,039 WARNING [139670256056064] (rs.cpp:304) null pointer passed for argument "device"

running command

$ roslaunch realsense2_camera rs_camera.launch

error message

[ INFO] [1601571623.360312063]: RealSense ROS v2.2.16
[ INFO] [1601571623.360333411]: Built with LibRealSense v2.37.0
[ INFO] [1601571623.360341901]: Running with LibRealSense v2.37.0
01/10 16:08:00,157 ERROR [140156020442880] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 01/10 16:08:00,178 WARNING [140156054013696] (rs.cpp:304) null pointer passed for argument "device"
[ WARN] [1601568480.178749109]: Device 1/1 failed with exception: failed to set power state
[ERROR] [1601568480.178776222]: The requested device with  is NOT found. Will Try again.

Iko-Git · 2020-10-23T13:23:28Z

@hamsterasu I reproduced the issue and found one solution. Could you please check if you have 99-realsense-libusb.rules under /etc/udev/rules.d/ ? If not, please copy https://github.com/IntelRealSense/librealsense/blob/master/config/99-realsense-libusb.rules to /etc/udev/rules.d/ before connect the cameras. After that you can connect the camera and execute the ros launch.

solved my issue too thanks, but I wonder shouldn't such a file be default installed with realsense package

camilorequena · 2020-11-02T14:20:07Z

@hamsterasu I reproduced the issue and found one solution. Could you please check if you have 99-realsense-libusb.rules under /etc/udev/rules.d/ ? If not, please copy https://github.com/IntelRealSense/librealsense/blob/master/config/99-realsense-libusb.rules to /etc/udev/rules.d/ before connect the cameras. After that you can connect the camera and execute the ros launch.

solved my issue too thanks, but I wonder shouldn't such a file be default installed with realsense package

This solved my issue too. Seems to be some kind of bug.

HWeigo · 2020-12-05T14:00:07Z

@hamsterasu I reproduced the issue and found one solution. Could you please check if you have 99-realsense-libusb.rules under /etc/udev/rules.d/ ? If not, please copy https://github.com/IntelRealSense/librealsense/blob/master/config/99-realsense-libusb.rules to /etc/udev/rules.d/ before connect the cameras. After that you can connect the camera and execute the ros launch.

Thanks! Mine is solved too

EricWiener · 2021-01-26T23:41:44Z

@RealSenseSupport I got the same problem when I was using docker.
I also tried to solve it by your suggestion (i.e. including the 99-realsense-libusb.rules in /etc/udev/rules.d/.) but it did not work for me...
Are there any solutions ??

I checked realsense-viewer did work and got RGB-D images, although there was error message.
Finally, I updated the firmware of realsense to 5.12, I got same error.
 01/10 17:41:38,038 ERROR [139670256056064] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 01/10 17:41:38,039 ERROR [139670256056064] (fw-update-device.cpp:128) access failed for 8086:adb uid: 2-7-10
 01/10 17:41:38,039 WARNING [139670256056064] (rs.cpp:304) null pointer passed for argument "device"
running command
$ roslaunch realsense2_camera rs_camera.launch
error message
[ INFO] [1601571623.360312063]: RealSense ROS v2.2.16
[ INFO] [1601571623.360333411]: Built with LibRealSense v2.37.0
[ INFO] [1601571623.360341901]: Running with LibRealSense v2.37.0
01/10 16:08:00,157 ERROR [140156020442880] (handle-libusb.h:51) failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS
 01/10 16:08:00,178 WARNING [140156054013696] (rs.cpp:304) null pointer passed for argument "device"
[ WARN] [1601568480.178749109]: Device 1/1 failed with exception: failed to set power state
[ERROR] [1601568480.178776222]: The requested device with  is NOT found. Will Try again.

Did you ever figure this one out?

Shunichi09 · 2021-01-27T04:01:35Z

In my case, when launching the container, using privileged option and -v "/dev:/dev" volume option solved this problem.

Like

docker run --gpus all -d \
    --name container_name \
    -v "/dev:/dev" \
    --privileged \
    --rm \
    image \
    tail -f /dev/null

pringithub · 2021-01-31T23:56:07Z

I needed to add the 99-* file as well for realsense to work.

Using Ubuntu 18.04 with ROS melodic. Seems this issue has been going on for months .. update the apt package?

billusbillus · 2021-04-28T15:00:51Z

Hi, I'm facing the same error and adding 99-realsense-libusb.rules under /etc/udev/rules.d/ didn't work for me.

I can see uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435 when I run dmesg.

I'm working on ubuntu 18.04 and installed with apt-get install ros-melodic-realsense2-camera. Also, Idk if it might be helpful, but I can't run rs-enumerate-devices. Got command not found.

Could you help me ? Thanks for time !

EDIT : Anyway, installing through the realsense distrib seems to install correct rules and make it works.

yayashuxue · 2021-06-22T05:36:28Z

I needed to add the 99-* file as well for realsense to work.

Using Ubuntu 18.04 with ROS melodic. Seems this issue has been going on for months .. update the apt package?

Mine still fail to work after adding it... I am also using 18.04 with ROS melodic. Can you provide me the steps you take? Thanks!!

arikus1 · 2022-03-21T03:27:12Z

i had a same mistakes,
i use rpi 4 4gb , t265 and kermel version = 5.13.0-1017-raspi ,
i just want to run rs-data-collect and its end like this
realsense error calling rs2_create_device(info_list:0xaaaaef733d50, index:0): unable to open device interface

i ruun a couple command another rs- and its still the same traouble that unable to open device intervace .
can some one help me pls what should i do

im from asia n my english was so bad im sory im a newbie with program

@MartyG-RealSense

MartyG-RealSense · 2022-03-22T08:03:47Z

Hi @arikus1 Your English is good, so don't worry. :)

The T265 Tracking Camera does not have built in depth sensing and so it would not work with some of the example programs. The link below has a list of the examples that can work with T265.

https://github.com/IntelRealSense/librealsense/blob/master/doc/t265.md#examples-and-tools

arikus1 · 2022-03-23T09:11:53Z

hi @MartyG-RealSense thank u for helping me , i wish u all the best broo , ur answer is a miracle for newbie like me 🙏

MartyG-RealSense · 2022-03-23T09:57:13Z

You are very welcome, @arikus1 - I am pleased that I could help :)

goyalvarun02 · 2022-08-26T06:09:23Z

@hamsterasu I reproduced the issue and found one solution. Could you please check if you have 99-realsense-libusb.rules under /etc/udev/rules.d/ ? If not, please copy https://github.com/IntelRealSense/librealsense/blob/master/config/99-realsense-libusb.rules to /etc/udev/rules.d/ before connect the cameras. After that you can connect the camera and execute the ros launch.

Hi ,

I tried the above but still it failed.

I am using docker on VM (ubuntu 18.04) .

MartyG-RealSense · 2022-08-26T06:18:24Z

Hi @goyalvarun02 Please create a new case for your problem using the green New Issue button on the front page of this support forum. Thanks!

https://github.com/IntelRealSense/librealsense/issues

goyalvarun02 · 2022-08-26T06:25:47Z

Realsense d435i is not detected on docker #10829

Created :-)

YangYB0624 · 2024-03-13T15:24:10Z

I copied https://github.com/IntelRealSense/librealsense/blob/master/config/99-realsense-libusb.rules to /etc/udev/rules.d/, however, I got another error:

13/03 23:18:38,690 WARNING [140163864020736] (messenger-libusb.cpp:66) bulk_transfer returned error, endpoint: 0x1, error: Resource temporarily unavailable, err. num: 11

hamsterasu changed the title ~~Cannot run~~ Cannot run D435i or T265 camera. "failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS" Sep 20, 2020

RealSenseSupport added the melodic label Sep 23, 2020

RealSenseSupport mentioned this issue Sep 24, 2020

RealSenseNodeFactory segfault during launch #1228

Closed

hamsterasu closed this as completed Sep 27, 2020

Shunichi09 mentioned this issue Oct 1, 2020

Failed to update Firmware 05.11.11.100 to 05.12.7.100 IntelRealSense/librealsense#7463

Closed

jarvisschultz mentioned this issue Oct 2, 2020

udev rules should be bundled with ROS packages #1426

Closed

MartyG-RealSense mentioned this issue Nov 18, 2020

Error in upsuare bord 2 #1507

Closed

sktometometo mentioned this issue Dec 29, 2020

add t265 odometry support 708yamaguchi/jsk_robot#3

Merged

locvu98 mentioned this issue Mar 19, 2021

realsense-viewer: command not found on Raspberry Pi 4B #1766

Closed

MartyG-RealSense mentioned this issue Apr 2, 2021

GL CallBack GL Error after running realsense-viewer IntelRealSense/librealsense#8705

Closed

fushi219 mentioned this issue Apr 20, 2021

Device not found when mapping T265 on mac into ubuntu docker #1816

Open

lmark1 mentioned this issue Apr 27, 2021

Add Realsesne D435 installation instructions larics/mood_ros#2

Closed

nabulsi mentioned this issue Jul 19, 2021

MACOSX_RPATH is not specified for the following targets: realsense2-gl IntelRealSense/librealsense#9422

Closed

Brac24 mentioned this issue Jan 8, 2022

Can't Access RealSense D435i NVIDIA-ISAAC-ROS/isaac_ros_visual_slam#11

Closed

HripsimeS mentioned this issue Sep 21, 2022

Failed to load nodelet '/camera/realsense2_camera of type realsense2_camera/RealSenseNodeFactory to manager realsense2_camera_manager' #2481

Closed

haashimrehan mentioned this issue May 13, 2023

Realsense camera ROS drivers with the Jetson TX2 MacRover/Rover#33

Closed

brunofavs mentioned this issue Apr 3, 2024

Implement Intel RealSense T265 to prepare for data collection at INESC 2024 (zaubot) lardemua/atom#909

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot run D435i or T265 camera. "failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS" #1408

Cannot run D435i or T265 camera. "failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS" #1408

hamsterasu commented Sep 20, 2020

RealSenseSupport commented Sep 23, 2020

hamsterasu commented Sep 23, 2020 •

edited

Loading

RealSenseSupport commented Sep 24, 2020

hongtaowu67 commented Sep 26, 2020 •

edited

Loading

RealSenseSupport commented Sep 27, 2020

hamsterasu commented Sep 27, 2020

Shunichi09 commented Oct 1, 2020 •

edited

Loading

Iko-Git commented Oct 23, 2020

camilorequena commented Nov 2, 2020

HWeigo commented Dec 5, 2020

EricWiener commented Jan 26, 2021

Shunichi09 commented Jan 27, 2021

pringithub commented Jan 31, 2021

billusbillus commented Apr 28, 2021 •

edited

Loading

yayashuxue commented Jun 22, 2021

arikus1 commented Mar 21, 2022 •

edited

Loading

MartyG-RealSense commented Mar 22, 2022

arikus1 commented Mar 23, 2022

MartyG-RealSense commented Mar 23, 2022

goyalvarun02 commented Aug 26, 2022

MartyG-RealSense commented Aug 26, 2022

goyalvarun02 commented Aug 26, 2022

YangYB0624 commented Mar 13, 2024

Cannot run D435i or T265 camera. "failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS" #1408

Cannot run D435i or T265 camera. "failed to open usb interface: 0, error: RS2_USB_STATUS_ACCESS" #1408

Comments

hamsterasu commented Sep 20, 2020

RealSenseSupport commented Sep 23, 2020

hamsterasu commented Sep 23, 2020 • edited Loading

RealSenseSupport commented Sep 24, 2020

hongtaowu67 commented Sep 26, 2020 • edited Loading

RealSenseSupport commented Sep 27, 2020

hamsterasu commented Sep 27, 2020

Shunichi09 commented Oct 1, 2020 • edited Loading

Iko-Git commented Oct 23, 2020

camilorequena commented Nov 2, 2020

HWeigo commented Dec 5, 2020

EricWiener commented Jan 26, 2021

Shunichi09 commented Jan 27, 2021

pringithub commented Jan 31, 2021

billusbillus commented Apr 28, 2021 • edited Loading

yayashuxue commented Jun 22, 2021

arikus1 commented Mar 21, 2022 • edited Loading

MartyG-RealSense commented Mar 22, 2022

arikus1 commented Mar 23, 2022

MartyG-RealSense commented Mar 23, 2022

goyalvarun02 commented Aug 26, 2022

MartyG-RealSense commented Aug 26, 2022

goyalvarun02 commented Aug 26, 2022

YangYB0624 commented Mar 13, 2024

hamsterasu commented Sep 23, 2020 •

edited

Loading

hongtaowu67 commented Sep 26, 2020 •

edited

Loading

Shunichi09 commented Oct 1, 2020 •

edited

Loading

billusbillus commented Apr 28, 2021 •

edited

Loading

arikus1 commented Mar 21, 2022 •

edited

Loading