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

travel (trajectory) length and time of end-effector joint #599

Open
h3ngy1ng opened this issue Jul 18, 2024 · 1 comment
Open

travel (trajectory) length and time of end-effector joint #599

h3ngy1ng opened this issue Jul 18, 2024 · 1 comment

Comments

@h3ngy1ng
Copy link

[rookie] ive a robot arm of 6 joints and would like to know:

  1. how does mtc and rviz know joint1 corresponds to the base joint, etc.
  2. i have the below code snippet calc the total trajectory length and time but i believe it computes both linear and rotary movement of all 6 joints.
    (x, y, z) from home position to an arbitrary (0, 0.5, 1.5) metres:
    Screenshot from 2024-07-18 10-02-32
    Screenshot from 2024-07-18 10-03-57

how do i verify mtc and rviz are reading the last joint (joint 6) as end-effector joint and get the travel (trajectory) length, time of specified joint.

@rhaschke
Copy link
Contributor

  • how does mtc and rviz know joint1 corresponds to the base joint, etc.

From the URDF, which defines the kinematics as a tree. The root of the tree is the base link / joint.

  • i have the below code snippet calc the total trajectory length and time but i believe it computes both linear and rotary movement of all 6 joints.

Indeed this only computes path length in joint space. Have a look at the existing cost functions instead:

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

No branches or pull requests

2 participants