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

[pr2eus] Allow initial av in angle-vector-sequence #270

Closed
wants to merge 1 commit into from

Conversation

pazeshun
Copy link
Collaborator

@pazeshun pazeshun commented Dec 5, 2016

@pazeshun pazeshun changed the title [WIP] Allow initial av in angle-vector-sequence [WIP] [pr2eus] Allow initial av in angle-vector-sequence Dec 5, 2016
@pazeshun
Copy link
Collaborator Author

pazeshun commented Dec 6, 2016

Tested in Baxter with jsk-ros-pkg/jsk_robot#741

@pazeshun pazeshun changed the title [WIP] [pr2eus] Allow initial av in angle-vector-sequence [pr2eus] Allow initial av in angle-vector-sequence Dec 6, 2016
@pazeshun
Copy link
Collaborator Author

pazeshun commented Dec 6, 2016

When you do

24.irteusgl$ send *ri* :angle-vector-sequence (list av1 av2) (list 0 :fast) nil 0 :scale 10.0 :allow-initial-av t

you can get following output

$ rostopic echo /robot/limb/left/follow_joint_trajectory/goal 
header: 
  seq: 1
  stamp: 
    secs: 1480988810
    nsecs: 859410541
  frame_id: ''
goal_id: 
  stamp: 
    secs: 0
    nsecs:         0
  id: 1480988810859972236_/default_robot_interface_1480988279165454790_88580_/robot/limb/left/follow_joint_trajectory_11
goal: 
  trajectory: 
    header: 
      seq: 0
      stamp: 
        secs: 1480988810
        nsecs: 859410541
      frame_id: ''
    joint_names: ['left_s0', 'left_s1', 'left_e0', 'left_e1', 'left_w0', 'left_w1', 'left_w2']
    points: 
      - 
        positions: [0.8732185635037704, -0.35051461003181683, -2.58207316120812, 1.451912815733543, 1.266301140399408, 0.9261409006858177, -0.07171360183364295]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: []
        effort: []
        time_from_start: 
          secs: 0
          nsecs:         0
      - 
        positions: [0.6889973932315314, -0.40928755815992957, -2.4558860484054907, 1.2745174531519226, 1.3166378530097589, 0.8595486641241652, -0.007423700762887047]
        velocities: [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
        accelerations: []
        effort: []
        time_from_start: 
          secs: 1
          nsecs: 228141136
  path_tolerance: []
  goal_tolerance: []
  goal_time_tolerance: 
    secs: 0
    nsecs:         0
---

You can set time_from_start to zero only in first point of trajectory (I called that trajectory initial av).

Please review this.

@pazeshun
Copy link
Collaborator Author

pazeshun commented Dec 6, 2016

I talked to @k-okada in offline.
I understand I should fix baxter_interface.
So is this PR unnecessary? If this PR is totally useless to other robots, I'll close this

@pazeshun
Copy link
Collaborator Author

pazeshun commented Dec 6, 2016

@pazeshun pazeshun closed this Dec 6, 2016
@pazeshun pazeshun deleted the let-init-av branch December 6, 2016 06:41
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.

[Baxter] Baxter's arm goes slightly down when trajectory starts
1 participant