-
Notifications
You must be signed in to change notification settings - Fork 64
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
forwardKinematics is not working consistent? #27
Comments
After a bit debugging I added some tests which showed me, that the Transformation calculated by |
So the forward and inverse kinematics implementation are really just a minor spin-off of this library. They are (and should not be) used for central functions, and do much worse in terms of speed, accuracy and robustness than KDL or other solvers. I just use them to calculate an elbow angle that matches my requirements. As these methods are quite tailored to my needs, I've probably added a fixed offset to the kinematics calculation, leading to this 180° difference between the official and my end-effector position. Please also note that some things changed with libfranka version v0.8.0 in this regard. I'll have a look at your tests soon. |
@pantor @peetCreative Did you manage to resolve these issues in the meantime? |
While adding some tests to my library I came across strange behaviors of the function
Robot::forwardKinematics
. So I added tests #26 to frankx. The first test simply checks ifRobot::forwardKinematics
withRobot::currentJointPositions
results in the same Affine asRobot::currentPose
. As I see in the implementation these functions read (readOnce
) from libfranka. So I ask myself, if the implementation of forwardKinematics is incorrect.However I suspect my self to have a misconception as this function is one of the central functions.
Maybe you want to add the tests anyway to the library.
Thanks
The text was updated successfully, but these errors were encountered: