I booked a slot and connected to the Fastbot, to try and complete the “wall following” exercise. However, the robot does not move. It does nto move with the joystick, and it does not move with simple pub commands to /cmd_vel. However, the position in the /odom still changes rapidly over time. The live camera shows no motion.
I’m totally confused, what does this all mean?
@kk_kyberkore
I apologize for that bad experience 
It could be a temporary problem with the robot. Could you please check again?
Sometimes the robot “develops a mind of its own” 
and has to be rebooted.
Hi.
I booked a new slot today and it still won’t move. Not with the joystick, not with publishing ant /cmd_vel.
I tried disconnecting and re-connecting a few times, but it didn’t help.
Could you please check?
Indeed, the joystick is not working (we’re looking into that), but teleop and publishing to /cmd_vel are.
Please see the video below. When using teleop, please ensure the keyboard is focused when pressing the indicated keys.
I watched the video, thanks. Perhaps I should have said earlier, at the moment I’m working with ROS, not ROS2. I’m currently going through the “ROS Basics in 5 Days”. Will it still work with ROS, or are real robots only combatible with ROS2?
Oh, I see. I checked on ROS 2. Let me confirm with a ROS 1 rosject - it should work with that also.
If you can look at the screenshot, you can see the /cmd_vel topic correctly gets the command to move. However, the robot does not move. When I try to use teleop it says “waiting for subscribers”.
So, teleop found its subscriber and started publishing, but the robot will not move. I run teleop on terminal 1 and rostopic echo on terminal 2. When I press “i” and “j” I get linear.x and angular.z respectively in echo. But the robot does not move.
I have confirmed that the robot is not responding to ROS 1. We are looking into it. I apologize for the inconvenience.
In the meantime, please continue with the course. I’ll let you know once it’s fixed.
Hi,
I have connected to turtlebot in real robot lab and receiving live video feeds. When I try to move the robot with onscreen joy stick, it does not respond. When attempting to move the robot through terminal, by using teleop_twist_keyboard.py, it returns a msg saying Waiting for subscriber to connect to /cmd_vel. I have attached screenshot,
For the command rostopic list, it returns active topics (also in the screenshot).
How do I get the robot to respond to joystick commands?
I am using google chrome browser.
This has been fixed. The robot now works with ROS 1. Could you please try again?
It still won’t move.
When using teleop, it keeps repeating “Waiting for subscribers”. It only starts when I rostopic echo on the other terminal. Could this mean that the robot itself is not subscribed to the topic?
Rostopic info says there is a “/ros_bridge (http://fastbot:40231/)” subscriber (as well as publisher).
With a rostopic pub command, it still won’t move - which makes sense, as both teleop and rostopic pub result in Twist messages in /cmd_vel. Something is probably wrong in the way the robot subscribes to the topic.
If there’s any way that we can both look at it at the same time, it would be great.
@kk_kyberkore @sarva86
Oops, so sorry about this. We definitely fixed and tested, and it worked then. But now we see it does not work anymore
We are taking a deep dive into this failure to get it working reliably again. I apologize again for the inconvenience.
Please proceed with the course and return to the Real Robot project later. Thanks in advance for your patience.
Hello @kk_kyberkore @sarva86, thank you for your issue reporting.
Based on your description, we have now changed the underlying system that makes the fastbot available in ROS 1. We have tested multiple times, and we have not experienced the Waiting for subscriber to connect to /cmd_vel anymore. So it should be fixed.
Thank you for your patience
It has been fixed indeed. The joystick works fine now, and my own rosject script works as intended. Thank you.
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.
