realsense-viewer not detecting d435i camera connected to the jetson board. Realsense ros-wrapper not working properly. #10016
Comments
|
Hi @Rafi-UST At the bottom of your ROS launch log it states that the RealSense ROS wrapper was built with 2.49.0 but is running with 2.50.0 (which the 2.3.2 wrapper version is designed specifically for - there was not a wrapper version published for 2.49.0). After the librealsense version is changed (like with your upgrade from 2.49 to 2.50), the RealSense ROS wrapper should be built from source again. If you have been having difficulty with building librealsense from source, the installation guide for Nano at #6964 (comment) shared by a RealSense user may be helpful. |
|
Hi @MartyG-RealSense , thanks for the quick response. If I update the version of librealsense (to v2.50.0) then the |
|
Ideally, a ROS wrapper version should be matched to a specific librealsense version, but that is not possible with 2.49.0 as it does not have a matching ROS wrapper version. In those rare circumstances, if 2.49.0 is the only SDK that will work for you then I would suggest trying to build one wrapper version older - version 2.3.1 that was designed for librealsense 2.48.0. https://github.com/IntelRealSense/realsense-ros/releases/tag/2.3.1 If the option is available to you, I would also recommend a wipe and fresh reinstall of your Nano to ensure that only one librealsense source-code build (2.50.0) is installed on it. |
|
Just days before I tried with the ros wrapper version 2.3.1 and librealsense v2.49.0 but the output form roslaunch was no realsense devices detected. Although now i did a fresh reinstall of librealsense (v2.50.0). The obtained outputs are attached below. roverteam@roverteam-desktop:~$ realsense-viewer roverteam@roverteam-desktop:~$ rs-enumerate-devices |
|
There was a case of the DS5 group_devices is empty error on Nano in #8100 in January 2021. The solution that worked in that particular case was to do a wipe and then install from source code using the earlier mentioned method at #6964 (comment) - did you use that method to perform the 2.50.0 reinstall, please? |
|
I followed the RSUSB backend method to build from source, now relasense-viewer is detecting the camera (Executed the libvuc_installation.sh script to do so). I am able to get the camera feed in rviz. The roverteam@roverteam-desktop:~/catkin_ws$ roslaunch realsense2_camera rs_camera.launch started roslaunch server http://127.0.0.1:43509/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 1dac3f78-5298-11ec-ba6d-00044be62a16 [ INFO] [1638357388.627086359]: Device with physical ID 2-1.1-8 was found. I hope the last warning is nothing to be concerned of? Thanking you in advance @MartyG-RealSense for the quick response and support. |
|
If the camera topics are being published correctly in RViz - which you can check by running it with rosrun rviz rviz - then you can safely ignore the control_transfer returned warnings. |
|
@MartyG-RealSense, yes the camera topics are being published properly.(checked raw and depth). Thanks !!! for the support. |
|
You are very welcome - it's excellent to hear that you succeeded :) |
Issue Description
I have been trying to compile different versions of intel realsense sdk (librealsense v2.50.0 , v2.49.0 , v2.48.0, v2.38.0 etc)from source , but none of the versions (even after successful build )are detecting the realsense camera attached.
Realsense viewer is displaying : Please connect intel realsense device (for all the versions of librealsense mentioned above except for v2.49.0). Even though its working with v2.49.0 , my end goal is to get a feed in rviz using the realsense-ros wrapper (
roslaunch realsense2_camera rs_camera.launch).The output attached below is what i got while executing the roslaunch comand (for v2.49.0 of liibrealsense)
realsense_rviz_camera_launch_output.txt
Tried both jetson hacks method and linux manual installation method for building librealsense from source.
Also attaching the catkin_ws directory structure (completed catkin_make successfully)
catkin_ws_directory_structure.txt
Tagging my colleague also with this issue: @iamrajee
The text was updated successfully, but these errors were encountered: