ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

It's just how teleop_twist_keyboard.py is currently written; It's convenient since the robot keeps moving in the same direction and/or orientation unless different command is sent.

Depending on how serious your usecase is, you could write a patch to maybe send pull request to teleop_twist_keyboard repository; e.g. a code that adds an option to stop the robot per each command. Shouldn't be any difficult.

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2