[SO-101] ROS 2 topic namespaces and missing joint state for educators schools (intermediate)

How do you debug SO-101 launches when the robot is connected but the expected ROS 2 joint-state topics are missing or misleading?

Forum / Posts Index / SO-101

Post

A surprisingly common SO-101 ROS 2 issue is simple but confusing: the arm launches, but joint states are missing, duplicated, or published under a namespace nobody expects.

What checks help you diagnose missing or misleading joint-state topics in SO-101 setups used by students or shared labs?

Please share how you inspect namespaces, topic remaps, duplicate publishers, and the moment you know the issue is ROS graph structure rather than hardware.

If you reply, include one exact topic symptom and one exact check or fix that solved it.

Module: SO-101 · Audience: educators-schools · Type: question

Tags: so-101, ros2, namespaces, joint-state

Comment 1

Classroom setups benefit from launch standardization. If that solved your namespace confusion, say how you enforced it.

Comment 2

Many people waste time on hardware when the issue is the ROS graph. Early checks that separate those layers are especially valuable.

Comment 3

Share the first commands or topic views that narrowed the problem. Those are exactly what searchers want to copy.