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.

Gazebo plugin vs. pr2_mechanism

asked 2011-10-05 01:06:59 -0600

ZdenekM

704 ●30 ●42 ●52

Hello,

I would like to create simulation of simple robot and play with it little. I have (almost) working URDF model a now I have to write some controller. But I'm little bit confused...

First I tried to study how to write Gazebo controller (or plugin?), but documentation is quite poor. Now I'm studying pr2_mechanism stack - it's much better documented and looks like easier way for me.

So my question - what is main difference between robot controller written as Gazebo plugin or as pr2_controller? Which way is encouraged? Is there any important disadvantage when using pr2_controller? Is it possible to use just it without any gazebo plugin?

Thanks for any advice or opinion.

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2011-10-05 07:06:51 -0600

DimitriProsser

11163 ●79 ●116 ●169

Using the pr2_mechanism model is preferred because it provides a ROS interace to Gazebo. Without this interface, you have no acess to the information from your ROS nodes. The pr2_mechanism stack provides some good tutorials for writing your own controller. A tutorial can be found here.

edit flag offensive delete link

add a comment

Question Tools

Stats

Asked: 2011-10-05 01:06:59 -0600

Seen: 360 times

Last updated: Oct 05 '11

Gazebo plugin vs. pr2_mechanism edit

1 Answer

Question Tools

Stats

Related questions

Gazebo plugin vs. pr2_mechanism