Skip to content
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

Timeouts do not stop robot motion #16

Closed
dawonn opened this issue Sep 18, 2013 · 2 comments
Closed

Timeouts do not stop robot motion #16

dawonn opened this issue Sep 18, 2013 · 2 comments

Comments

@dawonn
Copy link

dawonn commented Sep 18, 2013

Shouldn't the mux output a zero cmd_vel when the timeout expires?

Or is that purely the responsibility of the robot driver to make sure it's getting commands consistently? Is there a REP of some sort that defines this behavior?

@corot
Copy link
Collaborator

corot commented Sep 23, 2013

Well, it's intended to just multiplex velocity commands, not to modify them. But velocity_smoother does what you mention, and also kobuki_node has such a timeout. That should be enough in most cases.

@dawonn dawonn closed this as completed Sep 25, 2013
@dawonn
Copy link
Author

dawonn commented Sep 25, 2013

I added logic to my robot's driver node to stop the robot if no commands are received during a timeout period. I guess I'll pretend this is the 'standard' ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants