I was doing Basic Linux course, at some point work with rosject is needed, where hands-on Simulation workflow and then work with Real robot remotely are introduced. The Simulation part was straightforward, however there was a problem with Real Robot. I made a booking for 25 minutes, when time had come, I connected robot and followed instructions on Jupyter Notebook. First, is to run robot bringup program:
then also in a separate terminal run teleop_twist_keyboard
ros2 run teleop_twist_keyboard teleop_twist_keyboard
None of the controllers worked. The joystick on Remote camera did not work, robot did not move. And also keyboard control launched on separate terminal did not make any difference. I tried to refresh page, nothing helped. Plus, Rdviz also was never summoned, but it did work in Simulation.
Can someone explain what did i wrong? As far as i understand I can control and move robot via joystick right from the moment of connection without any additional commands on terminal.
Did you keep the terminal focused? When using the keyboard teleop program, keep the terminal focused (by clicking on it), otherwise it will not work.
It’s possible the robot itself has issues, suggested by the fact that the Joystick did not work. That said, sometimes the keyboard teleop works even if the Joystick does not.
Based on the information provided, I’m unsure what the problem could have been. Please try again and attach a short screencast to help us understand the situation.
Yes, i wanted to clarify the point 2. The Real Robot should move and react to joystick right away after start w/o any additional configurations and commands on terminal.
I will have to book and check it again, and follow the same instructions game. As far as I understand, no deviations from provided instructions should be done.
Yes, this is right. I apologize if I’ve confused you. The joystick and keyboard teleop are two separate programs. Because of this, the failure of one does not necessarily affect the other.