BlackBox's ROS 2 flight recorder captures episodes and tags failures
Never dig through raw logs again — record robot episodes with failure tags.
Field failures in robotics are notoriously hard to reproduce, often requiring engineers to SSH into robots, dig through raw logs, and hope to spot the issue. BlackBox Robotics addresses this with BlackBox, a dedicated flight recorder for ROS 2 systems. It records bounded windows of robot activity (episodes), lets you tag failures, and continuously monitors /diagnostics data. Over time, fleet-wide patterns emerge, making it easier to correlate failures across robots without manual log hunting.
BlackBox integrates directly via a ROS 2 node that requires minimal changes to existing setups. For non-ROS pipelines, a REST API is available, and RabbitMQ/MQTT support is under active development. The team is seeking brutal feedback from the community on whether this solves a real problem. You can test a live sandbox with demo data or sign up for a free account at bbrobotics.in to connect your own robot and upload episodes.
- Records bounded episodes of ROS 2 robot activity with failure tagging
- Monitors /diagnostics and surfaces fleet-wide failure patterns over time
- Integrates via ROS 2 node, REST API, and upcoming MQTT/RabbitMQ
Why It Matters
Robotics engineers can now systematically capture and analyze field failures without SSH or log diving.