problem with arm_navigation stack [closed]

edit

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.