Blog
Articles
Technical deep dives on the path to self-healing: ROS 2, SOVD, and robot fleet operations.

Safety on RTMaps 5, Diagnostics over SOVD: One Diagnostic View Across Two Runtimes
ros2_medkit gives ROS 2 robots SOVD diagnostics. rtmaps_medkit carries the same tree into the RTMaps 5 safety runtime, so one fault tree covers both. Shown here on a warehouse safety stop.
ROS 2 Fault Forensics: Queryable Rosbags with ros2_medkit and Mosaico
How ros2_medkit captures fault-scoped MCAP snapshots and Mosaico turns them into a queryable rosbag catalog. 414 MB per fault, not 1.5 TB per day.
Multi-ECU OTA Through SOVD: One Endpoint, Every Update Backend
Three ECUs, three firmware stacks, one REST call. How the SOVD plugin pattern coordinates updates across heterogeneous controllers with a single /updates lifecycle.
Unified PLC and ROS 2 Diagnostics with ros2_medkit
Bridge PLCs into ros2_medkit via OPC-UA. PLC faults trigger the same SOVD lifecycle as ROS 2 nodes - with AI diagnosis in 30 seconds.
VDA 5050 + SOVD: Fleet Coordination Meets Deep Diagnostics
VDA 5050 tells the fleet manager the robot stopped. SOVD tells the engineer why. How we bridged both standards on one robot.
ros2_medkit 0.4.0 - Production Diagnostics for ROS 2 Fleets
Triggers, remote scripts, resource locking, log aggregation, and OpenAPI 3.1. Stop firefighting your fleet at 2 AM.

Your ROS 2 Robot Deserves Real Diagnostics (SOVD)
Your robot stops. You SSH in and get a wall of text. SOVD replaces this with a REST API, structured faults, and diagnostic snapshots.