Spinnaker ROS2 Camera Driver

::: {.toctree maxdepth=”2”} :::

This package provides a ROS2 driver for Teledyne/FLIR cameras using the Spinnaker SDK. For hardware-synchronized cameras use the Spinnaker synchronized camera driver by following the link from the flir driver repository.

NOTE: This driver is not written or supported by FLIR.

Tested Configurations

Cameras

The following cameras have been successfully used with this driver:

• Blackfly S (USB3, GigE)
• Blackfly (GigE)
• Grashopper (USB3)
• Oryx (reported working)
• Chameleon (USB3, tested on firmware v1.13.3.00)
• FLIR AX5 (GigE)

Note: if you get other cameras to work, please report back, ideally submit a pull request with the camera config file you have created.

Platforms

• ROS2 Galactic under Ubuntu 20.04 LTS (no longer actively tested)
• ROS2 Humble/Iron under Ubuntu 22.04 LTS ROS2 Rolling/Jazzy under Ubuntu 24.04 LTS
• Spinnaker 3.1.0.79 (other versions may work as well but this is what the continuous integration builds are using)

How to install

This driver can be used with or without installing the Spinnaker SDK, but installing the Spinnaker SDK is recommended because during its installation the USB kernel configuration is modified as needed and suitable access permissions are granted (udev rules). If you choose to not use the Spinnaker SDK, you must either run the linux setup script by running ros2 run spinnaker_camera_driver linux_setup_flir or perform the required setup steps manually, see Setting up Linux without Spinnaker SDK. Without these setup steps, the ROS driver will not detect the camera. So you must either install the Spinnaker SDK (which also gives you the useful spinview tool), or follow the manual setup steps mentioned earlier.

Installing from packages

For some architectures and ros distributions you can simply install an apt package:

sudo apt install ros-${ROS_DISTRO}-spinnaker-camera-driver

The package will bring its own set of Spinnaker SDK libraries, so you don’t necessarily have to install the SDK, but it’s recommended, see above.

Building from source

1) Install the FLIR spinnaker driver. If you skip this part, the driver will attempt to download the Spinnaker SDK automatically to obtain the header files and libraries. 2) Prepare the ROS2 driver build: Make sure you have your ROS2 environment sourced:

    source /opt/ros/<my_ros_distro>/setup.bash

Create a workspace (`~/ws`), clone this repo:

    mkdir -p ~/ws/src
    cd ~/ws/src
    git clone --branch humble-devel https://github.com/ros-drivers/flir_camera_driver
    cd ..

To automatically install all packages that the `flir_camera_driver`
packages depends upon, run this at the top of your workspace:

    rosdep install --from-paths src --ignore-src

3) Build the driver and source the workspace:

    colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_EXPORT_COMPILE_COMMANDS=ON
    . install/setup.bash

How to use

Topics

Published:

• ~/image_raw: the camera image (image_transport)
• ~/image_raw/camera_info: camera calibration
• ~/meta: meta data message containing e.g. exposure time.

Subscribed:

• ~/control: (only when enable_external_control is set to True) for external control exposure time and gain.

Parameters

The driver itself has no notion of the camera type (Blackfly, Grasshopper etc), nor does it explicitly support any features that the FLIR cameras have. Rather, all camera features (called Spinnaker Nodes) are mapped to ROS parameters via a yaml file that is specific to that camera type. On startup the driver reads this parameter definition file. In the config directory there are some parameter definition files for popular cameras (blackfly_s.yaml etc) that expose some of the more frequently used features like frame rate, gain, etc. You can add more features by providing your own parameter definition file, see How to develop your own camera configuration file. The ROS driver code is just a thin wrapper around the Spinnaker SDK, and should allow you to access all features available in FLIR’s spinview program.

In addition to the parameters defined in the .yaml files, the driver has the following ROS parameters:

• adjust_timestamp: see About time stamps below for more documentation. Default: false.
• acquisition_timeout: timeout for expecting frames (in seconds). If no frame is received for this time, the driver restarts. Default is 3.
• buffer_queue_size: max number of images to queue internally before shoving them into the ROS output queue. Decouples the Spinnaker SDK thread from the ROS publishing thread. Default: 4.
• camerainfo_url: where to find the camera calibration yaml file.
• compute_brightness: if true, compute image brightness and publish it in meta data message. This is required when running with the synchronized driver, but incurs extra CPU load. Default: false.
• connect_while_subscribed: if true, connect to the SDK and pull data from the camera only while subscribers to image or meta topics are present. This feature reduces compute load and link utilization while no ROS subscribers are present, but adds latency on subscription: after a subscription the first image will be published up to 1s later than without this option.
• dump_node_map: set this to true to get a dump of the node map. Default: false.
• enable_external_control: set this to true to enable external exposure control. This feature is being deprecated, do not use. Default: false.
• frame_id: the ROS frame id to put in the header of the published image messages.
• image_queue_size: ROS output queue size (number of frames). Default: 4
• max_ieee_1588_offset: maximum allowed PTP/system clock offset [s] before warning is triggered. Default: 0.1
• min_ieee_1588_offset: minimum PTP offset [s] before warning is triggered. Default: 0
• parameter_file: location of the .yaml file defining the camera (blackfly_s.yaml etc)
• serial_number: serial number of the camera. If you don’t know it, put in anything you like and the driver will croak with an error message, telling you what cameras serial numbers are available
• use_ieee_1588: use PTP (IEEE 1588) to set the header.stamp time stamp instead of system time. Note that you will still need to enable IEEE 1588 at the camera level, and enable time stamp "chunks". Default: false.

The parameters listed above cannot be dynamically updated at runtime but require a driver restart to modify.

Parameters can also be defined to correspond to commands for the camera to run, for example a software trigger. The command is then executed whenever the ROS parameter is updated.

Example usage

The driver comes with an example launch file (driver_node.launch.py) that you can customize as needed.

# launch with --show-args to print out all available launch arguments
ros2 launch spinnaker_camera_driver driver_node.launch.py camera_type:=blackfly_s serial:="'20435008'"

Using multiple cameras at the same time

The FLIR Spinnaker does not support two programs accessing the Spinnaker SDK at the same time, even if two different cameras are accessed. Strange things happen, in particular with USB3 cameras. You can however run multiple cameras in the same address space using ROS2's Composable Node concept, see the example launch file multiple_cameras.launch.py.

If you are using hardware synchronized cameras please use the spinnaker_synchronized_camera_driver, which will associate the images triggered by the same sync pulse with each other and give them identical time stamps.

About time stamps

By default the driver will set the ROS header time stamp to be the time when the image was delivered by the SDK. Such time stamps are not very precise and may lag depending on host CPU load. However the driver has a feature to use the much more accurate sensor-provided camera time stamps. These are then converted to ROS time stamps by estimating the offset between ROS and sensor time stamps via a simple moving average. For the adjustment to work the camera must be configured to send time stamps, and the adjust_timestamp flag must be set to true, and the relevant field in the “chunk” must be populated by the camera. For the Blackfly S the parameters look like this:

'adjust_timestamp': True,
'chunk_mode_active': True,
'chunk_selector_timestamp': 'Timestamp',
'chunk_enable_timestamp': True,

Network Configuration for GigE cameras

The Spinnaker SDK abstracts away the transport layer so a GigE camera should work the same way as USB3: you point it to the serial number and you're set.

There are a few GigE-specific settings in the Transport Layer Control group that are important, in particular enabling jumbo frames from the camera per FLIR’s recommendations. The following line in your camera-specific config file will create a ROS2 parameter gev_scps_packet_size:

gev_scps_packet_size int "TransportLayerControl/GigEVision/GevSCPSPacketSize"

that you can then set in your ROS2 launch file:

"gev_scps_packet_size": 9000

As far as setting up the camera’s IP address: you can set up DHCP on your network or configure a static persistent IP using spinview in “Transport Layer Control”>“GigE Vision”. Check the box for “Current IP Configuration Persistent IP” first to enable it, then set your desired addresses under “Persistent IP Address”, “Persistent Subnet Mask” and “Persistent Gateway”. NOTE: these look like regular IPs, but to set them you have to enter the 32-bit integer representation of the IP address/mask. By hand/calculator: convert the IP octets from decimal to hex, then combine them and convert to a 32-bit integer, ex: 192.168.0.1 -> 0xC0A80001 -> 3232235521.

