camera_aravis

!!! IMPORTANT UPDATE !!!

camera_aravis for ROS 2 is now released as camera_aravis2: https://github.com/FraunhoferIOSB/camera_aravis2

Actively maintained repository for the ROS1 camara_aravis driver. It is open source under the LGPL (like Aravis itself).

The Aravis library is a glib/gobject based library for video acquisition using Genicam cameras. It currently implements the gigabit ethernet and USB3 protocols used by industrial cameras.

The camera_aravis driver has long history of multiple forks and now abandoned GitHub repositories. This repository is based on https://github.com/florisvb/camera_aravis.git, which in turn was forked from a deleted github repo (https://github.com/CaeruleusAqua/camera_aravis), which was itself forked from https://github.com/ssafarik/camera_aravis.

Tested with Aravis version 0.6.X. Since Ubuntu 20.04 the library can be installed from the official Ubuntu package repository. Install with:

sudo apt install libaravis-dev

The basic command to run camera_aravis:

$ rosrun camera_aravis cam_aravis

To run it in a given namespace:

$ ROS_NAMESPACE=cam1 rosrun camera_aravis cam_aravis

Continuous Integration

Service	Noetic	Master
GitHub
ROS Build Farm		N/A

Configuration

This ROS node publishes messages image_raw and camera_info for a specified camera. It supports a variety of camera features via the ROS reconfigure_gui, including the following:

• ExposureAuto (string: Off, Once, Continuous)
• GainAuto (string: Off, Once, Continuous)
• ExposureTimeAbs (float)
• Gain (float)
• AcquisitionMode (string: Continuous, SingleFrame, MultiFrame)
• AcquisitionFrameRate (float)
• TriggerMode (string: Off, On)
• TriggerSource (string: Any, Software, Line0, Line1, Line2)
• softwaretriggerrate (float)
• frame_id (string)
• FocusPos (integer)
• mtu (integer)

Note that if the camera parameters are to be initialized from the parameters from the dynamic reconfigure server, the launch parameter init_params_from_dyn_reconfigure needs to be set to true (Default: false );

Note that the above are also the ROS parameter names of their respective feature. You may set initial values for the camera by setting ROS parameters in the camera’s namespace.

In addition to the above features, this driver now supports (almost) every feature of every camera, you just have to know how the feature is specified; each GenICam-based camera contains an XML file onboard, and by viewing this file you can determine which ROS parameters to set for camera_aravis to write to the camera. Details on how to export the camera-specific XML can be found here: Extracting Camera-Specific GenICam XML.

Note that for this special feature access, the ROS parameter type must match the feature type. For example, a Basler ac640 has a boolean feature called “GammaEnable”, an integer feature called “BlackLevelRaw”, and a string enum feature called “PixelFormat” that takes values (Mono8, Mono12, Mono12Packed, YUV422Packed, etc). The ROS params that you set for these must be, respectively, a bool, an integer and a string. Also note that boolean features must be specified as ROS params false/true, not as integer 0/1.

$ rosparam set /camera_aravis/GammaEnable false
$ rosparam set /camera_aravis/BlackLevelRaw 5
$ rosparam set /camera_aravis/PixelFormat Mono12
$ rosrun camera_aravis cam_aravis

camera_aravis supports multiple cameras, each of which may be specified on the command-line, or via parameter. Runs one camera per node.

To specify which camera to open, via the command-line:

$ rosrun camera_aravis cam_aravis _guid:=Basler-21237813

To specify which camera to open, via a parameter:

$ rosparam set /camera_aravis/guid Basler-21237813
$ rosrun camera_aravis cam_aravis

It supports the dynamic_reconfigure protocol, and once the node is running, you may adjust its parameters by running the following and then manipulating the GUI:

File truncated at 100 lines see the full file