Skip to content

Issues with Cartesian interface #686

Answered by pattacini
paliasgh asked this question in Q&A
Discussion options

You must be logged in to vote

Hi @paliasgh

Here's my suggestions:

drvArmL.view(iarm);

// better off complying with the proper size of DOF
Vector curDOF;
iarm->getDOF(curDOF);
auto newDOF = curDOF;
newDOF = 1;  // ensure that all DOFs are enabled to then tune them up below

// iCub has a narrow reachable space because it's a baby; hence, let's use the torso too
newDOF[0] = 1;  // enable torso pitch
newDOF[1] = 0;  // torso roll is usually not required
newDOF[2] = 1;  // enable torso yaw
iarm->setDOF(newDOF, curDOF);

// reaching with prioritized position (default) is always the best option for us, especially when grasping is considered
// the solver will strive to comply with the target position and then will adapt to…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@paliasgh
Comment options

Answer selected by paliasgh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants