Open Source RoboticsRobots, software & learning

ZED ROS2 wrapper

Software

The ZED ROS 2 wrapper exposes camera-processing outputs through ROS integration code and launch/configuration files. [1] [2] [3] [4] [5]

Installation & first result →Official websiteGetting started

For
Robotics developers selecting a concrete sensor, interface or simulation workflow [1] [2] [3] [4] [5]
Source rights
Named licenses are documented by part. Review licenses

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

The ZED ROS 2 wrapper exposes camera-processing outputs through ROS integration code and launch/configuration files. It depends on the external ZED SDK. An open wrapper therefore does not establish that the complete stereo-processing engine, camera hardware or firmware is open source. [1] [2] [4]

Is this for you?

Known limitations
  • Apachewrapper doesnotestablish sourceorlicense of externalZED processingSDK.
  • Simulation camera route and realcamera operation are separate; no stream or calibration tested.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] [5] · Editorial assessment

What you need

Operating system
  • Ubuntu 22.04 / ROS 2 Humble (README)
  • Ubuntu 24.04 / ROS 2 Jazzy (README)

Upstream documented requirement/configuration only, not independently tested installation or compatibility.

[1]

Dependencies
  • SelectedREADME requires ZED SDK5.2 and matchedUbuntu/ROS2 distribution
  • Namedcamera_model, GPU/SDK/deviceconfiguration and separately supplied zed_msgs

[1] [2] [3] [4] [5]

Compute for the workload
  • CUDA and matched external ZED SDK required by README; feature-specific SDK version annotations remain relevant. No measured GPU/RAM minimum established.

Upstream documented requirement/configuration only, not independently tested installation or compatibility.

[1] [5]

Installation & first result

Open the upstream getting-started guide [1] [2] [3] [4] [5]

  • Select the named hardware/model and corresponding source configuration before installation.
  • Follow the cited starting route while keeping package, device and firmware versions matched; no operation reproduced here.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] [5] · Editorial assessment

Installation

README ZED SDK 5.2 and CUDA with matched ROS/camera packages and zed_msgs; some selected config features require SDK 5.3/5.4/5.5, so inspect enabled feature annotations.

Upstream documented requirement/configuration only, not independently tested installation or compatibility.

[1] [5]

Project notes

Keep the SDK and ROS route matched

The selected README requires ZED SDK 5.2 and CUDA and identifies Ubuntu/ROS distribution combinations, including Humble on 22.04 and Jazzy on 24.04. It directs older SDK users to releases. Those are upstream support statements, not a compatibility matrix reproduced here; choosing another SDK or today's package release requires a new match. Selected configuration annotations require SDK 5.3, 5.4 or 5.5 for some features: check each enabled feature rather than treating 5.2 as sufficient for every option. No SDK, ROS package or GPU environment was installed. [1] [5]

The named launch route is ros2 launch zed_wrapper zed_camera.launch.py camera_model:=<camera_model>. Replace the placeholder with the actual model; the launch source selects camera parameters and component setup. The README also notes that zed_msgs availability/installation differs by distribution. A command copied without its messages, camera configuration and SDK dependencies is not a complete setup. [1] [3] [5]

Simulation is a separate input path

The README gives ros2 launch zed_wrapper zed_camera.launch.py camera_model:=zedx sim_mode:=true use_sim_time:=true. Match camera_model to the simulated device; a mismatch can silently disable features. With use_sim_time, the node waits for valid /clock messages, so a simulation-clock publisher is required. A simulated image/IMU stream passing through the processing pipeline is different from receiving data from a physical camera. Match input mode and time source before interpreting a ROS topic as evidence that a real camera is connected. Neither path was run here. [1] [3]

The Apache-2.0 notice applies to the wrapper contribution; it does not establish rights for external SDK, hardware, models or data, whose applicable terms require separate review. No stereo-depth quality, tracking, object detection, GPU throughput, calibration or device recovery was tested. [2]

What we checked

Pinned documentation/selected source review only; no build, installation, live device/network, simulator, calibration or performance test.

Not yet established

  • Requirements: host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
b19902d

Source files and licenses

Distinct robot-facing source implementation/interface; no purchased hardware design or untested performance claim.

LayerAvailability / license
softwareavailable · Apache-2.0 wrapper; external ZED SDK separate
Scoped source declaration; purchased hardware, firmware, binaries, assets and external dependencies require separate terms. [1] [2] [3] [4] [5]
documentationavailable · Apache-2.0 wrapper; external ZED SDK separate
Scoped source declaration; purchased hardware, firmware, binaries, assets and external dependencies require separate terms. [1] [2] [3] [4] [5]

No separate physical design, pretrained distribution or dataset is selected as the released contribution in this scoped software review.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history