Closed zejiekong closed 1 year ago
@zejiekong you can use the dedicated controller application for this sensor. Its documentation is still WIP but it has a comprehensive help message printed by -h
key. The covariance in the case of these sensors is the only noise variance detection experiment, so the procedure looks like the following:
--covariance
option:
rosrun witmotion_ros witmotionctl-wt901 --covariance
The existing defaults are obtained exactly in this way repeating the experiment from 3 to 7 tries, then averaging the measurements.
Thank you very much for the explanation !
What methods would you recommend to remove the noise and bias from the witmotion imu if it is possible?
@zejiekong the sensors have their own implementation of the Kalman filter (at least, Witmotion Ltd. declares it), so the attempts to eliminate the noise with some kind of smart filtering likely will provoke filter dissipation. I can recommend exchanging the measurement frequency for precision and making the accumulation register with loopback-based deviation calculation via the known existing noise covariance.
Hi, what do you mean by exchanging the measurement frequency for precision?
@zejiekong just using several subsequent measurements from the sensor to reformulate new IMU ROS message with refined values
Also, I see there is a CalculateAccelerationBias method in the wt901-uart.cpp file. Does that calculate the accelerometer bias stability? And what does the SetAccelerationBias method do?
@zejiekong they are convenience methods to set up the constant biases on the linear accelerometer via controller application. The functionality is partially described here, but the documentation is still WIP. These methods do not calculate stability biases or noise covariance.
Hi, how is the accelerometer, gyroscope ... covariance matrix obtained for the wt901 sensor? As shown in the wt901.yml config file. Thank you.