The “Transport Layer Control”>“GigE Vision” section of spinview is also where you’ll find that “SCPS Packet Size” setting, which you can change when not capturing frames, and verify it works in spinview and without needing to spin up a custom launch file to get started, though it helps, and you’ll probably want one anyway to specify your camera’s serial number.

If you do not set up DHCP or set a static IP, your camera will probably assign itself an IP address according to the Link-Local address scheme. The address will be 169.254.xxx.xxx, where the x's are randomly generated. In your computer's network settings, change the IPv4 Method for the port that connects to your camera to "Link-Local Only." (You could also set the IPv4 Method to "Manual" with an address of 169.254.100.1 and a subnet mask of 255.255.0.0).

To check if the MTU settings are working correctly on the host you can ping with large packet size from a different host on the same network (must also have a MTU of 9000):

ping <host_ip_address> -c 2 -M do -s 8972

Note that this will not work if you ping the camera: you will find a MTU size of 1500, even if both camera and host NIC have correct MTU setting. Beware that some network cards have bugs that mess up the MTU when running ptp4l.

For more tips on GigE setup look at FLIR’s support pages here and here.

Configuring PTP (IEEE 1588)

The following resources are useful to learn about PTP setup on Linux:

• Synchronizing Time with Linux PTP
• RedHat Configuring PTP using ptp4l.

Only FLIR GigE cameras are PTP capable, but not all of them. For example the Blackfly series does not have PTP support, but the Blackfly S series does.

Each camera has a built-in PTP hardware clock (PHC). To use it, you need to:

