Show EOL distros:
camera_aravis: An ethernet camera driver for ROS.
- Maintainer: Steve Safarik <stevesafarik AT gmail DOT com>
- Author: Steve Safarik <stevesafarik AT gmail DOT com>, Andrew Straw <andrew.straw AT imp.ac DOT at>, strawlab, Steve Safarik
- License: LGPLv2
- External website: http://github.com/ssafarik/camera_aravis
- Source: git https://github.com/ssafarik/camera_aravis.git (branch: master)
camera_aravis: A complete and comfortable GenICam (USB3Vision and GigEVision) based camera driver for ROS (ethernet and usb).
- Maintainer status: maintained
- Maintainer: Dominik Kleiser, Fraunhofer IOSB <dominik.kleiser AT iosb.fraunhofer DOT de>
- Author: Dominik Kleiser, Fraunhofer IOSB <dominik.kleiser AT iosb.fraunhofer DOT de>, Dominik A. Klein, Fraunhofer FKIE <dominik.klein AT fkie.fraunhofer DOT de>, Steve Safarik, Straw Lab <stevesafarik AT gmail DOT com>, Andrew Straw, Straw Lab <andrew.straw AT imp.ac DOT at>, Floris van Breugel, van Breugel Lab <fvanbreugel AT unr DOT edu>
- License: LGPL v2
- External website: https://github.com/FraunhoferIOSB/camera_aravis
- Source: git https://github.com/FraunhoferIOSB/camera_aravis.git (branch: noetic-devel)
This package provides a ROS interface for ethernet cameras conforming to the GenICam standard. It is based on the Aravis library. You can get the driver here. NOTE! API of aravis changed in versions 0.3.4 and 0.3.6. When using aravis 0.3.4-0.3.6 you can use the driver from here. When using aravis version 0.3.6 or newer you can use driver from here.
This ROS node publishes messages image_raw and camera_info for a specified camera.
Camera settings are supported via ROS parameters and dynamic_reconfigure, including the following:
ExposureAuto (string: "Off", "Once", "Continuous")
GainAuto (string: "Off", "Once", "Continuous")
AcquisitionMode (string: "Continuous", "SingleFrame", "MultiFrame")
TriggerMode (string: "Off", "On")
TriggerSource (string: "Software", "Line1", "Line2")
In addition to the above features, this driver 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 use for the particular feature. You can use arv-tool-0.4 to see the feature list and the XML file (e.g. "arv-tool-0.4 --name=Basler-21285878 features")
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 cam1/GammaEnable false $ rosparam set cam1/BlackLevelRaw 5 $ rosparam set cam1/PixelFormat Mono12 $ ROS_NAMESPACE=cam1 rosrun camera_aravis camnode
camera_aravis supports multiple cameras, each of which may be specified on the command-line, or via parameter. It runs one camera per node.
To specify which camera to open, via the command-line:
$ ROS_NAMESPACE=cam1 rosrun camera_aravis camnode Basler-21237813
To specify which camera to open, via a parameter:
$ rosparam set cam1/guid Basler-21237813 $ ROS_NAMESPACE=cam1 rosrun camera_aravis camnode
There is an additional nice feature related to timestamps that unifies ROS time with camera time. The issue is that we want a stable timestamp on the images that the camera delivers, giving a nice smooth time delta from frame to frame. If we were to use the ROS clock on the PC, by the time we get the image packets from the camera a variable amount of time has passed on the PC's clock due to variable network and system delays. The camera's onboard clock is stable but it doesn't match with the ROS clock on the PC, and furthermore since it comes from a different piece of hardware, the two clock's rates are slightly different.
The solution is to start with a base of ROS time, and to accumulate the dt's from the camera clock. To accomodate the difference in clock rates, a PID controller gently pulls the result toward ROS time.
The basic command to run camera_aravis:
$ rosrun camera_aravis camnode
To run it in a given namespace, which is the better way to do it:
$ ROS_NAMESPACE=cam1 rosrun camera_aravis camnode