Upon attempting that update and running the same ROS commands, we get a new error (found in the post subsequent to this one).
Any thoughts on our initial issues with the camera dropping and our new issues after attempting to update the firmware? Thanks very much for your help!
@Peej1818 and @flyingMango, Thank you for reporting this issue to us, and we are sorry you are experiencing this issue. We have been able to reproduce this issue of Realsense dropping out recently and have started working towards a fix. We will post an update soon on this issue.
I appreciate your patience.
@Peej1818 , We are still working on finding the exact cause of the issue and a fix. In the meantime could you try upgrading your realsense camera firmware using the realsense-viewer GUI tool?
You can do this by executing the command realsense-viewer from your terminal and the GUI window should pop up. And on the top right, a prompt would pop up asking you to install the latest firmware if one is available as shown below.
Could you also send the output of the cmd: rs-enumerate-devices -S
The output should look something similar to given below.
Device Name Serial Number Firmware Version
Intel RealSense D435I 040322073254 05.13.00.50
Device info:
Name : Intel RealSense D435I
Serial Number : 040322073254
Firmware Version : 05.13.00.50
Recommended Firmware Version : 05.14.00.00
Physical Port : /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/video4linux/video2
Debug Op Code : 15
Advanced Mode : YES
Product Id : 0B3A
Camera Locked : YES
Usb Type Descriptor : 3.2
Product Line : D400
Asic Serial Number : 039223051361
Firmware Update Id : 039223051361
And ensure you see 3.2 under the Usb Type Descriptor field.
Hi all, I ran some experiments today with the same firmware/librealsense versions (5.14.0.0 and 2.53.1) as @Peej1818, and I was able to reproduce the “no such file or directory” errors in the original post. In my experiments, these errors appear whenever the Realsense camera joins as USB2.1, and disappears if it’s USB3.2.
@Mohamed_Fazil, does the camera show as USB2.1 when you reproduced the errors? @Peej1818 and @flyingMango, when you run rs-enumerate-devices -S, what USB connection does the camera show as? Also, can you share the serial numbers of the robots you’re working on?
Hi @Peej1818, we solved the issue on 1075 in a support call today by opening up Realsense Viewer (run realsense-viewer in a terminal) and performing a firmware update since the camera showed up in “recovery” mode.
@flyingMango Let us know if you’re still seeing these issues on a different robot.
@bshah - Thanks for the suggestions here. I updated the firmware and restarted Stretch. I still observe intermittent disconnections.
Here is the exact error I get:
ERROR: The device has been disconnected!
.
.
.
An exception has been thrown: xioctl(VIDIOC_S_FMT) failed, errno=5 Last Error: Input/output error
.
.
.
Hardware Notification:IR stream start failure, 1.67847e+12,Error,Hardware Error
Here are the details from rs-enumerate-devices:
~$ rs-enumerate-devices -S
Device Name Serial Number Firmware Version
Intel RealSense D435I 134322074171 05.14.00.00
Device info:
Name : Intel RealSense D435I
Serial Number : 134322074171
Firmware Version : 05.14.00.00
Recommended Firmware Version : 05.14.00.00
Physical Port : /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/video4linux/video0
Debug Op Code : 15
Advanced Mode : YES
Product Id : 0B3A
Camera Locked : YES
Usb Type Descriptor : 3.2
Product Line : D400
Asic Serial Number : 134523061170
Firmware Update Id : 134523061170
Hi @srama2512, I just left a response in the other thread. Since your camera still connects in realsense-viewer, the camera isn’t in the “recovery state” that we saw in this thread, so it’s not the same issue.
