Closed andreadelprete closed 9 years ago
That was the problem I was mentioning in https://github.com/robotology-playground/idyntree/commit/8cd0d08b2b60ed0d85730c2ca5232dce04b52e8e#commitcomment-8574045 . Unfortunately for some bad design (that was solved in v0.2/new_wbi_ID ) there is a strong coupling between the links present in the urdf file and the iDynTree code itself. Given that the urdf are not present in a unique point, to avoid bigger problems I had to revert the changes we discussed last week. https://github.com/robotology-playground/idyntree/commit/79aa6fc5d783bc989b6f8e8cf6bd25e48ac058f0 The easiest thing you can do is to re-revert locally the line that I commented here: https://github.com/robotology-playground/idyntree/commit/79aa6fc5d783bc989b6f8e8cf6bd25e48ac058f0 and everything should work,
I doubt that's the problem because I'm not using at all the "l_forearm_dh_frame"
The problem is in the mismatch between the link returned in get_iCub_partition
function and the one present in your urdf file. If you generated files with l_forearm_dh_frame
, you should use a consistent get_iCub_partition
function.
Solved in v0.2 (new_wbi_ID).
When using the wholeBodyInterface in wholeBodyReach now I get the following error messages: