-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add secondary calibration for Xsens #158
Comments
The implementation can be found at In order to trigger the calibration, you can access the
|
cc @Yeshasvitvs @kouroshD @S-Dafarra |
The result is pretty cool and already avoided us to recalibrate the suit a couple of times. I wonder whether it is possible to add a command to calibrate a whole subtree, e.g. when calibrating the torso, also the arms and the head are modified accordingly. |
implemented in 7719914 It is now possible to calibrate a chain, assuming having the configuration where all the joints in the chain are zero, with the command: Note that this functionality has not been extensively tested and the code is not really clean at this stage. |
That's interesting! How should we use it to calibrate the chest and both arms contemporaneously? |
I would say that, given that we may be interested in calibrating also the head at the same time, you can try with the whole body calibration
|
Please @lrapetti open the relate PR. |
Link or joints? |
Joints, thanks I have fixed it. |
merged #164 |
The objective is to add a secondary calibration to perform on top of xsens calibration in case the suit got miscalibrated. The idea is to have a known orientation and compute the calibration transform from the measured orientation.
In particular, the known position will be considered the position such that the joints are set to zero. In case of calibrating a single link, the known position will be measured by setting to zero the joints from the parent to the given link (e.g. when calibrating the head, all the neck joint are considered zero). When setting the whole body instead, the base position will be considered the one given by xsens, while all the joints are set to be zero.
The text was updated successfully, but these errors were encountered: