ROS Development
Robot Operating System (ROS 2) is the usual way to structure robotics software on a PC or SBC: nodes, topics, services, and launch files. This subject is running a small graph that talks to your robot or a simulator — not installing every package on earth. Use it when the studio project actually needs distributed robot software.
Starting Points
- ROS 2. Tutorials (Humble or the distro used in the studio).
- Firmware architecture for the MCU side of a hybrid system.
Key Points
- You run a ROS 2 environment and inspect topics with
ros2 topic list/echo. - You write or modify a node that publishes or subscribes to a message your robot uses.
- You launch more than one node with a launch file and explain the graph.
- You bridge or document the boundary between ROS and MCU firmware (serial, micro-ROS, or similar).
- You keep launch and network assumptions in the repo so a teammate can reproduce the demo.