How to build TurtleBot3 (Burger / Waffle Pi): the whole process
217 steps to build TurtleBot3 (Burger / Waffle Pi), from buying parts, printing and assembly to software, calibration and training, with the bill of materials, shop link…
Burger (Raspberry Pi 4 4GB) $783.50, Waffle Pi (Raspberry Pi 4 2GB) $1,908.31 and (4GB) $1,933.61 (robotis.us, 2026‑10‑31, all shown in stock; shipping calculated at checkout, tax not mentioned); kits include the Pi, lidar, battery, charger and power supply, and no self-sourced BOM total is given
Buy parts
- Buy compatible DYNAMIXEL and ROBOTIS sensors
Besides controlling DYNAMIXEL actuators, the OpenCR1.0 control board can also use ROBOTIS sensors such as Touch, Infrared and Color sensors.
- Prepare the microSD Card and Reader
If the PC has no microSD slot, use a microSD card reader to burn the recovery image. The reader is not included in the TurtleBot3 package.
Print and make
- Download 3D CAD data on Onshape for printing
The 3D CAD data for TurtleBot3 components is released via Onshape, accessible in a web browser on desktop PC, laptop and portable devices.
- Download OpenCR1.0 board files to make your own
To make or modify an OpenCR1.0 board yourself, its schematics, PCB gerber files, BOM and firmware source code are available under open-source licenses.
Assemble
- Connect OpenCR to Raspberry Pi
Connect the OpenCR to the Raspberry Pi with a micro USB cable.
- Connect the HDMI cable
Connect the HDMI cable before powering on the Raspberry Pi; otherwise, its HDMI port will be disabled.
Software
- Connect SBC power and peripherals
Power the SBC from a wall supply rather than a battery.
- Connect display and input devices
Connect an HDMI monitor, keyboard, and mouse to complete setup.
- Prepare microSD card and reader
If the PC has no microSD slot, use a microSD card reader to burn the recovery image.
- Download or update Raspberry Pi Imager
Download Raspberry Pi Imager to install Ubuntu Server 22.04 for Raspberry Pi; update it to the latest version if already installed.
- Choose deb or apt installation
Install either the deb or apt release of rpi-imager.
- Download the deb file
Download the Raspberry Pi Imager deb file.
- Install the deb release
Change to the Downloads directory and install the downloaded deb file with dpkg.
- Resolve deb dependency errors
If dependency errors occur, force the installation with apt-get, then run rpi-imager.
- Install and launch with apt
Install rpi-imager with apt, then launch it.
- Run Raspberry Pi Imager
Run Raspberry Pi Imager to install Ubuntu on the Raspberry Pi.
- Choose the operating system
Click CHOOSE OS in Raspberry Pi Imager.
- Select another general-purpose OS
Select Other gerneral-purpose OS.
- Select Ubuntu
Select Ubuntu from the available operating systems.
- Select Ubuntu Server 22.04.5
Select Ubuntu Server 22.04.5 LTS (64-bit) for RPi 3, 4, and 400, not the desktop OS.
- Select the micro SD card
Click CHOOSE STORAGE and select the micro SD card.
- Start the Ubuntu installation
Click Next to install Ubuntu to the selected storage device.
- Edit Wi-Fi and SSH settings
Click Edit Setting to configure Wi-Fi and SSH.
- Set account, Wi-Fi, and SSH options
Set the username and password, wireless LAN, and wireless LAN country. In the SERVICES tab, enable SSH and select password authentication.
- Skip the later Wi-Fi configuration
After completing this setup, skip the Wi-Fi configuration through step 4.
- Connect HDMI before powering on
Connect the HDMI cable before powering on the Raspberry Pi; otherwise, its HDMI port will be disabled.
- Edit the network configuration file
Use nano to edit /etc/netplan/50-cloud-init.yaml.
- Open the automatic upgrade configuration
Use nano to edit /etc/apt/apt.conf.d/20auto-upgrades.
- Disable automatic update settings
For the TurtleBot3 SBC, set package-list updates and unattended upgrades to 0.
- Mask the network wait service
Mask systemd-networkd-wait-online.service on the Raspberry Pi.
- Disable suspend and hibernation
Disable the sleep, suspend, hibernate, and hybrid-sleep targets on the TurtleBot3 SBC.
- Reboot the Raspberry Pi
Reboot the Raspberry Pi to apply the configuration.
- Connect over SSH from the remote PC
After rebooting, connect from the remote PC terminal using the Ubuntu username and Raspberry Pi IP address. Enter the password set in step 1.
- Edit the SSH configuration
Use nano on the Raspberry Pi to edit /etc/ssh/sshd_config.d/50-cloud-init.conf.
- Install net-tools and check the IP
Install net-tools on the Raspberry Pi, then check the IP address with ifconfig.
- Connect again from the remote PC
Run the SSH command on the remote PC and enter the Ubuntu system password.
- Create 2GB swap memory
When using the TurtleBot3 2GB, create 2GB of swap memory to prevent out-of-memory or package-building failures.
- Enable swap after reboot
Add the swap file to /etc/fstab so it is activated automatically after a reboot.
- Install core build dependencies
Install python3-argcomplete, python3-colcon-common-extensions, libboost-system-dev, and build-essential.
- Install ROS drivers and messages
Install the HLS-LFCD-LDS driver, TurtleBot3 messages, Dynamixel SDK, Xacro, and libudev-dev.
- Clone TurtleBot3 repositories
Clone the humble branches of turtlebot3, ld08_driver, and coin_d4_driver into ~/turtlebot3_ws/src.
- Remove unused packages
Enter the TurtleBot3 repository and remove the turtlebot3_cartographer and turtlebot3_navigation2 directories.
- Build the TurtleBot3 workspace
Return to the workspace, load the ROS Humble environment, and build using symlink installation with one parallel worker.
- Save and load workspace environment
Add the TurtleBot3 workspace installation environment to .bashrc and load it immediately.
- Configure OpenCR USB port
Copy the TurtleBot3 CDC udev rule, reload the rules, and trigger udev.
- Set the ROS domain ID
The ROS_DOMAIN_ID must match between the Remote PC and TurtleBot3 for communication in the same network environment.
Calibrate and test
- Confirm Burger model output
Check the terminal output to confirm that TURTLEBOT3_MODEL is set to burger.
- Set the BURGER Model
Set the TURTLEBOT3_MODEL environment variable to burger to select the TurtleBot3 BURGER.
- Set the ROS domain ID
Set ROS_DOMAIN_ID to 30 on both the Remote PC and TurtleBot3 SBC so they use the same ROS_DOMAIN_ID.
- Match the RMW implementation
Set RMW_IMPLEMENTATION to rmw_fastrtps_cpp on both the Remote PC and TurtleBot3 SBC so they use the same ROS middleware implementation.
- Permit Wi-Fi multicast
Check that the Wi-Fi router supports multicast; if it does, configure the router to permit multicast.
- List ROS topics
Run the topic-list command and check for topics such as battery_state, cmd_vel, imu, joint_states, magnetic_field, odom, parameter_events, robot_description, rosout, scan, sensor_state, tf, and tf_static. The topic list may vary depending on the installed ROS package version.
- List ROS services
Run the service-list command and check for services and parameter interfaces under diff_drive_controller, hlds_laser_publisher, launch_ros, motor_power/reset, sound, and turtlebot3_node.
- Select the velocity message type
From the Jazzy version, the cmd_vel topic uses the TwistStamped type. To use the Twist type, set enable_stamped_cmd_vel to false in the bringup package.
- Connect to Raspberry Pi via SSH
On the remote PC, press Ctrl + Alt + T to open a new terminal, connect through SSH using the Raspberry Pi's IP address, and enter the Ubuntu OS password on the Raspberry Pi.
- Launch TurtleBot3 basic packages
On the Raspberry Pi terminal, specify the TurtleBot3 model, then launch the bringup robot to run the basic applications.
- Check Burger model startup output
When TURTLEBOT3_MODEL is set to burger, check that the terminal output matches the startup output shown in the document.
- Confirm gyro calibration and device initialization
In the terminal output confirm that DynamixelSDKWrapper opened the port /dev/ttyACM0 and changed the baudrate, that gyro calibration ended, and that the battery, IMU, sensor and joint state publishers plus the motor power server were created.
- Confirm diff drive controller odometry running
Finally confirm that diff_drive_controller initialized odometry and prints Run!, meaning the robot is ready.
- Match ROS_DOMAIN_ID
Confirm that the Remote PC and TurtleBot3 SBC use the same ROS_DOMAIN_ID, and set it to 30 on both.
- Match RMW implementation
Confirm that the Remote PC and TurtleBot3 SBC use the same RMW implementation, and set it to rmw_fastrtps_cpp on both.
- Check Wi-Fi multicast support
Check whether the Wi-Fi router supports multicast; if it does, configure the router to permit multicast.
- Display topic list
Run the topic-list command; the displayed contents may vary depending on the installed ROS package version.
- Display service list
Run the service-list command; the displayed contents may vary depending on the installed ROS package version.
- Check Burger model launch messages
If the TurtleBot3 model is burger, the terminal will display the messages shown in the document.
- Confirm the OpenCR connection
After bringup starts, the system connects to the OpenCR board and reports that core(v1.2.1) is compatible with TB3 Burger.
- Complete automatic gyro calibration
After connecting to the OpenCR, the system automatically starts gyro calibration and finishes when the log shows “Calibration End.”
- Check swap memory
Run the free -h command to check swap memory.
- Confirm the default ROS domain ID
The default ROS_DOMAIN_ID of the TurtleBot3 is 30.
- Configure ROS domain ID as 30
Configure the ROS_DOMAIN_ID of both the Remote PC and TurtleBot3 SBC to 30, and add the setting to .bashrc.
- Enable the legacy camera driver
Run raspi-config, select I1 under Interface Options, and enable legacy camera support to use bcm2835 MMAL. After this is completed, the camera node in camera-ros cannot detect the camera, and the legacy driver must be disabled again to use camera-ros later.
- Modify the legacy camera configuration
Add camera_auto_detect=0, start_x=1, and the line enabling the legacy camera stack for bcm2835-v4l2. If camera-ros will be used afterward, remove or comment out camera_auto_detect=0, start_x=1, and dtoverlay=imx219.
- Check the camera device name
Run v4l2-ctl --list-devices to check the camera name. In this case, the camera name is mmal_service_16.1.
- View the camera image input
Run rqt_image_view on the remote PC to verify that the camera node is publishing image data correctly by displaying ROS 2 image topics.
- Follow the camera calibration instructions
If you plan to use advanced vision features such as camera calibration, follow the detailed instructions in the linked guide.
- Troubleshoot the camera calibration file error
If the “Unable to open camera calibration file” error appears, check the solution provided in the linked troubleshooting guide.
- Select Other general-purpose OS
In the operating system selection window, click Other gerneral-purpose OS.
- Select Ubuntu Server 24.04.2
Select Ubuntu, then choose Ubuntu Server 24.04.2 LTS 64-bit, which supports RPi 3/4/400. Choose Server OS rather than desktop OS.
- Select the microSD Card
Click CHOOSE STORAGE and select the microSD card used to install Ubuntu.
- Configure Wi-Fi and SSH
Click Edit Setting, set the username and password, Configure wireless LAN, and Wireless LAN country. In the SERVIES tab, enable Enable SSH with Use password authenication.
- Skip Repeated Wi-Fi Configuration
After completing the configuration in Imager, skip the first four steps of the following Wi-Fi configuration section.
- Power On the OpenCR
After assembling the TurtleBot3, connect power to the OpenCR and turn on the power switch. The red Power LED will turn on.
- Place Robot in a Clear Area
Place the robot on flat ground in a wide open area. A safety radius of 1 meter (40 inches) is recommended for the test.
- Test Forward Movement
Press and hold PUSH SW 1 for a few seconds to command the robot to move 30 centimeters (about 12 inches) forward.
- Test 180-Degree Rotation
Press and hold PUSH SW 2 for a few seconds to command the robot to rotate 180 degrees in place.
- Power the OpenCR and Start the Robot
After assembly, connect power to the OpenCR and turn on the power switch; the red Power LED will turn on.
Use it
- Load TurtleBot3 in Rviz
Run the TurtleBot3 Rviz2 launch file to display the robot in Rviz.
- Load TurtleBot3 in Rviz
Run the TurtleBot3 rviz2 launch file.
- Run roscore on the remote PC
Run roscore on the remote PC.
- Connect to Raspberry Pi via SSH
Open a new terminal on the remote PC with Ctrl + Alt + T, then connect to Raspberry Pi using SSH. The default password is turtlebot.
- Launch TurtleBot3 applications
Bring up the basic packages on the TurtleBot3 SBC to start the required TurtleBot3 applications.
- Follow the RViz launch guide
Follow the RViz launch guide linked in the document.
- Control the Robot with the Keyboard
After the node launches successfully, use w/a/s/d to move; w/x increases or decreases linear velocity, a/d increases or decreases angular velocity, space or s forces a stop, and CTRL-C quits. The values are approximately 0.22 linear and 2.84 angular for Burger, and 0.26 linear and 1.82 angular for Waffle and Waffle Pi.
- Control the Robot with RC-100B
Use Up/Down on the RC-100B to increase or decrease linear velocity, and Left/Right to increase or decrease angular velocity.
- Use the RC-100B controller
Use the RC-100B with the BT-410 Bluetooth module and OpenCR firmware; Waffle Pi includes the controller and Bluetooth modules.
- Enable TurtleBot3 remote control
Teleoperate the TurtleBot3 by remote control; when testing on a table, be careful because the robot may fall off the edge.
- Control movement with the keyboard
Move with w, a, s, and d; use w/x to increase/decrease linear velocity and a/d to increase/decrease angular velocity, press space or s to force stop, and press CTRL-C to quit.
Common problems
- SBC setup fails due to dependencies, architecture detection, or agent installation errors. #702 #304 #461 #401 #455
- SBC cannot communicate with the PC, or ROS stops responding after updates. #703 #431
- ROS 2 crashes or fails due to OS, clock, or version incompatibilities. #593 #1079 #546
- Camera, OpenCR upload, or robot bringup fails during setup. #863 #240 #149
- SLAM produces no map or freezes robot position while mapping. #80 #83 #195 #307
- Navigation localization and RViz frames suffer transform, position, or orientation errors. #78 #266 #362 #99 #203
- Odometry values or frames become implausible, inconsistent, or unstable. #926 #847 #880
- Teleoperation and velocity commands fail to update robot motion. #809 #1028
Parts
- Raspberry Pi 4 (Burger 4GB; Waffle Pi 2GB or 4GB) + OpenCR 1.0 (STM32F746, Cortex‑M7 at 216 MHz)
- Two DYNAMIXEL wheel actuators: XL430‑W250‑T on Burger (1.4 N·m stall at 11.1V), XM430‑W210‑T on Waffle Pi
- LDS‑03 360° lidar with USB2LDS; Waffle Pi adds a Raspberry Pi Camera v2.1, RC‑100B remote and BT‑410 Bluetooth
- 11.1V 1,800 mAh Li-Po battery (19.98 Wh) with charger and a 12V 5A supply; about 2.5 hours of runtime (Burger) or 2 hours (Waffle Pi), about 2.5 hours to charge
- Burger 138×178×192 mm, 1 kg, up to 0.22 m/s, 15 kg payload; Waffle Pi 281×306×141 mm, 1.8 kg, 0.26 m/s, 30 kg payload
- Injection-moulded waffle plates, supports, tyres and ball casters, screws and rivets (e-Manual parts list)
Tools
- A screwdriver and rivet tool come in the kit (parts list)
- A remote PC running Ubuntu 22.04 or 24.04, plus flashing a microSD image for the Pi
- Structural changes can be 3D printed from the Onshape CAD
Skills
- Linux and ROS 2 (Humble / Jazzy)
- SLAM (Cartographer), Nav2 navigation and Gazebo simulation
- Optional: OpenCR firmware work in the Arduino IDE
Software
- turtlebot3 ROS 2 packages (latest 2.3.7, 2026‑06‑15; humble, jazzy and rolling branches)
- turtlebot3_simulations (Gazebo Harmonic on Jazzy) and a Docker setup (since 2.3.4)
- e-Manual examples: AutoRace autonomous driving, mobile manipulation with an OpenMANIPULATOR‑X, the home service challenge
- OpenCR firmware (the turtlebot3_ros2 library in the OpenCR repo) and the coin_d4_driver for the LDS‑03