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

rs-enumerate-devices /realsense-viewer not working after launching realsense2_camera node #2016

Closed
joelbudu opened this issue Aug 2, 2021 · 7 comments
Labels

Comments

@joelbudu
Copy link

joelbudu commented Aug 2, 2021

rs-enumerate-devices /realsense-viewer doesn't seem to be working after launching a realsense2_camera node. It only works after physically disconnecting and reconnecting the USB cable.

@MartyG-RealSense
Copy link
Collaborator

Hi @joelbudu RealSense programs currently streaming with the camera should be closed before running another RealSense program, because the program that was run first will be blocking access to other applications using the streams that it currently has a 'claim' on.

Unplugging the camera from the USB ports stops all currently active streams and so makes all streams available to use for the next program that enables those streams and 'claims' them.

@joelbudu
Copy link
Author

joelbudu commented Aug 2, 2021

Dear @MartyG-RealSense . This issue happens even after closing the running application.

@MartyG-RealSense
Copy link
Collaborator

I have seen a couple of past cases similar to your situation, where the Viewer does not work after first running RealSense ROS. The link below has one such case.

#1187 (comment)

Since librealsense and the RealSense ROS wrapper operate independently and you do not need the Viewer open in order to use the ROS wrapper, a simple workaround may be to not use librealsense programs in sessions where you are using RealSense ROS. The RealSense ROS wrapper publishes a topic called /diagnostics that you can check for camera information.

@MartyG-RealSense
Copy link
Collaborator

Hi @joelbudu Do you require further assistance with this case, please? Thanks!

@joelbudu
Copy link
Author

joelbudu commented Aug 9, 2021

I did realize based on the links you shared that these is some disparity between the version of librealsense installed and the realsense-ros package I have installed.

I tried to build the latest realsesnse-ros from source but I'm receiving this warning now:

[ INFO] [1628513177.458658821]: RealSense ROS v2.3.1
[ INFO] [1628513177.458721123]: Built with LibRealSense v2.45.0
[ INFO] [1628513177.458755288]: Running with LibRealSense v2.48.0
[ WARN] [1628513177.458783389]: ***************************************************
[ WARN] [1628513177.458803737]: ** running with a different librealsense version **
[ WARN] [1628513177.458824719]: ** than the one the wrapper was compiled with! **
[ WARN] [1628513177.458848879]: ***************************************************

I'm not sure how to fix this.

@joelbudu
Copy link
Author

joelbudu commented Aug 9, 2021

Update: @MartyG-RealSense Apparently I had another librealsense2 package installed: ros-melodic-librealsense2 that was also creating a conflict. With matching librealsense2 versions this works fine and there is no issue. Thank you very much for the guidance.

@joelbudu joelbudu closed this as completed Aug 9, 2021
@MartyG-RealSense
Copy link
Collaborator

Great news @joelbudu that you found a solution - thanks very much for the update :)

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

No branches or pull requests

2 participants