arm_navigation package (lack of) scaling issue from urdf files

asked 2011-12-13 02:18:12 -0500

shart115
86 ●5 ●8 ●9

Hi, I tried getting the arm_navigation tool running with my custom (non-PR2) robot .urdf file and had some issues. The biggest (literally) issue was that my .urdf file uses .stl mesh files that are in inches that are manually scaled to meters. For example:

0.0254, being the inches-to-meters scale factor.

Now this all works fine in rviz and gazebo and whatever, but when I run the arm_navigation stack, things go a little crazy---at least in the display. I think the motion planner pieces are working fine, but if you run the planning_components_visualizer tool or the initial wizard to set things up, the green and pink overlays are at the original scale (and thus gigantic).

Anybody seen, or aware of this?

Thanks, Steve

edit retag flag offensive close merge delete

add a comment

1

answered 2011-12-13 03:45:42 -0500

David Lu

10932 ●123 ●219 ●250 http://MetroRobots.com/

updated 2011-12-13 03:46:32 -0500

Yeah, I encountered the same problem.

Relevant Bug Report

edit flag offensive delete link

add a comment

0

answered 2011-12-28 04:23:05 -0500

egiljones
2026 ●5 ●18 ●36

The scale is being correctly applied for collision checking purposes - and thus all your arm navigation components should work correctly. The scale is not being applied to the markers that are sent to rviz, thus making things seem giant. We'll release a bug fix into electric soon.