-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Turtlebot3 bringup suddenly doesn't work #745
Comments
I also had the very same problem; it seemed to disappear (temporarily) by executing rosrun turtlebot3_bringup create_udev_rules
https://emanual.robotis.com/docs/en/platform/turtlebot3/sbc_setup/#sbc-setup ...and has something to do with USB setup. You have to "expand" the text at the bottom of the page to see it. However, the problem reappeared shortly afterwards, after having used the robot for a few hours, and this time executing the above command did nothing to solve the problem. When I installed the software I followed the manual procedure, which was the only available by then; now you can just download a preconfigured image. I will try this when I have time.... |
I actually did the manual SBC setup and also tried to rerun the command Update: Not for long.. after the third bringup it again doesn't work.. |
@sudo-Boris |
First I tried to reupload the firmare with
I again pressed the reset button and have the issue from before. Update: It seems to work again. But I don't know for how long. |
@sudo-Boris |
It wasn't necessary, it disappeared with the second try. |
ISSUE TEMPLATE ver. 0.4.0
Which TurtleBot3 platform do you use?
Which ROS is working with TurtleBot3?
Which SBC(Single Board Computer) is working on TurtleBot3?
Which OS you installed on SBC?
I did the manual SBC setup in the emanual.
Which OS you installed on Remote PC?
Specify the software and firmware version(Can be found from Bringup messages)
Specify the commands or instructions to reproduce the issue.
roslaunch turtlebot3_bringup turtlebot3_robot.launch
... logging to /home/ubuntu/.ros/log/86af288a-bf01-11eb-b39e-48b02d2b81aa/roslaunch-ubuntu-2658.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.
started roslaunch server https://my_TURTLEBOT_IP:35829/
SUMMARY
PARAMETERS
NODES
/
turtlebot3_core (rosserial_python/serial_node.py)
turtlebot3_diagnostics (turtlebot3_bringup/turtlebot3_diagnostics)
turtlebot3_lds (hls_lfcd_lds_driver/hlds_laser_publisher)
ROS_MASTER_URI=https://my_HOST_IP:11311
process[turtlebot3_core-1]: started with pid [2667]
process[turtlebot3_lds-2]: started with pid [2668]
process[turtlebot3_diagnostics-3]: started with pid [2669]
[INFO] [1622135149.303476, 0.000000]: ROS Serial Python Node
[INFO] [1622135149.398551, 0.000000]: Connecting to /dev/ttyACM0 at 115200 baud
Please describe the issue in detail.
I have worked with the turtlebot without issues, but at one seemingly random point I could not run the bringup of the
turtlebot.
It stops when trying to connect to /dev/ttyACM0.
Other post mentioned it was a battery issue. I charged my turtlebot3 up to full. Then the next bringup worked. But after that
one bringup, it had the same error again, even after again charging those few percentages.
I have tried doing an apt-get update and upgrade -> still the same issue. What could it be? All the sudden stopped
working..
The text was updated successfully, but these errors were encountered: