Guided beta caseProbeginnerPublisher control flow
The topic exists but publishes nothing
Restore odometry output without changing the message type or topic name.
Pairs with Topics and message flow in ROS 2 Systems Debugging. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
`/wheel/odometry` has a publisher, but `ros2 topic hz` receives no samples.
Ubuntu 24.04, ROS 2 Jazzy, Python and C++ nodes, browser telemetry workspace
System boundary
Trace only the relevant path.
encoder timerodometry publisher/wheel/odometry
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.
- Odometry rate exceeds 25 Hz
- Timestamps increase monotonically
- Hidden regression behavior
- Root cause explanation