-
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
[ROS 1] Stops after publishing a few images while consuming 100% CPU in Jetson AGX Xavier ( JetPack 4.6.3) #2646
Comments
Hi @ravijo There are known issues with enabling pointcloud on Jetson devices specifically in the ROS1 wrapper, as described at #1967 A workaround is to launch with rs_rgbd.launch instead of rs_camera.launch.
Before this launch is performed, support for an RGBD launch in the ROS1 wrapper must first be installed by using the command below in the Ubuntu terminal for your particular ROS version (Melodic in this case). Kinetic Melodic Noetic With the rs_rgbd launch file you do not need to enable the pointcloud in the roslaunch instruction, as it publishes one by default. It generates a point cloud that is published at depth_image_proc Information about depth_image_proc can be found at http://wiki.ros.org/depth_image_proc |
Hi @ravijo Do you require further assistance with this case, please? Thanks! |
Thank you very much. I needed more time to check your suggestions. For now, please leave this issue without closing it. |
That's no problem at all to keep this issue open for a further time period. Thanks very much for the update! |
Thank you very much for waiting. Based on your instructions, I installed Below is the output shown on terminal:
Below is a screenshot showing Jetson informaiton: Thank you for your invaluable help and understanding. I am looking forward to hear fom you. |
I note that you are using librealsense 2.50.0 and firmware 5.14.0.0. Using this firmware version with 2.50.0 could result in errors as it was designed for use with the newer SDK 2.53.1. I would therefore recommend downgrading your firmware version to 5.13.0.50 which is the one that is designed for use with 2.50.0. |
Thanks a lot for the quick response.
How to downgrade RealSense firmware to install 5.13.0.50? On the side note, the firmware was updated to latest one because |
You can download the firmware .bin file for 5.13.0.50 to your computer from the link below. https://dev.intelrealsense.com/docs/firmware-releases#d400-series-firmware-downloads Once the .bin is downloaded, go to the More option near the top of the Viewer's options side-panel and select Update Firmware from its drop-down menu. A file selector will appear. Navigate to the folder on your computer that the .bin file was downloaded to and select the .bin file. The downgrade will then automatically begin. |
It works well when Thanks |
You are very welcome. It's excellent to hear that you achieved a solution. Thanks very much for the update! |
How much CPU usage did you achieve after doing so? |
Below is the summary:
|
I am facing a weird problem: the
realsense-viewer
is working fine, but the ROS driver stops after publishing a few images. The ROS driver is consuming 100%. Furthermore, it seems that the issue is happening whenenable_pointcloud
is set as shown below:The above logs are cropped to make this post cleaner. Please see logs.txt for complete logs.
Below is a screenshot showing CPU usage while executing the above command. Please note that no other application is running during this time, and the display is attached directly to the device with an HDMI cable.
Version Information
librealsense2
Infolibrealsense2-utils
Inforos-melodic-realsense2-camera
InfoPlease note that the ROS driver is installed from the
apt
.Additional Info
The
dmesg
does not contain any error message. However, a few entries shown below appeared frequently:Summary
✅ The
realsense-viewer
works✅ Default
rs_camera.launch
works❌ The
rs_camera.launch
whileenable_pointcloud
is set does not work❌ The
rs_camera.launch
whileenable_pointcloud
consumes 100% CPUAny workaround, please?
The text was updated successfully, but these errors were encountered: