A ROS2 wrapper for Intel RealSense cameras that provides depth, color, and IMU data as ROS topics and services.
RealSense ROS is a ROS2 wrapper for Intel RealSense depth cameras that provides a standardized interface to access camera data within the ROS ecosystem. It converts raw camera streams (depth, color, infrared, IMU) into ROS topics, services, and TF transforms, enabling seamless integration with robotics applications. The wrapper handles device management, coordinate transformations, and real-time post-processing filters.
Robotics developers and researchers using ROS2 who need to integrate Intel RealSense cameras for perception tasks like 3D mapping, object detection, navigation, and SLAM. It's particularly valuable for teams building autonomous robots, drones, or industrial automation systems.
Developers choose RealSense ROS because it provides a production-ready, officially supported bridge between RealSense hardware and ROS2, with comprehensive feature support, active maintenance, and compatibility with multiple ROS2 distributions. It eliminates the need for custom driver development while offering extensive configurability and performance optimization.
ROS Wrapper for RealSense™ Cameras
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Publishes depth, color, infrared, and IMU data as standard ROS topics with configurable QoS, enabling multi-modal perception pipelines without custom code.
Includes built-in filters like spatial, temporal, hole-filling, and pointcloud generation, allowing for enhanced depth data processing directly within the wrapper.
Supports parameter adjustments for streams and filters via ROS services during operation, providing flexibility for tuning without node restarts.
Provides static and dynamic TF frames for optical and ROS coordinate systems, adhering to REP conventions for seamless integration with other ROS nodes.
Requires installing ROS2 distributions, librealsense SDK, and managing multiple build options, which can be error-prone and time-consuming, especially on Windows where support is limited.
Enabling the ROS2 Lifecycle Node disables image_transport functionality, forcing a choice between better node management and compressed image topics, as admitted in the README.
Migration from ros2-legacy involved significant parameter changes (e.g., replacing stereo_module with depth_module), which can break existing setups and require manual updates.