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.

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

Expected Output #6

Open
ShrutheeshIR opened this issue Aug 20, 2020 · 3 comments
Open

Expected Output #6

ShrutheeshIR opened this issue Aug 20, 2020 · 3 comments

Comments

@ShrutheeshIR
Copy link

Could you also put up the expected IMU output, so that users can manually verify if the program has compiled successfully and working fine?

Additionally, any guide on how to calibrate our own IMU, i.e. what positions to place the IMU, for how long etc. would be certainly helpful!

Thanks

@pxc2017
Copy link

pxc2017 commented Sep 15, 2020

hello i also want to use this to calibrate my own imu,but confused about the data sample from xsens in bin/test_data, why the all acc datas are more than 30k? we know the raw datas should be small at least the data at z axis closed to 9.8 in this calibration, what pre-process should i do? thx

@bigship
Copy link

bigship commented Sep 16, 2020

Same question as pxc2017

@goksanisil23
Copy link

The method presented in the paper for this work actually calibrates the accelerometer and gyro measurements from the raw digital readings. Hence, it's a calibration procedure to obtain the correct bias and scale factor terms that maps the digital readings to the measurements that physically make sense (i.e m/s² and rad/s)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants