Problems with move_arm & actionlib [closed]
Dear All!! I have a problem with move_arm action server. When I send the MoveArmGoal from my client, sometimes the server doesn't receive the message. The first message always works, but after the second that problem may arise.
Anyone else has this problem? Can you help me?
Thanks!
More details would help assessing what's wrong. What ROS distro are you using?, is it a PR2 or do you have a custom setup?, in what space is your goal specified, joint or task?. Do the logs say something useful (check relevant nodes all the way down to DEBUG severity)?.
0
answered 1 mins ago Ivan Rojas Jofre gravatar image Ivan Rojas Jofre flag of Spain 43 ● 6 http://www.facebook.com/i...
updated just now
Hi Adolfo! You right, I forget this important information, Thanks for reminding
I checked the debug, and print this message when arise the problem: Node: /iri_wam_move_arm Time: 277.955000000 Severity: Debug Location: /opt/ros/electric/stacks/common/actionlib/include/actionlib/server/action_server_imp.h:ActionServer<ActionSpec>::goalCallback:256 Published Topics: /rosout, /allowed_contact_regions_array, /move_iri_wam_markers, /move_iri_wam_markers_array, /move_iri_wam/result, /move_iri_wam/feedback, /move_iri_wam/status, /display_path, /display_joint_goal, /iri_wam_move_arm/statistics, /iri_ros_controller/follow_joint_trajectory/goal, /iri_ros_controller/follow_joint_trajectory/cancel
The action server has received a new goal request
Can you confirm that your controller implementing the follow_joint_trajectory action also receives the goal generated by move_arm?. Look for a debug message that reads "Figuring out new trajectory at xxx.xxx, with data from yyy.yyy", where xxx.xxx and yyy.yyy are timestamps.
Did you end up figuring this one out?. If so, it would be useful to post the answer here for future reference.