This ROS 2 node provides support for a variety of cameras via libcamera. Amongst others, this node supports V4L2 and Raspberry Pi cameras.
Binary packages are available via the ROS package repository for some Linux and ROS distributions (check with rosdep resolve camera_ros). If it's available, you can install the DEB or RPM packages via:
# source ROS distribution
source /opt/ros/humble/setup.bash
# DEB package
sudo apt install ros-$ROS_DISTRO-camera-ros
# RPM package
sudo dnf install ros-$ROS_DISTRO-camera-rosThe camera_ros node depends on libcamera version 0.1 or later.
Some Linux and ROS distributions provide binary libcamera packages. Check your package manager for libcamera and rosdep resolve libcamera to see if binary packages are available.
If your distribution does not provide a binary libcamera package, you have to compile libcamera from source either independent of the colcon workspace according to the official build instructions or as part of the colcon workspace. Either way, you have to install libcamera's build dependencies manually:
# DEB
sudo apt install pkg-config python3-yaml python3-ply python3-jinja2 openssl libyaml-dev libssl-dev libudev-dev libatomic1 meson
# RPM
sudo dnf install pkgconfig python3-yaml python3-ply python3-jinja2 openssl libyaml-devel openssl-devel libudev-devel libatomic mesonThe camera_ros package is built in a colcon workspace. The following instructions assume that you are building libcamera from source in the colcon workspace.
# create workspace with camera_ros package
mkdir -p ~/camera_ws/
cd ~/camera_ws/
git clone https://github.com/christianrauch/camera_ros.git src/camera_ros
# optional: build libcamera in colcon workspace
pip install colcon-meson
git clone https://git.libcamera.org/libcamera/libcamera.git src/libcamera
# resolve binary dependencies and build workspace
source /opt/ros/humble/setup.bash
rosdep install --from-paths src --ignore-src --skip-keys=libcamera
colcon buildIf you installed libcamera externally, you can omit the colcon-meson and libcamera steps. Additionally, if there is a binary package and a rosdep entry for libcamera (check with rosdep resolve libcamera) you can also omit --skip-keys=libcamera and have this binary dependency resolved automatically.
The package provides a standalone node executable:
ros2 run camera_ros camera_nodea composable node (camera::CameraNode):
ros2 component standalone camera_ros camera::CameraNodeand an example launch file for the composable node:
ros2 launch camera_ros camera.launch.pyThe node provides two sets of parameters:
- static read-only parameters to configure the camera stream once at the beginning
- dynamic parameters which are generated from the camera controls to change per-frame settings and which can be changed at runtime
Those parameters can be set on the command line:
# standalone executable
ros2 run camera_ros camera_node --ros-args -p param1:=arg1 -p param2:=arg2
# composable node
ros2 component standalone camera_ros camera::CameraNode -p param1:=arg1 -p param2:=arg2or dynamically via the ROS parameter API.
The camera stream is configured once when the node starts via the following static read-only parameters:
| name | type | description |
|---|---|---|
camera |
integer or string |
selects the camera by index (e.g. 0) or by name (e.g. /base/soc/i2c0mux/i2c@1/ov5647@36) [default: 0] |
role |
string |
configures the camera with a StreamRole (possible choices: raw, still, video, viewfinder) [default: video] |
format |
string |
a PixelFormat that is supported by the camera [default: auto] |
width, height |
integer |
desired image resolution [default: auto] |
The configuration is done in the following order:
- select camera via
camera - configure camera stream via
role - set the pixel format for the stream via
format - set the image resolution for the stream via
widthandheight
Each stream role only supports a discrete set of data stream configurations as a combination of the image resolution and pixel format. The selected stream configuration is validated at the end of this sequence and adjusted to the closest valid stream configuration.
By default, the node will select the first available camera and configures it with the default pixel format and image resolution. If a parameter has not been set, the node will print the available options and inform the user about the default choice.
The node avoids memory copies of the image data by directly mapping from a camera pixel format to a ROS image format, with the exception of converting between "raw" and "compressed" image formats when requested by the user. As an effect, not all pixel formats that are supported by the camera may be supported by the ROS image message. Hence, the options for format are limited to pixel formats that are supported by the camera and the raw ROS image message.
The dynamic parameters are created at runtime by inspecting the controls that are exposed by the camera. The set of exposed controls is camera-dependent. The ROS parameters are directly formatted from the exposed controls, hence the parameter names match the control names.
libcamera does not expose the framerate directly as a parameter. Instead, the framerate range has to be converted to a duration:
FrameDurationLimits, if it is exposed by the camera:
# set fixed framerate of 20 Hz (50 ms)
ros2 run camera_ros camera_node --ros-args -p FrameDurationLimits:="[50000,50000]"
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent