ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

I have a mobile robot that isn't currently supported by ROS. How should I structure the driver node(s) to expose my robot's integrated sensors and actuators?

asked 2011-11-07 11:36:27 -0600

mmwise gravatar image

Please help in writing up a ROS best practice.

edit retag flag offensive close merge delete



Should we create a wiki page with a tutorial for this answer? If so where should it be created (under the page)?

Gonçalo Cabrita gravatar image Gonçalo Cabrita  ( 2012-08-30 05:08:02 -0600 )edit

That seems like a good place for a link, at least. "Want to add a robot to this list? Here's how."

joq gravatar image joq  ( 2012-08-30 07:37:38 -0600 )edit

Great suggestion !!

Arkapravo gravatar image Arkapravo  ( 2012-10-09 20:02:58 -0600 )edit

I think it's hard to give a general answer. I would use a different software design for a simple robot such as a Roomba (i.e. one node per sensor) than for something like the PR2 (something like pr2_controller_manager and pr2_etherCAT).

Lorenz gravatar image Lorenz  ( 2012-10-09 22:40:57 -0600 )edit

1 Answer

Sort by » oldest newest most voted

answered 2012-10-09 06:44:11 -0600

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

Although this isn't yet a tutorial,

edit flag offensive delete link more


(so that this wasn't still listed as an unanswered question...)

SL Remy gravatar image SL Remy  ( 2012-10-09 06:45:07 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2011-11-07 11:36:27 -0600

Seen: 1,419 times

Last updated: Oct 09 '12