List view
Add fault management to ros2_medkit: fault reporting with two-level filtering (local + central), persistent storage, lifecycle management, and REST API access. Goals: - Two-level filtering: FaultReporter (local) + FaultManager (central) - Multi-source fault aggregation by fault_code - Persistent storage - REST API and SSE for monitoring - Backwards compatibility with diagnostic_updater Success Criteria: - FaultReporter library with local filtering (default enabled) - FaultManager with central aggregation and lifecycle - Storage survives restarts - REST API + SSE working
No due date•11/16 issues closedGoal: Complete SOVD API coverage with fleet-oriented and advanced features. The final milestone adds capabilities for fleet management, bulk data transfer, software updates, and authentication — completing the standard specification coverage. Standard API coverage: - Bulk Data (5 endpoints) — large data transfers - Communication Logs (5 endpoints) — protocol-level logging - Clear Data (5 endpoints) — cache and learned data management - Updates (4 endpoints) — software update management - Auth (2 endpoints) — authorization and token management
No due date•2/5 issues closedGoal: Enable automated workflows and reactive data collection. Developers can set up scripts for automated diagnostics, subscribe to data changes, and define triggers for event-driven workflows. Standard API coverage: - Scripts (8 endpoints) — upload, execute, and manage diagnostic scripts - Subscriptions (8 endpoints) — cyclic data subscriptions and triggers - Datasets (4 endpoints) — dynamic data lists for subscription
No due dateGoal: Allow developers to configure and control running applications. This milestone brings configuration management (backed by ROS 2 parameters) and operation execution, giving developers runtime control over their nodes. Standard API coverage: - Configuration (5 endpoints) — read/write configuration values - Operations (7 endpoints) — define, execute, and monitor operations - Modes (3 endpoints) — entity operating modes
No due date•6/6 issues closedGoal: Enable developers to monitor application health and diagnose issues. With observability features, developers can check fault codes, browse logs, and monitor the lifecycle state of their nodes — essential for debugging and troubleshooting. Standard API coverage: - Faults (4 endpoints) — list, inspect, and clear diagnostic faults - Logs (5 endpoints) — browse and configure application logs - Lifecycle (6 endpoints) — status, start, restart, shutdown operations
No due dateGoal: Provide a complete view of the ROS 2 system and enable basic data operations. Developers can discover all running nodes, explore the entity hierarchy, and read/write diagnostic data. This milestone establishes the foundation for all subsequent features. Standard API coverage: - Discovery (11 endpoints) — version info, entity collections, hierarchy navigation - Data (5 endpoints) — data categories, groups, read/write operations
No due date•48/54 issues closed