-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Lots of "Failed to read busnum/devnum" warnings polluting the terminal #2754
Comments
Hi @martinakos Failed to read busnum/devnum is a very rarely occurring warning that has typically been associated with using RealSense on a single-board computer where the USB port is a USB OTG micro-sized port instead of a full-sized port. As you experience this warning with ROS2 Humble but not with ROS Noetic though, this suggests that the problem is not related to your computer hardware. Do the warnings still occur in Humble if you reset the camera at launch with initial_reset:=true
|
Yes, they do. |
If you are running Humble in a Docker container and the messages occur, is your Noetic installation on the host that doesn't have the messages not in a Docker container? |
I have Noetic installed in ubuntu 20.04 in my laptop (the host). I run ros2 humble on a docker because it requires ubuntu 22.04 and I can't install it in the host OS. |
There was a Humble case a few weeks ago at #2730 where a RealSense ROS user was experiencing the busnum/devnum message. Setting RViz to use compressed data - see #1510 (comment) - improved their performance. |
rviz2 doesn't show the compressed option when selecting an image topic (I think the issue you refer to is for ros1). In any case, the warning message is displayed before I run rviz2 |
Would it be possible for you to change the logging level to mute WARNING type messages, or do you need to look for other types of WARNING message when checking the log? |
I'd prefer not have to mute all warning messages. do you know how to mute that warning message only? |
Individual message types cannot be excluded from the logging level, so the only alternative may be to build a customized version of librealsense from source code where you have edited line 1203 of the file backend-hid.cpp to remove the busnum/devnum message. https://github.com/IntelRealSense/librealsense/blob/master/src/linux/backend-hid.cpp#L1203 |
I was checking who wrote that piece of code and I saw in the commit messages Metadata fields parsing and extraction Could we ask the developers that wrote that code, (@dorodnic, @ev-mp) what are these checks doing and if it's safe to ignore them? |
I have highlighted your question to my Intel RealSense colleagues. Thanks very much for your patience. |
Hi @martinakos My colleagues agreed with my suggestion to edit the source code to remove the busnum/devnum message, and added that it would be safe to ignore the warning as you did not find that it impacted the actual performance. In regard to metadata extraction, they said that you can use the Realsense Viewer’s metadata window to confirm if the desired metadata attribute(s) is supported. or use the following example code for reference. |
Ok. thanks. |
Hi @martinakos Do you require further assistance with this case, please? Version 2.54.1 of librealsense is now available at the link below. https://github.com/IntelRealSense/librealsense/releases/tag/v2.54.1 The release notes, with an extensive list of enhancements and bug-fixes, are available here: https://github.com/IntelRealSense/librealsense/wiki/Release-Notes#release-2541 |
I have updated to the latest librealsense in my host machine and rebuilt realsense2_camera from source with ROS1 noetic and I still get the warnings. |
Thanks very much @martinakos |
I'm running on ros2 humble. I launch the camera with
ros2 launch realsense2_camera rs_launch.py
and I get this output
I get lots of this "Failed to read busnum/devnum" warnings. I'm showing the output of rs_launch.py to make diagnosis easier as it's a provided launch. In the specific launch I'm writing I get event more of this Failed to read busnum/devnum" warnings and it makes hard to see other messages I'm interested in. The driver seems to be working normally though.
Note I'm running humble inside a docker with Ubuntu 22.04 LTS. In my host I have Ubuntu 20.04 with ROS Noetic and if I run
roslaunch realsense2_camera rs_camera.launch
with the same camera connected I don't get any of the warnings above.
I've checked other issues with this warning message but none of their suggestions worked to eliminate this warning. Do you have any suggestions to eliminate this warning?
The text was updated successfully, but these errors were encountered: