Ask Your Question
5

How should we represent the thrusters on an AUV?

asked 2012-10-15 10:08:45 -0500

matthewbot gravatar image

updated 2012-10-15 10:12:33 -0500

We're looking to run ROS on an in-house AUV while hopefully bring more support in ROS for AUVs. While we could just use topics to transport thruster information between our device driver and controller using a specialized topics, I'd like to find a better approach. Our nodes consist of a thruster driver, a controller, and a thruster mapper which converts Wrenches to thruster efforts. I'd like for the mapper to be entirely generic, and somehow retrieve the names, positions, orientations, min/max thrust, etc of the thrusters relative to the vehicle's center of mass, then publish a generic thruster effort message that is compatible with thruster drivers besides our own.

It seems like there are a lot of parallels to URDF and joints in a ground vehicle. Could URDF be extended to support thrusters? What would it take to accomplish this, and would it potentially be merged into a future ros release?

It also seems like this could be done in terms of tf static transforms, one for each thrusters. Would this be a better approach instead?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2015-07-22 11:52:11 -0500

Airuno2L gravatar image

Have you seen the hector_quadrotor package? There might be stuff there you can use.

edit flag offensive delete link more

Your Answer

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

Add Answer

Question Tools

Stats

Asked: 2012-10-15 10:08:45 -0500

Seen: 666 times

Last updated: Oct 15 '12