-
Notifications
You must be signed in to change notification settings - Fork 4.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
Intel-ROS(RDK) #10341
Comments
Hi @w-1016-Papman The instructions for that ROS2 robotics project link to this ROS2 wrapper: https://github.com/intel/ros2_intel_realsense That wrapper is obsolete though and development on it was stopped before the D455 and L515 camera models were released. It will therefore not be able to work with your cameras. It was also created by Intel developers but not by the Intel RealSense team. The official RealSense ROS2 wrapper that is actively updated and compatible with modern RealSense camera models is at the link below: https://github.com/IntelRealSense/realsense-ros/tree/ros2-beta Regarding why you may have experienced the installation error with the obsolete wrapper, Intel RealSense switched to new secure https:// web addresses in 2021 instead of using the old amazonaws http addresses. |
Your information is very important to me, I will revise it as you said, thank you very much for replying late at night, after all you should be on the other side of the world at this time. |
Don't worry, in my time zone it is early morning now :) |
Hi bro, I'm sorry I might have to disturb you again, but this time I'm already at night. |
As a general rule, if a warning does not have any apparent negative effect on the ROS wrapper's performance (such as being able to smoothly view published RealSense ROS data in the RViz2 interface) then it can likely be safely ignored. If you have completed the build instructions and you have successfully performed a test launch with ros2 launch realsense2_camera rs_launch.py and the topics are viewable in RViz2 without noticable slowdown then I would recommend not worrying about the warning. |
Sorry I haven't finished building yet,so this commend |
As you are using Ubuntu 18.04 with Eloquent, it should be compatible with the current ROS2 wrapper, as shown in the extract below from the wrapper documentation. Switching the Python version to Anaconda could cause problems though. This is because Anaconda installs at a different directory path on the computer to the path used by "ordinary" Python such as Python 3.6. If librealsense was being used with Conda, usually this would be dealt with by defining a PYTHONPATH to the location of Anaconda on the computer, as mentioned at #10002 (comment) The warnng WARNING: ROS_PYTHON_VERSION is unset. Defaulting to 3 suggests to me that the ROS wrapper installation cannot find Anaconda and so is setting the Python version as Python 3 instead. I would recommend not to have the RealSense Viewer opened and streaming data before launching the ROS2 wrapper. The ROS wrapper does not require the Viewer to be active. |
Hi @w-1016-Papman Do you require further assistance with this case, please? Thanks! |
Thanks, not needed for now, I think I might open a new issue to discuss if there are other questions |
Thanks very much for the update! |
Hi dude, I'm trying to install the Intel-ROS2 project while it's easier to work with my D455 camera and L515 camera, I saw it herelink
And I found this document
, when I followed the steps in 'Installation' step by step to run the command in Ubuntu18.04 (kernel version: Linux4.15) terminal, I found that in my rdk_ws folder there is a missing file called Subfolder of 'turtlebot3_ws'.
I don't know if this is because my system version is too low, I would like to ask if you have understood it, and if you know how to deal with this situation.
The terminal prompt fails with this message
Failed to fetch http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo/dists/bionic/InRelease Could not connect to realsense-hw-public.s3.amazonaws.com:80 (52.218.65.73), connection timed out
thanks
The text was updated successfully, but these errors were encountered: