Roadmaps / Robotics / Setup and lab safety
Read first
Setup and lab safety
You need a laptop that can run a 3D simulator. 16 GB of RAM is recommended; 8 GB works for runs without the 3D window (author's estimate, not measured). Install the current ROS 2 long-term release and its paired Gazebo release (see Sources), or use a container image for your operating system. Check that each package you need exists for that release before you start, and fall back to the previous release (Jazzy with Gazebo Harmonic) if one is missing. Pin both versions in your repository. Everything in the core path is free.
| Optional kit for Week 16 (estimates, not checked) | Why you need it | Typical price |
|---|---|---|
| Two-wheel robot chassis with motors and wheel encoders | A body that moves | US$40 to 100 |
| Single-board computer that runs ROS 2 on your chosen release | The robot's computer; check support before you buy | US$60 to 120 |
| Microcontroller board with a motor driver | Real-time wheel control (an ESP32 class board works) | US$15 to 30 |
| 2D lidar with a ROS 2 driver | Mapping and obstacle detection | US$80 to 200 |
| Inertial sensor (IMU) breakout | Turn rate for the state estimator | US$10 to 25 |
| Battery pack and a physical emergency stop switch in the motor line | Power, and a stop that does not depend on software | US$30 to 60 |
The minimum optional kit is about US$235 to 535. Nothing in the milestone needs it.
| Risk | Rule |
|---|---|
| A real robot hits a person or a wall | First runs happen with the wheels off the ground. Then cap speed at 0.3 m/s in a cleared area with nobody in it. A physical emergency stop cuts motor power, in hardware. |
| Software is the only stop | Never rely on a program to stop a real robot. The emergency stop must work with the computer off or hung. |
| Battery fire | Charge lithium packs in a fire-safe bag, never unattended, with the charger made for that chemistry. |
| Lidar and eyes | Read the lidar datasheet for its laser class before you point it at anyone. |
| Simulation overstates safety | A passing simulation proves the software does what you modelled. It does not prove the wiring, the motors or the brakes. Say this in the Checkpoint 4 report. |