Skip to content

OrbbecSDK_ROS2

  • Software
  • Perception
  • Driver or SDK

A ROS 2 wrapper that connects Orbbec depth cameras and LiDAR sensors to the ROS 2 ecosystem, supporting several ROS 2 distributions.

  • Closed core

Made by Orbbec, United States (checked on github.com/orbbec (opens in a new tab)).

Source on GitHub: github.com/orbbec/OrbbecSDK_ROS2 (opens in a new tab). Facts read at commit c153462 (opens in a new tab).

Licenses

Code
Apache-2.0 (opens in a new tab)

Read by Robotheca from LICENSE (opens in a new tab) (Apache-2.0) at commit c153462 (opens in a new tab), on 16 Oct 2026.

Commercial use
Unknown

It needs closed parts under their own terms: read them before any commercial use.

One part it needs is closed

  • Needs Orbbec SDK libraries (prebuilt): The repository ships the Orbbec SDK as prebuilt libraries in orbbec_camera/SDK (for example libdepthengine.so), without their source.

Labels

  • Closed coreIt needs closed parts: Orbbec SDK libraries (prebuilt).

What it does

  • Provides ROS 2 integration for Orbbec cameras, with launch files for specific camera series.
  • Supports the ROS 2 Foxy, Humble, Jazzy, Lyrical, and Rolling distributions; default branch is v2-main.
  • Can be installed from Linux binary packages or built from source with colcon.
  • Requires udev rules so the cameras can be opened without running nodes as root.
  • Includes example launch files, command-line tools for listing devices, and services such as getting the SDK version.

Written by Robotheca from the project's README (opens in a new tab) at commit c153462.

Getting started

Difficulty
Beginner
Hardware it needs, as the project states it
Orbbec cameras or LiDAR devices connected over USB, running Ubuntu 20.04, 22.04, 24.04, or 26.04 with a supported ROS 2 distribution.

Maintenance

Status
Active: a commit in the last 90 days
Newest commit
8 Oct 2026 on v2-main
Latest release
Release v2.10.6 (30 Sept 2026)

Checked on GitHub on 16 Oct 2026.

Robots on Robotheca that use it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.