turtlebot3_robot.launch (burger) doesn't work
Hello everyone,
I'm using Tb3 Burger in ROS1 Noetic with RPi4 (the image is from provided documentation https://emanual.robotis.com/docs/en/platform/turtlebot3/sbc_setup/#sbc-setup). I have configured the wifi network between remote PC and the host (RPi4) and its ping to each other finely. I try to bringup (https://emanual.robotis.com/docs/en/platform/turtlebot3/bringup/#bringup), running the 'roscore' from remote PC, later I tried to launch the Tb3, it says
RLException: Unable to contact my own server at [http://{xxx.xxx.xxx.xxx}:42447/]. This usually means that the network is not configured properly. A common cause is that the machine cannot connect to itself. Please check for errors by running: ping {xxx.xxx.xxx.xxx} For more tips, please see http://wiki.ros.org/ROS/NetworkSetup The traceback for the exception was written to the log file
I've followed every instructions http://wiki.ros.org/ROS/NetworkSetup, there IS stable connection between the host and remote PC (using both ping and netcat).
Is anyone encounter the same problem before? Highly appreciate your guidance.
**apologies I didn't copy paste from the terminal as I left my robot at college, I can't upload the image I've been saving previously as my points is not enough, I promise I type the error correctly and will cut paste next time, thanks for understanding
ubuntu@raspberrypi:~$ roslaunch turtlebot3bringup turtlebot3robot.launch ... logging to /home/ubuntu/.ros/log/41aeb98a-bd51-11ed-b8b9-2b876dc8d9d4/roslaunch-raspberrypi-2991.log Checking log directory for disk usage. This may take a while. Press Ctrl-C to interrupt Done checking log file disk usage. Usage is <1GB.
RLException: Unable to contact my own server at [http://{192.168.254.102}:38529/]. This usually means that the network is not configured properly.
A common cause is that the machine cannot connect to itself. Please check for errors by running:
ping {192.168.254.102}
For more tips, please see
http://wiki.ros.org/ROS/NetworkSetup
The traceback for the exception was written to the log file
Asked by AqilahAD on 2023-03-07 16:34:54 UTC
Comments