-
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
Dependency Issues with ROS2 Wrapper #2369
Comments
This is a continuation of a case begun at IntelRealSense/librealsense#10562 I researched the case again from the beginning. Your Ubuntu version is Bionic (18.04). If you are using the ros2_beta wrapper then its documentation recommends Ubuntu Focal (20.04) for use with Foxy. The same recommendation of 20.04 for Foxy also applies to the previous ros2 branch of the wrapper. |
Hi Marty, NVidia Jetson devices come with Ubuntu 18.04 pre-installed in Jetpack. I have reservations about upgrading my OS, as I'd like to use multiple cameras in my development. As per https://dev.intelrealsense.com/docs/nvidia-jetson-tx2-installation: Would upgrading my OS, and therefore not utilizing the native kernel drivers limit me to using only one camera? |
Whilst a native build of librealsense is the ideal for a multiple camera project, multicam can work with an RSUSB backend build, and Intel made improvements to RSUSB's multicam handling back in SDK 2.35.2, as described at IntelRealSense/librealsense#6467 |
Very good! Thank you for the advice. I think I will try running Jetpack 5.0, as there was reported success from here: IntelRealSense/librealsense#10416 Hopefully the ROS2 Wrapper will be compatible, as Jetpack 5 contains Ubuntu 20.04. |
Hi, @MartyG-RealSense. I've successfully installed ROS2 foxy and the RealSense SDK v.2.50.0 from source on Jetpack 5.01, Ubuntu 20.04, kernel version: 5.10.65-tegra This did resolve one of my issues! All of the dependencies appear to be resolved, but I get the same error message when I try to use This was the output from my latest attempt:
Thank you for all your support so far, you've been a great deal of help! Edit: I've been doing some more research, and this appears to be a problem that is specific to Nvidia Jetson devices. As seen here: ros-perception/vision_opencv#345 The fix that is proposed there has not worked for me, but I believe the issues must be closely related. I'll update if I find a fix! |
Hi @LiquidTurtle1 You are very welcome! Thanks very much for the information about the Jetson-related OpenCV issue. Good luck! |
Hi @MartyG-RealSense, I have made some progress, and I think my build was successful, but I just wanted to verify with you, since I'm having trouble launching the node. I solved my previous issue by running From here, the build finishes cleanly,
However, once I try to launch the node, I receive this error:
This appears to be more of a ROS issue than a RealSense problem. From my research, I may need to install a previous version of OpenCV, or redirect rosdep one more time. If you have any idea or suggestions for this issue, that would be great. Thanks again for your assistance! |
In a couple of non-librealsense ROS cases that had the libcv_bridge.so: cannot open shared object file error, they suggested checking that there was a defined LD_LIBRARY_PATH environment variable. https://stackoverflow.com/questions/40071541/python-import-error-cannot-open-shared-object-file |
This seems like a valuable resource, but I'm not sure I totally understand what this does. I entered
Searching for librealsense2_camera.so which is located in /usr/local/lib As expected, when I close my current terminal, and restart the process in a new one, it starts looking for libcv_bridge.so again. Do you think you'd be able to explain what they are doing in the post you linked so that I might be able to apply it myself? |
I researched your question carefully but was not able to find a reference that was clear enough for me to be confident in sharing. One theory offered about this problem is that if a new version of OpenCV has been installed then it may be causing a conflict with the OpenCV version that is installed by ROS. So it was suggested to remove all OpenCV versions from the computer and use the version that is installed when ROS is installed. |
@MartyG-RealSense I discovered my error! Not following directions! Instead of sourcing the proper directory, as instructed in the Wrapper Installation Guide, I used Everything runs fine now, thank you for the assistance! |
It's no trouble at all. It's great to hear that you found the solution. :) |
Hi I am having the same problem. I am trying to run
Your fix :
doesn't work for me as there is no
|
Issue Description
Hello.
New to ROS2 and new to Linux, apologies for any basic questions or redundancies!
I am looking to implement SLAM using the D435i and L515 in a ROS2 environment. I have been able to run both the RealSense and ROS2 software independently, but I am encountering errors when I attempt to install the ROS2 Wrapper for RealSense.
I installed the latest RealSense SDK with Debian Packages from the Jetson installation guide: https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md
Installing Realsense ROS2 Wrapper:
Using the -r flag with
rosdep install
successfully ignores the dependency errors, but the build is still unsuccessful.Do you have any suggestions?
The text was updated successfully, but these errors were encountered: