Welcome to MicroROS V2 Robot Car repository
6. FAQ
FAQ
- What is the correct way to start the robot? Answer: After turning on the robot's power, wait until you hear a long beep from the buzzer; that means the startup was successful.
- Why does the robot need parameter configuration? Answer: Because each user's WiFi environment and IP address are different, parameters need to be configured according to the actual situation.
- Why does the robot's buzzer keep beeping "beep—beep—beep"? Answer: The robot beeps "beep—beep—beep" when the battery is low. At this point the robot cannot be controlled. Please turn off the robot's power and then charge the robot.
- When using ROS2 to control the robot and view its status, the data may lag, or a single command may not be executed after it is sent. Why? Answer: This is caused by WiFi network congestion. The ESP32 and the ROS2 program on the virtual machine exchange data over WiFi, so if too many users are using the WiFi, the network quality will be affected, which in turn affects the data exchange between the ESP32 and the ROS2 program on the virtual machine. It is recommended to use a dedicated 2.4G band WiFi for testing. Note that the current ESP32 model is esp32-s3, which does not support 5G band WiFi.
- Why can't the robot be controlled using the ROS2 program? Answer: Check whether someone is currently using a USB Host gamepad to control the robot. If so, stop using the USB Host gamepad, and then the ROS2 program can control the robot, because the USB Host gamepad has higher control priority than ROS2 topic control.
- If you cannot access the Dify backend by entering the virtual machine IP address,
Answer: You can restart the Dify script in the root directory:
sh shutdown_dify.sh
