This is the official ROS driver for Zivid 3D cameras.
This driver provides support for ROS2. If you are looking for ROS1 support, please see the ros1-master branch.
Contents: Installation | Getting Started | Launching | Configuration | Services | Topics | Samples | FAQ
This driver supports Ubuntu 20.04 / 22.04 / 24.04 with ROS2. Follow the official ROS installation instructions for
your OS. If you are looking for the ROS1 driver, please see
the ros1-master branch.
To use the ROS driver you need to download and install the "Zivid Core" package. Zivid SDK version 2.9.0 to 2.13.1 is supported. See releases for older ROS driver releases that supports older SDK versions.
Follow this guide to install "Zivid Core" for your version of Ubuntu. The "Zivid Studio" and "Zivid Tools" packages can be useful to test your system setup and camera, but are not required by the driver.
An OpenCL 1.2 compatible GPU with driver installed is required by the SDK. Follow this guide to install OpenCL drivers for your system.
A C++17 compiler is required.
sudo apt-get install -y g++First, source the setup.bash script for your ROS distribution in your terminal:
source /opt/ros/$ROS_DISTRO/setup.bashThen create the workspace and src directory:
mkdir -p ~/ros2_ws/srcClone the Zivid ROS project into the src directory:
cd ~/ros2_ws/src
git clone https://github.com/zivid/zivid-ros.gitInitialize rosdep:
cd ~/ros2_ws/src
sudo rosdep init
rosdep updateInstall dependencies:
cd ~/ros2_ws/src
rosdep install -i --from-path ./ -yFinally, build the driver:
cd ~/ros2_ws
colcon build --symlink-installConnect the Zivid camera to your PC. You can use the ZividListCameras command-line
tool available in the "Zivid Tools" package to confirm that your system has been configured correctly, and
that the camera is discovered by your PC. You can also open Zivid Studio and connect to the camera.
Close Zivid Studio before continuing with the rest of this guide.
Run the sample_capture_cpp via the launch script to check that everything is working.
cd ~/ros2_ws && source install/setup.bash
ros2 launch zivid_samples sample_with_rviz.launch sample:=sample_capture_cppThis will start the zivid_camera driver node, the sample_capture_cpp node, and rviz.
The zivid_camera driver will connect to the first available Zivid camera, and
then sample_capture_cpp will trigger captures repeatedly. The resulting point cloud and
color image should be visible in rviz.
A more detailed description of the zivid_camera driver follows below.
For sample code, see the Samples section.
To launch the driver, use ros2 run:
cd ~/ros2_ws && source install/setup.bash
ros2 run zivid_camera zivid_cameraThe driver will by default connect to the first available Zivid camera.
This behavior can be overridden by setting the serial_number launch parameter, see below.
The following parameters can be specified when starting the driver. Note that all the parameters are optional.
For example, to run the zivid_camera driver with a specific serial_number specified:
ros2 run zivid_camera zivid_camera --ros-args -p serial_number:=ABCD1234Or you can use a launch file and invoke it as:
ros2 launch zivid_samples zivid_camera_with_serial_number.launch serial_number:=ABCD1234file_camera_path (string, default: "")
Specify the path to a file camera to use instead of a real Zivid camera. This can be used to develop without access to hardware. The file camera returns the same point cloud for every capture. Visit our knowledgebase to download file camera.
frame_id (string, default: "zivid_optical_frame")
Specify the frame_id used for all published images and point clouds.
serial_number (string, default: "")
Specify the serial number of the Zivid camera to use. This parameter is optional. By default, the driver will connect to the first available camera.
update_firmware_automatically (bool, default: true)
Specify if the firmware of the connected camera should be automatically updated to the correct version when the Zivid ROS driver starts. If set to false, if the firmware version is out of date then camera must be manually updated, for example using Zivid Studio or
ZividFirmwareUpdater. Read more about firmware update in our knowledgebase. This parameter is optional, and by default it is true.
The capture settings used by the zivid_camera ROS driver must be configured using YAML,
which can be exported from Zivid Studio or the API, or downloaded as .yml files from our knowledge
base.
For convenience, the Zivid ROS driver supports configuring capture settings in two ways: Using file path to a .yml file, or as a YAML string.
The following ROS parameters control which settings are used when capturing with the driver. Note
that you must set either the _file_path or the _yaml parameter. If both _file_path and _yaml
parameters are set to a non-empty string at the same time, then the driver will return an error when
capturing. By default, all settings parameters are empty.
settings_file_path (string, default: "")
Specify the path to a .yml file that contains the settings you want to use.
settings_yaml (string, default: "")
Specify a YAML string that contains the settings you want to use. For example, you can copy the contents of a .yml file saved from Zivid Studio.
The service capture_assistant/suggest_settings will modify the settings parameters automatically.
settings_2d_file_path (string, default: "")
Specify the path to a .yml file that contains the settings you want to use.
settings_2d_yaml (string, default: "")
Specify a YAML string that contains the 2D settings you want to use. For example, you can copy the contents of a .yml file saved from Zivid Studio.
Invoke this service to trigger a 3D capture. See section Configuration for how to configure the 3D capture settings. The resulting point cloud is published on topics points/xyz and points/xyzrgba, color image is published on topic color/image_color, and depth image is published on topic depth/image. Camera calibration is published on topics color/camera_info and depth/camera_info.
See Sample Capture for code example.
Invoke this service to trigger a 2D capture. See section Configuration for how to configure the 2D capture settings. The resulting 2D image is published to topic color/image_color. Note: 2D RGB image is also published as a part of 3D capture, see capture.
See Sample Capture 2D for code example.
zivid_interfaces/srv/CaptureAndSave.srv
It does exactly the same as the capture service, in addition it will save the frame to a file. This service takes a path as an argument. The chosen format is detected via the file extension. See knowledge base for a list of available output formats.
See Sample Capture and Save for code example.
zivid_interfaces/srv/CaptureAssistantSuggestSettings.srv
Invoke this service to analyze your scene and find suggested settings for your particular scene,
camera distance, ambient lighting conditions, etc. This service will automatically update the node parameter
settings_yaml with the suggested settings, see section Configuration.
When this service has returned, you can invoke the capture service to trigger a 3D capture using
these suggested settings.
This service has two parameters:
max_capture_time (duration):
Specify the maximum capture time for the settings suggested by the Capture Assistant. A longer capture time may be required to get good data for more challenging scenes. Minimum value is 0.2 sec and maximum value is 10.0 sec.
ambient_light_frequency (uint8):
Possible values are:
AMBIENT_LIGHT_FREQUENCY_NONE,AMBIENT_LIGHT_FREQUENCY_50HZ,AMBIENT_LIGHT_FREQUENCY_60HZ. Can be used to ensure that the suggested settings are compatible with the frequency of the ambient light in the scene. If ambient light is unproblematic, useAMBIENT_LIGHT_FREQUENCY_NONEfor optimal performance. Default isAMBIENT_LIGHT_FREQUENCY_NONE.
See Sample Capture Assistant for code example.
zivid_interfaces/srv/CameraInfoModelName.srv
Returns the camera's model name.
zivid_interfaces/srv/CameraInfoSerialNumber.srv
Returns the camera's serial number.
zivid_interfaces/srv/IsConnected.srv
Returns if the camera is currently in Connected state (from the perspective of the ROS driver).
The connection status is updated by the driver every 10 seconds and before each capture
service call. If the camera is not in Connected state the driver will attempt to re-connect to
the camera when it detects that the camera is available. This can happen if the camera is
power-cycled or the USB/Ethernet cable is unplugged and then replugged.
The Zivid ROS driver provides several topics providing 3D, color, SNR and camera calibration data as a result of calling capture/capture_2d services. The different output topics provides flexibility for different use cases. Note that for performance reasons no messages are generated or sent on topics with zero active subscribers.
Camera calibration and metadata.
Color/RGBA image. RGBA image is published as a result of invoking the capture or capture_2d service. Images are encoded as "rgba8", where the alpha channel is always 255.
Camera calibration and metadata.
Depth image. Each pixel contains the z-value (along the camera Z axis) in meters. The image is encoded as 32-bit float. Pixels where z-value is missing are NaN.
Point cloud data. Sent as a result of the capture service. The output is in the camera's optical frame, where x is right, y is down and z is forward. The included point fields are x, y, z (in meters) and rgba (color).
Point cloud data. This topic is similar to topic points/xyzrgba, except that only the XYZ 3D coordinates are included. This topic is recommended if you don't need the RGBA values.
Camera calibration and metadata.
Each pixel contains the SNR (signal-to-noise ratio) value. The image is encoded as 32-bit float. Published as a part of the capture service.
Normals for the point cloud. The included fields are normal x, y and z coordinates. Each coordinate is a float value. There are no additional padding floats, so point-step is 12 bytes (3*4 bytes). The normals are unit vectors. Note that subscribing to this topic will cause some additional processing time for calculating the normals.
In the zivid_samples package we have added samples that demonstrate how to use
the Zivid ROS driver. These samples can be used as a starting point for your project.
To launch the Python samples using ros2 launch, you need python to be available as a command.
For example, the python-is-python3 package can be installed to achieve this, by running the
following command:
sudo apt install python-is-python3On Windows, the Python samples cannot be launched using ros2 launch. Instead, please launch the
samples using ros2 run zivid_samples <sample_name>.py together with
ros2 run zivid_camera zivid_camera in another terminal window.
This sample performs single-acquisition 3D captures in a loop. This sample shows how to configure the capture settings, how to subscribe to the points/xyzrgba topic, and how to invoke the capture service.
ros2 launch zivid_samples sample.launch sample:=sample_capture_cpp
ros2 launch zivid_samples sample.launch sample:=sample_capture.pyUsing ros2 run (when zivid_camera node is already running):
ros2 run zivid_samples sample_capture_cpp
ros2 run zivid_samples sample_capture.pyThis sample performs single-acquisition 2D captures in a loop. This sample shows how to configure the capture 2d settings with a YAML string, how to subscribe to the color/image_color topic, and how to invoke the capture_2d service.
ros2 launch zivid_samples sample.launch sample:=sample_capture_2d_cpp
ros2 launch zivid_samples sample.launch sample:=sample_capture_2d.pyUsing ros2 run (when zivid_camera node is already running):
ros2 run zivid_samples sample_capture_2d_cpp
ros2 run zivid_samples sample_capture_2d.pyThis sample performs a capture, and stores the resulting frame to file. This sample shows how to configure the capture settings with a YAML string, how to invoke the capture_and_save service, and how to read the response from the service call.
ros2 launch zivid_samples sample.launch sample:=sample_capture_and_save_cpp
ros2 launch zivid_samples sample.launch sample:=sample_capture_and_save.pyUsing ros2 run (when zivid_camera node is already running):
ros2 run zivid_samples sample_capture_and_save_cpp
ros2 run zivid_samples sample_capture_and_save.pyThis sample shows how to invoke the capture_assistant/suggest_settings service to suggest and set capture settings. Then, it shows how to subscribe to the points/xyzrgba and color/image_color topics, and finally invoke the capture service.
ros2 launch zivid_samples sample.launch sample:=sample_capture_assistant_cpp
ros2 launch zivid_samples sample.launch sample:=sample_capture_assistant.pyUsing ros2 run (when zivid_camera node is already running):
ros2 run zivid_samples sample_capture_assistant_cpp
ros2 run zivid_samples sample_capture_assistant.pyThis sample performs single-acquisition 3D captures in a loop. This sample shows how to configure the capture settings from a yaml file, how to subscribe to the points/xyzrgba topic, and how to invoke the capture service.
ros2 launch zivid_samples sample.launch sample:=sample_capture_with_settings_from_file_cpp
ros2 launch zivid_samples sample.launch sample:=sample_capture_with_settings_from_file.pyUsing ros2 run (when zivid_camera node is already running):
ros2 run zivid_samples sample_capture_with_settings_from_file_cpp
ros2 run zivid_samples sample_capture_with_settings_from_file.pyros2 launch zivid_camera visualize.launchros2 run zivid_camera zivid_camera --ros-args -p serial_number:=ABCD1234See section Configuration for more details.
ros2 run zivid_camera zivid_camera --ros-args -p settings_file_path:=/path/to/settings.yml -p settings_2d_file_path:=/path/to/settings2D.ymlros2 service call /capture std_srvs/srv/Trigger
ros2 service call /capture_2d std_srvs/srv/Triggerros2 run zivid_camera zivid_camera --ros-args -p file_camera_path:=/usr/share/Zivid/data/FileCameraZivid2L100.zfcVisit our knowledgebase to download file camera.
You can use multiple Zivid cameras simultaneously by starting one node per camera and specifying unique namespaces per node.
ros2 run zivid_camera zivid_camera --ros-args --remap __ns:=/zivid_camera1ros2 run zivid_camera zivid_camera --ros-args --remap __ns:=/zivid_camera2You can combine this with a serial_number parameter (see above) to control which node uses which camera. By default, the zivid_camera node will connect to the first available (unused) camera. We recommend that you first start the first node, then wait for it to be ready (for example, by waiting for the capture service to be available), and then start the second node. This avoids any race conditions where both nodes may try to connect to the same camera at the same time.
This project comes with a set of unit and module tests to verify the provided functionality. To run the tests locally, first download and install the file camera used for testing:
wget -q https://www.zivid.com/software/FileCameraZivid2M70.zip
unzip ./FileCameraZivid2M70.zip
rm ./FileCameraZivid2M70.zip
sudo mkdir -p /usr/share/Zivid/data/
sudo mv ./FileCameraZivid2M70.zfc /usr/share/Zivid/data/Then run the tests:
cd ~/ros2_ws/ && source install/setup.bash
colcon test --event-handlers console_direct+ && colcon test-result --allThe tests can also be run via docker. See the GitHub Actions configuration file for details.
The node logs extra information at log level debug, including the settings used when capturing. Enable debug logging to troubleshoot issues:
ros2 run zivid_camera zivid_camera --ros-args --log-level debugAbove will enable debug logging for all components, you can also specify just the zivid_camera logger like so:
ros2 run zivid_camera zivid_camera --ros-args --log-level zivid_camera:=debug
colcon build --cmake-args -DCOMPILER_WARNINGS=ONThe CI test for this package enforces the linting defined by clang-format. From the code analysis
docker image, run:
find /host -name '*.cpp' -or -name '*.hpp' | xargs clang-format -iThe style follows the one from
ament_clang_format.
This project is licensed under BSD 3-clause license, see the LICENSE file for details.
Please report any issues or feature requests related to the ROS driver in the issue tracker. Visit Zivid Knowledge Base for general help on using Zivid 3D cameras. If you cannot find a solution to your issue, please contact [email protected].
This FTP (Focused Technical Project) has received funding from the European Union's Horizon 2020 research and innovation programme under the project ROSIN with the grant agreement No 732287. For more information, visit rosin-project.eu.