The ROS wrapper allows you to use Intel RealSense Depth Cameras D400, SR300 & L500 series and T265 Tracking Camera, with ROS and ROS2.
These are the currently supported ROS Distributions:
- Noetic Ninjemys (Ubuntu 20.04 Focal)
- Melodic Morenia (Ubuntu 18.04 Bionic)
- Kinetic Kame (Ubuntu 16.04 Xenial)
These are the currently supported ROS2 Distributions:
- Foxy Fitzroy (Ubuntu 20.04 Focal)
- Eloquent Elusor (Ubuntu 18.04 Bionic)
- [ Dashing Diademata (Ubuntu 18.04 Bionic) - EOL ]
Installation instructions: https://docs.ros.org/en/foxy/Installation/Ubuntu-Install-Debians.html
- Please refer to GitHub for installation Instructions and ROS distributions
- A summary of using Intel RealSense devices with ROS can be found on the official ROS Intel RealSense Wiki page
Link to Example
Link to GitHub
D400, L500, T265
D400, L500, T265
The published topics differ according to the device and parameters.
See the table below for Topics supported according to SKUs.
For a full list of topics type 'rostopic list' with your camera connected.
Applies to all D400 camera with RGB, ie: D415, D435, D435i, D455
*Note: /color refers to the stream coming out and /rgb_camera refers to the device itself
*Note: /depth refers to the stream coming out and /stereo_module refers to the device itself
Left IR Imager
Right IR Imager
Applies to all D400 cameras with IMU: D435i, D455
The compression packages apply to all the camera Modules (SKUs).
Requires compressed-image-transport package installed such as package ros-kinetic-compressed-image-transport
Requires compressed-depth-image-transport package installed such as package ros-kinetic-theora-image-transport
Requires theora-image-transport package installed such as package ros-kinetic-theora-image-transport
Note: '/camera' prefix can be modified:
- The "/camera" prefix in the topics is the default parameter and can be changed - refer to tf_prefix parameter in the table below.
- rs_multiple_devices.launch demonstrates how to modify the /camera prefix for multiple cameras
Default / Comment
Attach to the device with the given serial number (serial_no) number.
Default: Attach to a randomly available RealSense device.
Attach to the device with the given USB port (usb_port_id). i.e 4-1, 4-2 etc.
Default: Ignore USB port when choosing a device.
Attach to a device whose name includes the given device_type regular expression pattern.
Default: Ignore device type
Publish topics from rosbag file
Allows resetting the device before using it. Recommended to be used for example, when a glitch prevented the device from being properly closed.
If set to true, the device will reset prior to usage.
If set to true, will publish additional topics with all the images aligned to the depth image.
The topics are of the form: /camera/aligned_depth_to_color/image_raw etc.
The options, separated by commas: colorizer, pointcloud,
The depth FOV and the texture FOV are not similar. By default, pointcloud is limited to the section of depth containing the texture. You can have a full depth to pointcloud, coloring the regions beyond the texture with zeros, by setting allow_no_texture_points to true.
Gather closest frames of different sensors, infra red, color and depth, to be sent with the same timetag.
This happens automatically when filters such as pointcloud are enabled.
<stream_type>_width, <stream_type>_height, <stream_type>_fps
<stream_type> can be any of infra, color, fisheye, depth, gyro, accel, pose.
Setting a value to 0, will choose the first format in the inner list. (i.e. consistent between runs but not defined).
Choose whether to enable a specified stream or not. <stream_name> can be any of infra1, infra2, color, depth, fisheye, fisheye1, fisheye2, gyro, accel, pose.
Default is true.
This parameter allows changing the frames' IDs prefix per camera.
By default all frames' IDs have the same prefix - camera_.
Define the frame_id all static transformations refers to.
Define the origin coordinate system in ROS convention (X-Forward, Y-Left, Z-Up).
The rest of the frame IDs can be found at nodelet.launch.xml
Cameras such as D435i, D455 and T265, have built in IMU components which produce 2 separate streams: gyro - which shows angular velocity and accel which shows linear acceleration. Each with it's own frequency. (See details in Note-2)
By default, 2 corresponding topics are available, each with only the relevant fields of the message sensor_msgs::Imu are filled out.
Remove from the depth image all values above a given value (meters).
Disable by giving negative value (default)
Set the variance given to the Imu readings.
For the T265, these values are being modified by the inner confidence value.
Images processing takes time. Therefor there is a time gap between the moment the image arrives at the wrapper and the moment the image is published to the ROS environment. During this time, Imu messages keep on arriving which may result image with earlier timestamp to be published after Imu message with later timestamp.
Setting hold_back_imu_for_frames to true will hold the Imu messages back while processing the images and then publish them all in a burst, thus keeping the order of publication as the order of arrival.
Applies to T265: add wheel odometry information through this topic.
The code refers only to the twist.linear field in the message.
Applies to T265: include odometry input, it must be given a configuration file.
Explanations can be found here. The calibration is done in ROS coordinates system.
A Boolean parameter, publish or not TF at all.
Default is True.
A double parameter, positive values mean dynamic transform publication with specified rate, all other values mean static transform publication.
Default is 0.
A Boolean parameter, publish if True TF from odom_frame to pose_frame.
Default is True.
(1) See detail description of filters at Post-processing filters
- colorizer: will color the depth image. On the depth topic an RGB image will be published, instead of the 16bit depth values.
- pointcloud: will add a pointcloud topic /camera/depth/color/points. The texture of the pointcloud can be modified in rqt_reconfigure (see below) or using the parameters: pointcloud_texture_stream and pointcloud_texture_index. Run 'rqt_reconfigure' to see available values for these parameters.
(2) Setting unite_imu_method creates a new topic, imu, that replaces the default gyro and accel topics. The imu topic is published at the rate of the gyro. All the fields of the Imu message under the imu topic are filled out.
- linear_interpolation: Every gyro message is attached by the accel message interpolated to the gyro's timestamp.
- copy: Every gyro message is attached by the last accel message.
The following command allow to change camera control values using [http://wiki.ros.org/rqt_reconfigure].
rosrun rqt_reconfigure rqt_reconfigure
Updated about 1 year ago