Pricing
00
In productionProintermediateLaunch scope

The launch file places a node in the wrong namespace

Restore one robot's diagnostics without changing fleet-wide topic names.

Pairs with Nodes, names, and namespaces in ROS 2 Systems Debugging. Read the concept first, then diagnose it here.

Unlock this lab with Pro

Operator report

`/robot_2/diagnostics` is silent while `/diagnostics` receives duplicate publishers.

Ubuntu 24.04, ROS 2 Jazzy, Python and C++ nodes, browser telemetry workspace

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01launch GroupAction→
  2. 02diagnostics node→
  3. 03/robot_2/diagnosticsOUT
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
  • Namespaced topic detected
  • Global duplicate removed
  • Hidden regression behavior
  • Root cause explanation