• configure the camera to use PTP by enabling it either in SpinView or via the ROS parameter [gev_ieee_1588]{.title-ref}` (set to true/false)
• run the camera in Auto or SlaveOnly mode by setting the corresponding parameter in SpinView or using the ROS parameter gev_ieee_1588_mode.
• enable time stamps being sent via chunks by setting chunk_mode_active to True, chunk_selector_timestamp to Timestamp followed by chunk_enable_timestamp to True.
• tell the driver to actually use the time stamps instead of the system clock by setting use_ieee_1588 to True. If this flag is set, the driver will populate the ROS image message header stamp with the PTP time stamp.

The launch file section for the Blackfly S has some commented out example settings.

When the camera boots up it will start its PHC time at zero rather than at the correct time (TAI). The driver log will have warning messages and indicate a huge offset.

[WARN] [1744643742.707293740] rate [Hz] in   5.01 out   0.00 drop   0 LIS off[s]: 1744643660.7902

Do not run like that because your image header stamps will be totally messed up. In the above example, the camera has been started in SlaveOnly mode, and hence is in the LIS status (listening). This cannot be fixed by running the camera in Auto mode, because the camera has no way to set its PHC to a network time. Although the camera will eventually assume a role as master and the clock status will show MAS, it will still have a huge offset. To fix this you must provide PTP messages from another host on the network by running ptp4l like so: :

ptp4l -i eth0 -m

If you have some fancy PTP capable hardware clock attached to this host, you can synchronize your host system clock with the PHC of the network card:

phc2sys -c /dev/ptp_my_fancy_clock -c CLOCK_REALTIME -O 0 -m -l 6

and you are all set. Alternatively you can force the network card's PHC to follow your host's system clock:

phc2sys -s CLOCK_REALTIME -c /dev/ptp0 -O 0 -m -l 6

In this scenario you need to make sure that your host's system clock does not exhibit jumps, e.g. use something like chrony to keep it smoothly in sync with network time.

Once the camera gets PTP packets it will eventually accept the host's PHC as master clock, switch to slave mode, and reset its time stamps:

[WARN] [1744645260.742396500]: rate [Hz] in   5.00 out   0.00 drop   0 LIS off[s]: 1744645228.1477
[WARN] [1744645265.742424829]: rate [Hz] in   5.00 out   0.00 drop   0 SLV off[s]: 1744645228.1478
[INFO] [1744645270.742237929]: rate [Hz] in   5.00 out   0.00 drop   0 SLV off[s]: 0.0273

Note that once a camera has been up and running for a while it can be very reluctant to accept PTP message from a master and switch from listener (LIS) to Slave (SLV) mode. Power cycle the camera (disconnect the GigE/POE cable) to fix this. Best practice is to have the master clock running already before starting the camera.

Monitor the offset for a while! If the system clock of the host that is running the driver is not disciplined by the master PHC then the offset will keep drifting. Make sure that something keeps the system clock synchronized with the PHC.

How to develop your own camera configuration file

The camera configuration file defines the available ROS parameters, and how they relate to the corresponding Spinnaker nodes. The Spinnaker API follows the GenICam standard, where each property (e.g. exposure mode, gain, …) of the camera is represented by a node. Many properties are of integer or floating point type, but some are enumerations (“enum”). Before you modify a configuration file you can explore the Spinnaker Nodes by using the spinview applications that comes with the Spinnaker SDK. Once you know what property you want to expose as a ROS parameter, you add a mapping entry to the yaml configuration file, e.g.:

- name: image_width
  type: int
  node: ImageFormatControl/Width

With this entry in place, the ROS driver will now accept an integer parameter of name image_width, and whenever image_width changes, it will apply this change to the Spinnaker Node ImageFormatControl/Width.

Enumerations (enum) parameters are slightly trickier than float and integers because their values are restricted to a set of strings. Any other strings will be rejected by the Spinnaker API. Please document the valid enum strings in the configuration file, e.g.:

- name: line1_linemode  # valid values: "Input", "Output"
  type: enum
  node: DigitalIOControl/LineMode

The hard part is often finding the node name, in the last example "DigitalIOControl/LineMode". It usually follows by removing spaces from the spinview display names. However, in the SpinView GUI you can also see the true name by double-clicking on a node under the features tab and looking for "Name" (as opposed to "Display Name"). If that doesn't work, launch the driver with the dump_node_map parameter set to "True" and look at the output for inspiration.

NOTE: !!!! THE ORDER OF PARAMETER DEFINITION MATTERS !!!!

On node startup, the parameters will be declared and initialized in the order listed in the yaml file. For instance you must list the enum exposure_auto before the float exposure_time because on startup, exposure_auto must first be set to Off before exposure_time can be set, or else the camera refuses to set the exposure time.

Known issues

1) If you run multiple drivers in separate nodes that all access USB based devices, starting a new driver will stop the image acquisition of currently running drivers. There is an ugly workaround for this currently implemented: if image delivery stops for more than acquisition_timeout seconds, the acquisition is restarted. This operation may not be thread safe so the driver already running could possibly crash. This issue can be avoided by running all drivers in the same address space with a composable node (see stereo launch file for example).

Troubleshooting/Common Issues

1) Driver doesn't find camera. This is usually due to incorrect permissions, missing udev files etc. Install the Spinnaker SDK and get SpinView to work. 2) Driver doesn't publish images and/or warns about incomplete images for GigE cameras

    rate [Hz] in  39.76 out   0.00 drop   0% INCOMPLETE 100%

The reason for the incomplete images is usually that you are
exceeding the network bandwidth, causing packets to be dropped such
that incomplete frames arrive at the host. Check for the MTU on all
network cards and switches to be 9000 (jumbo frames). Sometimes the
MTU for switches has to be set higher. Also make sure the GigE
camera has jumbo frames enabled, i.e. `gev_scps_packet_size` is set
to 9000.

3) Driver reports dropped packages. This means the connected subscriber is not picking up fast enough. Check CPU utilization of subscribers and the available network bandwidth between driver and subscriber. 4) Image seems laggy when viewed. This is usually not a camera driver issue, but related to ROS2 RMW or the image viewer. Check CPU utilization on displaying host and network bandwidth. 5) Camera doesn't reach desired frame rate. First play around in SpinView to reproduce the problem there. For GigE cameras, check network bandwidth. Switch to Bayer images to reduce network bandwidth by a factor of three. Check your exposure time. The frame rate cannot exceed the inverse of the exposure time. 6) GigE camera cannot be initialized:

    [19074765]: found camera with serial number: 19074765
    [Spinnaker Wrapper]: Could not initialize camera on any interface!
    [Spinnaker Wrapper]: failed attempt on interface: GEV Interface 1

Either the IP address of your camera is out-of-network (switch it to
DHCP using SpinView) or another application (SpinView?) is currently
using the camera.

Setting up Linux without Spinnaker SDK

Only use these instructions if you did not install the Spinnaker SDK on your machine.

1) Somewhere in your .bashrc file, set the following env variable:

export SPINNAKER_GENTL64_CTI=/opt/ros/${ROS_DISTRO}/lib/spinnaker-gentl/Spinnaker_GenTL.cti

2) Add the “flirimaging” group and make yourself a member of it

sudo addgroup flirimaging
sudo usermod -a -G flirimaging ${USER}

3) Bump the usbfs memory limits

The following was taken from
[here](https://www.flir.com/support-center/iis/machine-vision/application-note/using-linux-with-usb-3.1/).
Edit the file `/etc/default/grub` and change the line default to:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.usbfs_memory_mb=1000"

Then

    sudo update-grub

If your system does not have `/etc/default/grub`, create the file
`/etc/rc.local`, and change its permissions to 'executable'. Then
write the following text to it:

    #!/bin/sh -e
    sh -c 'echo 1000 > /sys/module/usbcore/parameters/usbfs_memory_mb'
    exit 0

4) Setup udev rules

    echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="1e10", GROUP="flirimaging"' | sudo tee -a /etc/udev/rules.d/40-flir-spinnaker.rules
    echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="1724", GROUP="flirimaging"' | sudo tee -a /etc/udev/rules.d/40-flir-spinnaker.rules
    sudo service udev restart
    sudo udevadm trigger

5) Logout and log back in (or better, reboot)

    sudo reboot

How to contribute

Please provide feedback if you cannot get your camera working or if the code does not compile for you. Feedback is crucial for the software development process. However, before opening issues on github first verify that the problem is not present when using spinview.

Bug fixes and config files for new cameras are greatly appreciated. Before submitting a pull request, run this to see if your commit passes some basic lint tests:

colcon test --packages-select spinnaker_camera_driver && colcon test-result --verbose

License

This software is issued under the Apache License Version 2.0. The file cmake/TargetArch.cmake is released under a custom license (see file).

Changelog for package spinnaker_camera_driver

3.0.2 (2025-05-25)

• avoid ament_target_dependencies
• fixed doc formatting
• PTP support for spinnaker_camera_driver
• added reverse x/y for blackfly s
• Contributors: Bernd Pfrommer

3.0.1 (2025-04-01)

• do not use user_set_selector for blackfly_s in launch file
• document software trigger
• Contributors: Bernd Pfrommer

3.0.0 (2024-11-21)

• Remove "NOT TESTED" from tested Chameleon params - Tested with [CM3-U3-50S5C]{.title-ref} camera model, [trigger_source: "Line0"]{.title-ref} and [trigger_selector: "FrameStart"]{.title-ref}

• Re-order Chameleon config params to match Blackfly
  • Match Chameleon param order with Blackfly config params

• Add Reverse and VideoMode Chameleon config params - ReverseX/Y params flip the image as expected. This changes the pixel format accordingly (e.g. BayerRG8 -> BayerBG8 for an X and Y flip) - Video Mode options can affect effective resolution, frame rate and brightness depending on camera model, please check the documentation.

• support brightness computation for all bayer image types
• better documentation for setting GENTL variable
• only access camera with correct serial
• better diagnostics on incomplete images
• work around compile error on Iron
• fix multiple network interface refreshCameraList
• add support for transport layer and stream params
• added option to launch blackfly type
• mention SPINNAKER_GENTL64_CTI
• updated docs for jazzy, adjust download script
• remove unnecessary debs from package
• point to new spinnaker sdk for noble
• renamed stereo_synced file and added doc
• added user set control examples for blackfly/blackfly_s
• fix broken composable node by installing in correct location

• Add FLIR-AX5 Camera (#176) * added config file for flir_ax5 ---------Co-authored-by: Bernd Pfrommer <<bernd.pfrommer@gmail.com>>

• add option to disable external control (default!)
• updated docs for sync driver, switch to RST
• widened the ExposureController interface
• fix build errors on rolling/noble
• added blacklevel and whitebalance support for blackfly
• use proper name for camerainfo when using sync driver
• fixes to compile on focal/galactic
• Oryx parameter file
• lint
• allow for unreadable command nodes
• Initial support for command nodes
• remove more spinnaker imports
• make Spinnaker private
• added blackfly GigE configuration file
• track incomplete frames
• fixed licensing documentation
• provision camera driver for exposure control
• fixed bugs discovered when running on GigE cams
• avoid searching ROS path for library
• added connect_while_subscribed feature
• Added binning parameter
• install spinnaker library in same place as driver library
• remove junk directories from search path
• added first implementation of synchronized driver
• prepare single-camera driver for use with sync'ed driver
• fixed stereo launch file serial nb bug
• removed changelogs
• Contributors: Alejandro Bordallo, Bernd Pfrommer, Luis Camero, Sir-Photch, anonymousarmadillo100, buckleytoby, iagogomes

2.0.8 (2023-11-14)

• Changes.
• Added linux_setup_flir script instructions to Readme
• Add newline echo before Done
• Rename script to remove extension
• Ask permission for usb change and don't limit detection to 1000
• Ask about usergroup and give feedback
• Added linux pc setup script
• fix python formatting to satisfy linter
• fix formatting of BSD license to satisfy linter
• Contributors: Bernd Pfrommer, Hilary Luo, Tony Baltovski

2.0.7 (2023-10-03)

• Changes.
• Restricted the device permissions
• Added Teledyne to udev as requested
• Added udev rule
• Contributors: Hilary Luo, Tony Baltovski

2.0.6 (2023-08-12)

• updated changelog
• use correct file name when downloading spinnaker from clearpath web site
• resurrect building when the Spinnaker SDK is present
• also compile with older version (0.6) of yaml library
• git clone needs --branch humble-devel
• Contributors: Bernd Pfrommer

2.0.5 (2023-08-11)

• updated changelog
• add ffmpeg depency to fix build failures on ROS farm
• reference correct yaml dependency in rosdep
• switch from config files to standard yaml format
• Contributors: Bernd Pfrommer

2.0.4 (2023-08-10)

• updated changelogs
• install spinnaker libraries in spinnaker_camera_driver dir
• Contributors: Bernd Pfrommer

2.0.3 (2023-08-01)

• Changes.
• Hardcoding OS to jammy since it is the only one currently supported.
• Contributors: Tony Baltovski

2.0.2 (2023-07-28)

• Changes.
• replace lsb-release with python3-distro
• add dependencies for spinnaker download
• Contributors: Bernd Pfrommer, Tony Baltovski

2.0.1 (2023-07-24)

• Changes.
• use cmake find_program to detect lsb_release
• Contributors: Bernd Pfrommer, Tony Baltovski

2.0.0 (2023-07-20)

• Changes.
• added spinnaker_camera_driver package
• deleted spinnaker ros2 driver, to be replaced by new version
• Contributors: Bernd Pfrommer, Tony Baltovski

0.2.5 (2023-01-06 20:18)

• Changes.
• Fixed arm64 folder name.
• Contributors: Tony Baltovski

0.2.4 (2023-01-06 11:43)

• Changes.
• Fixed typo in arm64 arch.
• Contributors: Tony Baltovski

0.2.3 (2022-04-19)

• Changes.
• Only install necessary libraries
• Contributors: Luis Camero, Tony Baltovski

0.2.2 (2022-03-28)

• Changes.
• Added new-line at EOF
• Spinnaker libraries are now all copied to usr/lib
• Reordered definitions to prevent compiler warnings
• Contributors: Luis Camero, Tony Baltovski

0.2.1 (2022-03-21)

• Changes.
• Removed check for build/usr/lib which would cause build to skip Spinnaker SDK install
• Contributors: Luis Camero, Tony Baltovski

0.2.0 (2022-03-11)

• Changes.
• Changes.
• Fixed all issues reported by roslint
• Updated file paths to /opt/spinnaker instead of /usr/spinnaker
• Updated download_spinnaker look-up table
• Add readable check to SDK parameters
• URDF Description, Diagnostics, ISP Enable, and Launch Files (#81)
  • Changes required to use GigE Blackfly S version
  • Added blackfly mesh
  • Added URDF of blackflys and CHANGELOG
  • Added new_line at end of flir_blackflys.urdf.xacro
  • Added DiagnosticAnalyzers and more detailed diagnostic messages
  • Added ISP enable and disable config and updated camera launch file to be more descriptive
  • Switched order of configuration to put ISP enable next to color encoding
  • Updated config to include enumeration for Off, Once, Continuous parameters, and udpated diagnostics.launch
  • Handled issue where no namespace prevents diagnostics_agg from loading from analyzer paramaters
• Branch to Support GigE Cameras (#79)
  • Changes required to use GigE Blackfly S version
  • Update SpinnakerCamera.cpp
• Add new parameter to apply an offset to image time stamps (#56)
• Fixes SpinnakerCamera teardown (#16)
  • fixes error on destroying SpinnakerCamera with multiple cameras
  • adds clarifying comment
• Add /opt/spinnaker to spinnaker discovery options (#63)
• increase maximum value of exposure_time/auto_exposure_time_upper_limit (#55)
• add option to set queue_size for ros publisher (#54)
• Added support for Grasshopper3. Identical to Chameleon3, split into separate files for clarity. (#26)
• Feature: horizontal and vertical image reverse (#41)
  • Add horizontal/vertical inverse to reconfigure cfg

  * Add ReverseX/ReverseY with setProperty Co-authored-by: Fabian Schilling <<fabian.schilling@me.com>>

• Update Spinnaker.cfg (#50) Fix for correct spelling with capital letter for bool type

• Add auto exposure ROI parameters (#52) * spinnaker_camera_driver: setProperty: report available enum values Only done on failure. This helps to figure out which enum values are available on a particular camera model. * spinnaker_camera_driver: expose AE ROI parameters This is highly useful when using fisheye lenses, which illuminate only a circle in the center of the image. The AE gets confused by the black regions around it and overexposes the image. This also exposes the "AutoExposureLightingMode" parameter, which allows the user to choose a lighting preset (front/back/normal).

• Fix/frame rate params (#20)
  • [spinnaker_camera_driver] Fixed naming of frame rate control params
  • [spinnaker_camera_driver] Format of mono and stereo launchfiles
  • [spinnaker_camera_driver] Updated diagnostics launchfile
• Removed opencv as depend. (#46)
• Changed the download script to check for destination folder and moved unpack directory. (#44)
• Create the directory if it doesn't exist
• Remove an unnecessary deb
• Spinnaker driver now successfully downloads & builds
• Start overhauling the spinnaker download script so it works with the correct endpoint & matches the general structure of the pointgrey_camera_driver
• Contributors: Adam Romlein, Chris I-B, Evan Bretl, Fabian Schilling, Ferdinand, Joseph Curtis, Luis Camero, Max Schwarz, Stephan, Tony Baltovski, Yoshua Nava, Yuki Furuta, luis-camero

0.1.3 (2018-09-25)

• Update Changelog.
• Fix install targets when Spinnaker is installed locally. Tabs in FindSpinnaker.
• Add missing target (Cm3) and switch to find_package script. (#11)
  • Add missing target (Cm3) and switch to find_package script.
  • Clean up message.
• Adding support of feeding some camera diagnostics to the diagnostic a… (#4)
  • Adding support of feeding some camera diagnostics to the diagnostic aggregator
  • Creating a seperate diagnostics launch example
• Fix null conversion and unsigned comparison Warnings.
• Contributors: Helen Oleynikova, Michael Hosmar, mlowe-ascent

0.1.2 (2018-07-27)

• Update Changelog.
• Add ARM Build Support (#3)
  • Added ARM Build Support.
• Contributors: Michael Hosmar

0.1.1 (2018-07-25)

• Update Changelog.
• Add opencv3 as build dependency.
• Contributors: Michael Hosmar

0.1.0 (2018-07-24)

• Add Changelog
• Change TODO's to me.
• Flir = Spinnaker
• Add timeout and fix reconnection. Replace Pointgrey references from e4b1493. Changed some prints away from "Once".
• Move to std::shared_ptr and removed unnecessary install directive.
• Remove old changelog.
• Remove unnecessary config files.
• line length.
• flir_camera_driver = spinnaker_camera_driver
• Contributors: Michael Hosmar