Robot Operations

After configuring your Raspberry Pi and flashing the firmware, you can start the robot’s onboard ROS 2 stack. This module describes the launch command and how to verify that all expected topics and nodes are active.

Examine the output to confirm that sensor topics like /scan and /camera/image_raw are present and that nodes such as rplidar_node, camera_node and micro_ros_agent are running. If any expected topics or nodes are missing, troubleshoot by reviewing earlier setup steps.

To safely power off the robot, you should first stop any running ROS nodes and processes, then issue a shutdown command. Abruptly disconnecting power can corrupt the filesystem or leave hardware in an unsafe state.

Rebooting the robot is useful after editing configuration files or applying firmware updates. A reboot cleanly shuts down processes and restarts the operating system.

In an emergency—such as a runaway robot or hardware failure—you must quickly stop all software and power down the system to prevent damage or injury. Follow these steps:

If software commands fail or the system is unresponsive, cut power by switching off the power supply or unplugging the battery. After addressing the issue, inspect hardware and restart with the normal procedure.

Consistent maintenance prolongs the life of your robot and catches issues before they become critical. This module outlines daily and weekly checks you can perform using ROS 2 commands.

Observe the outputs for each sensor to ensure data is being published. The /cmd_vel publication should cause the robot’s wheels to turn briefly—ensure the workspace is clear before running this test. Schedule deeper maintenance (tightening hardware, inspecting cables, updating packages) weekly or monthly as recommended by the program.