metavision_driver
- Software
- Perception
- Driver or SDK
A ROS2 driver that streams raw event-camera data from Prophesee Metavision SDK cameras and publishes it as ROS event_camera_msgs. Not written or supported by Prophesee.
Made by ROS event camera support.
Source on GitHub: github.com/ros-event-camera/metavision_driver (opens in a new tab). Facts read at commit 9702f83 (opens in a new tab).
Licenses
- Code
- Apache-2.0 (opens in a new tab)
Read by Robotheca from LICENSE (opens in a new tab) (Apache-2.0) at commit 9702f83 (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Yes
What it does
- Gets RAW EVT3 events from the camera with little processing and publishes them in event_camera_msgs format, for high data rates from Gen3 and later sensors.
- Built for speed and low CPU use: avoids memory copies, runs as a nodelet/composable node, and prints message rate statistics.
- Supports bias reconfiguration, hardware ROI, stereo camera synchronization, external trigger input and output, and event rate control.
- Events can be decoded and displayed with companion packages such as event_camera_codecs, event_camera_py, event_camera_renderer and event_camera_tools.
- Supports the IDS XCP-E, SilkyEVCam VGA and HD, and Prophesee EVK4 cameras; EVT2 and EVT4 formats are not supported.
Written by Robotheca from the project's README (opens in a new tab) at commit 9702f83.
Getting started
- Difficulty
- Intermediate
- Hardware it needs, as the project states it
- ROS2 with the Metavision SDK (OpenEB) installed or the binary package; a supported event camera (IDS ueye XCP-E, SilkyEVCam VGA or HD, or Prophesee EVK4) that outputs EVT3 data, plus its udev rules and camera plugins.
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Active: a commit in the last 90 days
- Newest commit
- 16 Oct 2026 on master
- Latest release
- None published on GitHub
Checked on GitHub on 16 Oct 2026.
Links
Robots on Robotheca that use it
No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.
Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.