Phase 1 of 4 · Study weeks 1-4
ROS 2 foundations and a simulated robot
This phase makes the first checkpoint possible: a robot in simulation that you can drive, measure and record.
Topics every week
- Week 18 h
- Nodes, topics, services and actions
- Packages,
colconand launch files - The
ros2command-line tools - Quality of service (QoS) basics
Hand inA two-node package with a launch file and a test that shows a QoS mismatch dropping data
- Week 28 h
- Robot description with URDF and xacro
- Links, joints and inertia
- Frames and
tf2(REP 105) - Viewing with RViz
Hand inA robot model and a script that checks the transform tree
- Week 38 h
- Gazebo and the ROS bridge
- Spawning the robot in a world
- Simulation time (
use_sim_time) - Teleoperation and bag recording with
rosbag2
Hand inThe robot driving in a world, with a bag of a 10 m square run
- Week 48 h
ros2_control: hardware interfaces and the controller manager- The differential-drive controller and odometry
- Measuring command-to-wheel delay
Hand inCheckpoint 1, with your predicted delay beside the measured one
Practice projects
- Practice 1, the QoS drop (Week 1): make a publisher and subscriber that fail to connect because of mismatched QoS, then fix them. Done when: a test shows no messages before and all messages after, and you can say which policy differed.
- Practice 2, the frame checker (Week 2): write a script that loads the transform tree and fails on a missing, duplicated or misnamed frame. Done when: three seeded errors are each caught with a clear message.
- Practice 3, the delay histogram (Week 4): measure the time from a velocity command to the wheel command. Done when: a histogram of 1,000 commands gives median and p99, and a second run with a busy computer shows the change.
- Optional, a second world: build a world with a narrow aisle. Done when: the robot passes through by teleoperation and the clearances are in a table.
GitHub repos to study
Existence, last commit and README notices were checked on 22 Nov 2026 by shallow clone. Every repository below had a commit in the last six months. Archive status comes from the README, not from the GitHub setting, so look again before you rely on one.
| Repo | What to read | Week |
|---|---|---|
| ros2/demos | Small examples of topics, services, actions and QoS | 1 |
| ros2/geometry2 | How tf2 stores and looks up transforms over time | 2 |
| gazebosim/ros_gz | The ROS and Gazebo bridge, and its version table | 3 |
| gazebosim/gz-sim | The simulator: worlds, systems and sensors | 3 |
| ros-controls/ros2_control | The controller manager and hardware interface design | 4 |
Milestone checkpoint
Build the simulated robot (Checkpoint 1 above). Write the tree checker first and watch it fail on a seeded wrong frame. Then describe the robot, run it in Gazebo, put the differential-drive controller on ros2_control and drive the 10 m square while recording a bag. Hand in the checker output, the delay table with your prediction beside it, the square-run end-point error, ADR-1 (Python for the core path, and where a C++ node would help) and ADR-2 (what the controller runs at and why).
Check yourself
Answer each question in your head first, then open it to check.
When do you use a topic, a service and an action?
A topic for a continuous stream. A service for a quick request and one reply. An action for a long job that needs progress and a way to cancel.In REP 105, which transform does localisation publish, which does odometry publish, and why are they separate?
Localisation publishes map to odom. Odometry publishes odom to base_link. Odom to base_link is smooth but drifts. Map to odom jumps when localisation corrects, but is globally consistent. Keeping them apart lets a controller use the smooth one.What does
use_sim_timedo, and what breaks if one node uses wall time?Nodes take time from the/clocktopic instead of the wall clock. A node on wall time stamps data with a different clock, so transforms look like they come from the future or the past and messages are dropped.Why can mismatched QoS settings leave a subscriber receiving nothing?
A publisher and subscriber connect only when their QoS is compatible, for example a best-effort publisher cannot satisfy a reliable subscriber. Without a match no data flows.What does the controller manager do?
It loads and configures controllers, reads state from hardware interfaces, runs the update loop at a fixed rate and writes the commands back.