Realsense D415 on Kinetic topic stops when we add another

asked 2021-01-14 16:02:44 -0600

Unproductive gravatar image

updated 2021-01-18 18:18:15 -0600

Hi Ros Experts,

When we add another camera topic we lose one of the existing ones.

What should we be looking for as the cause of this: We are capturing colour images, and depth images.

WE initially are capturing frames from /camera/color/image_raw and /camera/depth/image_rect_raw

When we add in a point cloud topic, we get the point cloud topic and capture PCD files from it, however the /camera/depth/image_rect_raw topic ceases working -- it quickly drops out.

Explaining this a little more clearly:

roslaunch realsense2_camera rs_camera.launch filters:=pointcloud align_depth:=true

results in a point cloud but no depth map on /camera/depth/image_rect_raw OR /camera/depth/align_depth

roslaunch realsense2_camera rs_camera.launch filters:=pointcloud

gives a point cloud but no depth map on /camera/depth/image_rect_raw OR /camera/depth/align_depth

roslaunch realsense2_camera rs_camera.launch

gives a depth map on depth map on /camera/depth/image_rect_raw ... but of course, no point cloud.

We would like to get both the depth map and the point cloud.

We need some hints! What should we be looking for to solve this?

Ubuntu 16.04, ROS kinetic, realsense2 2.41.


edit retag flag offensive close merge delete


Hi ROS Gurus,

Adding to question above from my colleague:

  1. The point cloud topic described above was added by running the command: $ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud When this command is run the depth image topic /camera/depth/image_rect_raw stops working on rviz and the new topic /camera/depth/color/points starts working OK in rviz.

  2. If we remove the pointcloud instruction and add the aligh_depth as shown in the following command: $ roslaunch realsense2_camera rs_camera.launch align_depth:=true We get an additional topic /camera/depth/align_depth and the topic /camera/depth/image_rect_raw does NOT freeze and continues to work normally.

Does anyone know why, the addition of the pointcloud topic appear to "disable" the default /camera/depth/image_rect_raw topic?

Many thanks.

armnavas gravatar image armnavas  ( 2021-01-14 17:48:21 -0600 )edit

Hi ROS Gurus,

Below is the rs_camera.launch file we are using:

  <arg name="serial_no"           default=""/>
  <arg name="json_file_path"      default=""/>
  <arg name="camera"              default="camera"/>
  <arg name="tf_prefix"           default="$(arg camera)"/>

  <arg name="fisheye_width"       default="640"/>
  <arg name="fisheye_height"      default="480"/>
  <arg name="enable_fisheye"      default="true"/>

  <arg name="depth_width"         default="640"/>
  <arg name="depth_height"        default="480"/>
  <arg name="enable_depth"        default="true"/>

  <arg name="infra1_width"        default="640"/>
  <arg name="infra1_height"       default="480"/>
  <arg name="enable_infra1"       default="true"/>

  <arg name="infra2_width"        default="640"/>
  <arg name="infra2_height"       default="480"/>
  <arg name="enable_infra2"       default="true"/>

  <arg name="color_width"         default="640"/>
  <arg name="color_height"        default="480"/>
  <arg name="enable_color"        default="true"/>

  <arg name="fisheye_fps"         default="30"/>
  <arg name="depth_fps"           default="30"/>
  <arg name="infra1_fps"          default="30"/>
  <arg name="infra2_fps"          default="30"/> ...
armnavas gravatar image armnavas  ( 2021-01-18 00:00:58 -0600 )edit

We also updated to RealSense SDK 2.0 (v2.41) with no luck.

armnavas gravatar image armnavas  ( 2021-01-18 00:33:55 -0600 )edit

A clarification on my Jan 15 2021 comment:

I did talso try to run our D415 Realsense camera with both the point cloud filter and the align depth option, with the following command with no success either.

roslaunch realsense2_camera rs_camera.launch filters:=pointcloud align_depth:=true
armnavas gravatar image armnavas  ( 2021-01-18 17:07:16 -0600 )edit

This reads like either a bug in the code, or a limitation due to bandwidth requirements to have all those streams active at the same time on the USB bus (so not on the ROS side).

In both cases, I would suggest to take this up with the Intel maintainers of the driver. They should know.

gvdhoorn gravatar image gvdhoorn  ( 2021-01-19 04:19:23 -0600 )edit

@gvdhoorn how would we establish that it was definitely not a ROS issue? Or that it was definitely a USB issue? A diagnostic approach that narrows down the possibilities would be appreciated.

Unproductive gravatar image Unproductive  ( 2021-01-19 16:57:25 -0600 )edit

It doesn't really matter. Intel supports ROS with their realsense drivers. They also support their realsense devices without ROS.

In either case: I'd suggest to post this on their issue tracker. And seeing you're encountering this while using ROS, my suggestion would be to post it on IntelRealSense/realsense-ros/issues.

gvdhoorn gravatar image gvdhoorn  ( 2021-01-20 01:30:19 -0600 )edit