I have been follow this tutorial up to the step where I run this command:
ros2 launch tutorial_pkg slam.launch.py on the robot and run rviz2 on my laptop which works just fine. But once I have all this running and visualizing I can no longer use this command to drive the robot: ros2 run teleop_twist_keyboard teleop_twist_keyboard. Prior to starting the tutorial_pkg and rviz2 I have the ability to drive it around but once I start them and after I end them I can no longer drive the robot.
If there is any additional information needed please let me know!
Hi @etanwill
Please provide the following information. I’d like to reproduce the behavior mentioned above or at least collect logs from the ROS driver.
-
Are you using the Rosbot snap? If not, how are you running the ROS driver?
1.1 If so, what ROS middleware is set for sudo snap get rosbot ros?
1.2. Logs can be collected using sudo snap logs rosbot -f.
-
Does the problem mainly occur when a new device communicating via ROS appears on the LAN or is it more likely to happen when running SLAM?
In the middle of trying to get all of the information for the second step all of my systems started working just fine. I have no idea how or why I wish I had more information. If this comes up again and persists or I find a reason why this seems to have fixed itself I will be sure to post again.
Thank you for your time and sorry!
I’m glad it works and thanks for info