Ask Your Question
0

problem with arm_navigation stack [closed]

asked 2012-02-27 01:31:51 -0500

Hi everyone!!

I have a problem with arm_navigation stack. I need to get a trajectory with target time, in other words, I want a path that executed in that time. The MotionPlanRequest message, that it inside move_arm_action, has two parameters for to defined path duration. But, the result trajectory time is smaller that target time.

Any ideas??

Thanks!!

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Ivan Rojas Jofre
close date 2013-06-20 10:50:14

1 Answer

Sort by ยป oldest newest most voted
1

answered 2012-02-28 05:52:23 -0500

egiljones gravatar image

None of the planners we release really plan for dynamics, so while they are part of the message those values are not used. If the problem is that the resulting trajectories are too fast, that should be pretty easy to fix - just increase the times on the trajectory points before you send the path to the controller. At least the PR2 controller should be able to act correctly based on that. If the paths are too slow there's not that much that can be done about that - you can potentially increase the acceleration limits in the joint_limits.yaml file and move the arms somewhat faster. Finally, the right way to do this is have the planner reason more about timing, but that's not something our planners currently do.

edit flag offensive delete link more

Question Tools

Stats

Asked: 2012-02-27 01:31:51 -0500

Seen: 154 times

Last updated: Feb 28 '12