ros wrapper installation is failing on ubuntu 22 #3051
Comments
|
Hi @alonsnir Before installing the RealSense ROS2 wrapper with
|
|
Hi @MartyG-RealSense I have followed the installation instructions step by step
|
|
Thanks very much for the information. If you installed the SDK with the distribution_linux instructions then your SDK version is likely to be 2.54.2. If your SDK is 2.54.2 then the firmware version that should be used with it is 5.15.1.0 rather than the 5.14.0.0 version (which is designed for use with 2.53.1). This is unlikely to be the cause of your wrapper installation problem though. Can you confirm if you configured your Ubuntu repositories using the instructions at https://wiki.ros.org/Installation/Ubuntu/Sources before you used the |
|
I have configured it as https://wiki.ros.org/Installation/Ubuntu/Sources Here is the result of it: |
|
And you are installing on a PC such as a laptop or desktop and not a computer board such as Nvidia Jetson? |
|
It's Intel SoC. Details here https://www.aaeon.com/en/p/subcompact-boards-gene-adp6 |
|
SDK installation problems are more likely to occur on computing devices with an 'exotic' hardware / software configuration, such as industrial boards. In this situation, building librealsense from source code with the libuvc backend or RSUSB backend installation methods can often resolve these problems. This is because these installation types are not dependent on Linux versions or kernel versions and do not require kernel patching. A quick and easy way to perform a libuvc installation is by using a build script with an installation procedure at the link below. https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md |
|
I will give it a try and get back with results. |
|
Yes, if you use the libuvc or RSUSB backend then you can use the default kernel as librealsense will not need to rely on the kernel. |
|
@MartyG-RealSense before I go with the libuvc method, just to clarify that the librealsense install went well. Could you please explain how this will help with the ros wrapper installation? |
|
If your current librealsense installation is working fine then stick with that instead of using libuvc. Considering that you reported Connection failed errors when trying to install the wrapper from Debian packages on the ROS server, you could consider whether there is an internet connectivity problem with downloading the packages from IP address 64.50.236.52 80. This could be due to a firewall or proxy on your computer or a network that the computer is on. You could test for the possibility of a firewall or proxy block on your computer by attempting to build the wrapper from source code instead. |
|
@MartyG-RealSense here I have attempted to build from source, and even I have the SDK installed (from the debain packages) so I guess building the wrapper from sources requires building the librealsense in a same manner, which I did and now the system is up and running. Thank you |
|
@MartyG-RealSense I have a related question please. Why are node names are differ between what I have installed from the ubuntu packages and the one build from sources? built from sources, note the version Installed from packages |
|
The packages installed from the ROS server will be based on what the best librealsense and ROS wrapper version matches were at the time that the packages were created. Whilst librealsense 2.54.2 works with wrapper 4.54.1, this SDK version did not exist at the time that the packages were created. So officially the recommended match for wrapper 4.54.1 is still librealsense 2.54.1.
However, since 2.54.2 was mostly bug-fixes rather than new features, it will still work fine with wrapper 4.54.1 if you install librealsense from source code or non-ROS packages. |
|
Hi @alonsnir Do you require further assistance with this case, please? Thanks! |
I have resolved this by remapping, so nodes run on dev machine (deb packages) vs target machine (build from sources) will refer same topics (e.g. /camera/camera/color/image_raw) and still the question is puzzling |
|
I believe that the discrepancy may be because a change to camera naming - #2857 - was merged into the ROS2 wrapper's source code on August 29 2023. But that change would not be in the package version of the 4.54.1 wrapper, as the package version was released on June 27 2023. The package version of the 4.54.1 will date from its original publishing date of 27 June 2023, but numerous changes have been added to the source code version since then. The package version will be updated when the next ROS wrapper version is published. The camera_name feature is described in the wrapper documentation links below. https://dev.intelrealsense.com/docs/ros2-wrapper#camera-namespace-and-camera-name |
|
@MartyG-RealSense thanks for clarifying |
Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):
All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)
Issue Description
cannot get the ROS2 wrapper to be installed on a new system
Installed 22.04.1 and then changed kernel to 5.15.0-43-generic due to the Reasense SDK requirements
I'm stuck on it a few days already, any help would be much appreciated
The text was updated successfully, but these errors were encountered: