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

IMU calibration #74

Open
pzhu008 opened this issue Nov 8, 2019 · 8 comments
Open

IMU calibration #74

pzhu008 opened this issue Nov 8, 2019 · 8 comments

Comments

@pzhu008
Copy link

pzhu008 commented Nov 8, 2019

Hi,
Error occured when I use imu_utils to calibrate IMU. (no results for gyro)

I recorded a rosbag of IMU raw data for 90 mins. All gyro_x, gyro_y, gyro_z are zeros. Then I use ./record to generate a dataset. Also all gyro_x, gyro_y, gyro_z are zeros.

Do you have any idea about this?

Thanks,

imj

@niekez
Copy link

niekez commented Jan 17, 2020

It seems that there's is some filtering being done setting the gyro values to zero when there is little movement. This makes it impossible to measure the bias and bias random walk.

It would be more appropriate to send the raw data as the topic says.

I think the firmware had to be adjusted for this, could you please make this happen?

I'm experiencing some issues in maplab where the frame gets ignored because the gyro data is zero, also the gyro intrinsics can't be measured for callibration purposes.

@pzhu008
Copy link
Author

pzhu008 commented Jan 17, 2020

It seems that there's is some filtering being done setting the gyro values to zero when there is little movement. This makes it impossible to measure the bias and bias random walk.

It would be more appropriate to send the raw data as the topic says.

I think the firmware had to be adjusted for this, could you please make this happen?

I'm experiencing some issues in maplab where the frame gets ignored because the gyro data is zero, also the gyro intrinsics can't be measured for callibration purposes.

@pzhu008 pzhu008 closed this as completed Jan 17, 2020
@pzhu008 pzhu008 reopened this Jan 17, 2020
@pzhu008
Copy link
Author

pzhu008 commented Jan 17, 2020

try SDK 2.3.6 without filter

@niekez
Copy link

niekez commented Jan 20, 2020

try SDK 2.3.6 without filter

It's not possible to downgrade the firmware for 2.3.6. Also I'm using the S1030, and as far as I know there's no processing being done by the SDK. I think it's happening on a firmware level, but maybe someone can point me to the SDK code where filtering is done on the gyro.

@lesurp
Copy link

lesurp commented Aug 4, 2020

Hi, any update on this issue?
I'm using the example noise values given in the repository here but I would very much prefer calibrating my mynteye myself...

@lesurp
Copy link

lesurp commented Aug 6, 2020

Actually, this filtering is actively deteriorating the processing I am doing with the values. Is there any reason why the filters cannot be disabled on the s1030, while it can on the other devices? (https://slightech.github.io/MYNT-EYE-S-SDK-Guide/src/control/imu_low_pass_filter.html)

@KalmanXiong
Copy link
Collaborator

KalmanXiong commented Aug 6, 2020 via email

@LSXiang
Copy link

LSXiang commented Jan 28, 2021

This is a bug in SDK version 2.5, you can ref to #113

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

5 participants