Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change first point in trajectory to commanded position #1

Merged
merged 3 commits into from
Dec 7, 2016

Conversation

pazeshun
Copy link

@pazeshun pazeshun commented Dec 6, 2016

@pazeshun pazeshun changed the title [WIP] Change first point in trajectory to commanded position Change first point in trajectory to commanded position Dec 6, 2016
@pazeshun
Copy link
Author

pazeshun commented Dec 6, 2016

Ping @wkentaro

1 similar comment
@pazeshun
Copy link
Author

pazeshun commented Dec 7, 2016

Ping @wkentaro

@wkentaro
Copy link
Owner

wkentaro commented Dec 7, 2016

Is this tested with real robot?

@pazeshun
Copy link
Author

pazeshun commented Dec 7, 2016

Yes. With master branch of jsk_apc.

@k-okada
Copy link

k-okada commented Jul 31, 2017

With this PRj, gazebo simulation is not working, joint_trajectory_action do not generate command because of errors,

$ rosrun baxter_interface joint_trajectory_action_server.py --interpolation minjerk
[ERROR] [WallTime: 1501462702.406211] [2142.279000] /rsdk_position_w_id_joint_trajectory_action_server: Exceeded Error Threshold on left_s1: 0.999433532707
[ERROR] [WallTime: 1501462702.407546] [2142.279000] /rsdk_position_w_id_joint_trajectory_action_server: Exceeded Error Threshold on right_s0: 0.653352615824

If we revert following lines, we can solve the problem.

-            first_trajectory_point.positions = self._get_current_position(joint_names)
+            first_trajectory_point.positions = self._get_commanded_position(joint_names)

Why you have to use comanded_position the first trajectory point??? @pazeshun

@pazeshun
Copy link
Author

current_position comes from /robot/joint_states which may be different from the commanded_position.
Please see jsk-ros-pkg/jsk_robot#738 (comment) and RethinkRobotics#77 (comment) for detailed information.

@pazeshun
Copy link
Author

I've also heard simulator problem like start-jsk/jsk_apc#2106 (comment).
Perhaps we have to stop using commanded_position...

@k-okada
Copy link

k-okada commented Jul 31, 2017

thank you for information, Yes I just fixed this problem by writing as same code as start-jsk/jsk_apc#2106 (comment) ...

@k-okada
Copy link

k-okada commented Jul 31, 2017

A robot in gazebo shaking, but the data is clean, need to check on real robot

screenshot from 2017-07-31 17 07 51

rqt_plot -b pyqt /robot/limb/left/joint_command/command[0],/robot/limb/left/joint_command/command[1],/robot/limb/left/joint_command/command[2],/robot/limb/left/joint_command/command[3],/robot/limb/left/joint_command/command[4],/robot/limb/left/joint_command/command[5],/robot/limb/left/joint_command/command[6]  /robot/limb/left/follow_joint_trajectory/goal/goal/trajectory/points[0]/positions[0]  /robot/limb/left/follow_joint_trajectory/goal/goal/trajectory/points[0]/positions[1]  /robot/limb/left/follow_joint_trajectory/goal/goal/trajectory/points[0]/positions[2]  /robot/limb/left/follow_joint_trajectory/goal/goal/trajectory/points[0]/positions[3]  /robot/limb/left/follow_joint_trajectory/goal/goal/trajectory/points[0]/positions[4]  /robot/limb/left/follow_joint_trajectory/goal/goal/trajectory/points[0]/positions[5]  /robot/limb/left/follow_joint_trajectory/goal/goal/trajectory/points[0]/positions[6]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants