The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The MotionCommandBtn message was dropped in trunk because it only enabled a few hardcoded behaviors. The replacement is the nao_controller node in nao_driver which enables arbitrary joint trajectories and pose_manager in nao_remote which enables the robot to assume fixed body poses via an actionlib interface. All this is fully configurable and a few default poses are loaded from the parameter server: "crouch" (sit down), "zero", "init" (stand up).
Your robot can enter these poses if nao_controller and nao_remote are running (there are configured launchfiles in their packages), and you call the corresponding action just like the Gamepad teleoperation does on button presses. The new actionlib interface has the advantage that you can now be sure that the action was called properly and finished completely.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
