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.

Sign up for GitHub

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

Jump to bottom

Changing head (neck) joint order #48

Closed
jgvictores opened this issue Apr 11, 2019 · 1 comment
Closed

Changing head (neck) joint order #48

jgvictores opened this issue Apr 11, 2019 · 1 comment
Assignees
@jgvictores
Labels
invalid

Comments

@jgvictores
Copy link
Member

jgvictores commented Apr 11, 2019 •
edited
Loading

As spoken with @rsantos88 @PeterBowman @smcdiaz, as part of Review and Unify TEO kinematic model (#38 and roboticslab-uc3m/teo-developer-manual#40) we are going to change the head (neck) joint order so we can have a nice DH parameter description of the trunk+head kinematic chain (past: 0=no, 1=yes; future: 0=yes, 1=no).

Sorry for the inconveniences! Tasks involved:

  • update diagrams
  • update .ini configuration files
  • update simulation models
@jgvictores jgvictores added announcement Can close without announcement > 1 month horizontal labels Apr 11, 2019
@jgvictores jgvictores self-assigned this Apr 11, 2019
@jgvictores jgvictores mentioned this issue Apr 11, 2019
Closed
jgvictores added a commit to roboticslab-uc3m/teo-configuration-files that referenced this issue Apr 11, 2019
@jgvictores
Invert head joints
905ec31 
- Changing head (neck) joint order)
- roboticslab-uc3m/teo-main#48
jgvictores added a commit to roboticslab-uc3m/teo-configuration-files that referenced this issue Apr 11, 2019
@jgvictores
Invert head joints
cbdd6f7 
- Changing head (neck) joint order
- roboticslab-uc3m/teo-main#48
@jgvictores jgvictores mentioned this issue Apr 11, 2019
Closed
@jgvictores
Copy link
Member Author

False alarm, see solution at roboticslab-uc3m/teo-developer-manual#40 (comment). Closing as invalid, sorry!

@PeterBowman PeterBowman closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgvictores jgvictores

Labels
invalid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jgvictores @PeterBowman