Pricing
00
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 Pro

Operator 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

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01diagnostics callback→
  2. 02heartbeat watchdog→
  3. 03protective stopOUT
02

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.

03

Verification

Pass more than the visible symptom.

4 checks
  • Clock offset applied
  • Causal event identified
  • Hidden regression behavior
  • Root cause explanation