Choose the physical model first
TurtleBot3 is sold in more than one configuration. The ROS examples expect a matching model parameter, such as burger or waffle_pi. That choice determines which robot description, frame geometry and sensors the software expects. Using the wrong model can produce misleading visualization and navigation parameters.
The basic platform includes a mobile base with motor control and an OpenCR controller. Robotics projects built around different range sensors and onboard computers need their own compatible wiring, drivers and configuration.
Mapping and navigation are different jobs
In the official ROS 2 workflow, the user first brings up the robot and runs a SLAM package while moving around the space. The resulting map records observed walls and obstacles along with estimated motion. It is then saved for use by the navigation system.
Navigation2 loads the map, estimates the initial robot pose and plans a path toward a goal. If the localization estimate does not align with the laser scan, the robot may plan from the wrong part of the room. ROBOTIS instructs users to set the initial pose in RViz and check the sensor overlay before sending a target.
A practical failure to investigate
Suppose the robot moves straight when commanded, but its map slowly rotates during a loop. Check wheel diameter, axle separation, encoder calibration and the relationship between odometry and the IMU or range data before changing global-planner settings. This is a proposed troubleshooting approach, not a test performed by TechniaHQRobot.
Simulator examples are useful for learning ROS topics and transforms, but they omit wheel slip, imperfect sensors and physical obstacles that affect a classroom robot.
Historical context and licensing
TurtleBot originated at Willow Garage before the TurtleBot3 generation was developed by ROBOTIS. The broader TurtleBot history appears on Wikipedia, but the Robotis e-Manual is the source for current TurtleBot3 installation commands and supported ROS versions.
Choose Burger or Waffle and assemble the chassis
Use matching revisions of parts, firmware and instructions. These steps summarize project documentation; no physical build was performed for this article.
Official files and manuals 5 references
Assembly sequence 5 steps
Select Burger, Waffle or Waffle Pi
The BOM lists different chassis plates, motor types, camera accessories and caster configurations. Use one assembly PDF.
Manufacturer's instructions ↗Build chassis and DYNAMIXEL drive train
Attach plates, wheel actuators and caster supports following the chosen hardware setup document.
Manufacturer's instructions ↗Install OpenCR, Raspberry Pi and LDS lidar
Route sensor and power lines with the correct model's mounting locations and keep the rotating lidar clear.
Manufacturer's instructions ↗Prepare the supported ROS 2 branch and firmware
Configure the OpenCR interface and model variables for Burger or Waffle before moving the robot.
Manufacturer's instructions ↗Calibrate drive and only then start mapping
Test wheel directions, TF and laser data before SLAM. Save a map and use navigation only with a valid costmap and obstacle sensor.
Manufacturer's instructions ↗
Hardware CAD, sensor setup and ROS navigation
Answers are based on published source material and project documentation. Their order does not represent search volume.
01Where are TurtleBot3 STL, CAD and PCB Gerber files?
ROBOTIS links mechanical hardware models and OpenCR board/PCB files from the official OpenSource page. Select the correct Burger or Waffle design.
Sources Official project source ↗
02Are Burger and Waffle assembly parts interchangeable?
No. The BOM identifies different motors, numbers of plates, casters and sensors. Choose the matching hardware PDF.
Sources Official project source ↗
03How do I assemble a TurtleBot3 from a kit?
The official hardware setup page supplies separate assembly manuals for Burger, Waffle and Waffle Pi, alongside videos.
Sources Official project source ↗
04Why does SLAM produce no map?
Before blaming SLAM, check that lidar scans, TF transforms and odometry are being published by the correct robot model. The official SLAM guide details its launch configuration.
Sources Official project source ↗
05Can I navigate without an existing map?
Robot navigation examples usually require a valid map or an appropriate map-building/localization mode. Follow the Navigation guide and check goal, costmap and laser inputs.
Sources Official project source ↗
06Can I build an OpenCR board independently?
ROBOTIS publishes OpenCR schematics, Gerber designs, firmware and hardware references; fabrication and testing of the controller require separate electronics work.
Sources Official project source ↗
What to check before building TurtleBot3
Build and integration
Select Burger or Waffle hardware before reading the parts and sensor instructions. The main ROS repository contains launch and control packages; simulation tools live in companion TurtleBot3 repositories. ROBOTIS also publishes board, chassis and variant hardware materials in its open-source documentation. Mapping and autonomous navigation require configured range sensing and correctly calibrated wheel motion.
Known constraints
The platform is split across several software repositories, and supported ROS branches vary. Not all example behaviors are provided by the base hardware alone: SLAM and navigation need supported sensor and compute configurations. Core software uses Apache-2.0 while some components and documentation have different terms.
Original documentation
Found a changed specification? Submit a correction with its source ↗