Guided beta caseProadvancedIncident reconstruction
The robot stopped during a delivery
Identify the initiating event from a bag, controller logs, and drive diagnostics containing unrelated warnings.
Pairs with Bags, logs, and reconstruction in ROS 2 Systems Debugging. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
The mission aborts after localisation warnings, a heartbeat gap, and a protective stop occur within 800 ms.
Ubuntu 24.04, ROS 2 Jazzy, Python and C++ nodes, browser telemetry workspace
System boundary
Trace only the relevant path.
diagnostics callbackheartbeat watchdogprotective stop
How this lab works
You diagnose it — no command list.
Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you — finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.
Verification
Your repair must pass more than the visible symptom.
- Clock offset applied
- Causal event identified
- Hidden regression behavior
- Root cause explanation