Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to contact ROS master at [http:https://{10.0.0.xxx}:11311] The traceback for the exception was written to the log file #706

Open
Paulino1956 opened this issue Feb 10, 2021 · 1 comment

Comments

@Paulino1956
Copy link

got this message:" unable to contact ROS (running on Melodic) master at [http:https://{10.0.0.xxx}:11311] The traceback for the exception was written to the log file"
after running on shell 1 pi@raspberrypi:~ $ roslaunch turtlebot3_bringup turtlebot3_robot.launch

while open shell 2 (master) running $roscore

at screen:

NODES

auto-starting new master
process[master]: started with pid [14369]
ROS_MASTER_URI=http:https://10.0.0.xxx:11311/

setting /run_id to 6972849e-6bd0-11eb-9cce-d8c0a6261e0f
process[rosout-1]: started with pid [14380]
started core service [/rosout]
(STOPPED HERE)

Thanks in advance for you help !

@ROBOTIS-David
Copy link

ROBOTIS-David commented Feb 16, 2021

@Paulino1956

Hi, Paulino1956

Thank you for opening the issue on here.

  1. Are you using Raspbian ? If so, the suggested OS for the SBC is the Ubuntu 18.04.3 Preinstalled Server ARM64 for Raspberry Pi3.

  2. Make sure that the Remote PC and SBC (TurtleBot3) are working under the same wifi address. See Network Configuration to set the network. Note that, you need to select the proper ROS version in the e-Manual.

  3. You can directly ask your inquiry to the issue section on the TurtleBot3's github section. One of engineer will address your issue as soon as possible.

@ROBOTIS-Will ROBOTIS-Will transferred this issue from ROBOTIS-GIT/emanual Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants