Waiting for action server when using SimpleActionClient

edit

The way action client waits for server is by looking at a bunch of ROS topics and trying to get messages on all of them. You can look at the code in the "actionlib" package to see exactly how it is working

 roscd actionlib
 cd src/actionlib/
 EDITOR action_client.py

That said you should just try

 rostopic list | grep <the name of your topic - something about right arm I guess>

to see which topics are there (they should be something about status/feedback/result) and then

 rostopic echo <topic that you care about>

to see whether the topic is published at all.

I just tried this in diamondback (in the simulator) using the code (in src/move_arm_joint_goal.cpp) in pr2_arm_navigation_tutorials. Are you giving the right argument to the action client - it should be "move_right_arm" if you are addressing the right arm.

I'm having this problem too. I'm running diamondback (1.4.8). I can produce it with pretty recently checked-out pr2 stacks with the following

1. roslaunch pr2_gazebo pr2_empty_world.launch
2. roslaunch pr2_3dnav right_arm_navigation.launch
3. roscd pr2_navigation_tutorials; ./bin/move_arm_joint_goal

This hangs on line 10: move_arm.waitForServer();

roswtf tells me that all the move_right_arm subscriptions are unconnected. rostopic echo move_right_arm/* doesn't give me any messages either.

Can someone confirm this? I followed the relevant tutorials to the letter. I would very much appreciate any debugging suggestions.

Thanks, Tom