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

Using attitude from IMU to improve ROVIO tracking #248

Open
makiello opened this issue May 13, 2021 · 1 comment
Open

Using attitude from IMU to improve ROVIO tracking #248

makiello opened this issue May 13, 2021 · 1 comment

Comments

@makiello
Copy link

Hello,

Thanks for this great project!

I've been testing Rovio using my own system (Xsens Mti-300 and MT9V022 camera).

When walking down a corridor, turning fairly fast and returning to the original position, ROVIO seems to slightly underestimate the angle it has turned through at the end of the corridor. This results in an error in position of almost 2 metres, see first picture below.

Screenshot (365)

Rovio_corridor

The maximum value of angular rate on the z axis is only 1.5 rads/s so it is definitely not due to the gyroscope reaching its maximum value.
Taking the velocity from ROVIO and combining it with the attitude solution from the Xsens, I get a much smaller drift (see below).
Rovio_and_attitude

My question is: can I use the attitude from the Xsens in the prediction step of the filter?

I see that there is an ‘enableAttitude’ in the configuration file. If I set it to ‘true’ and publish pose messages containing the quaternion orientation from the Xsens to the /rovio/pose topic, will the filter take this into account?

@suyash023
Copy link

Hey @makiello Were you able to combine the attitude information from Xsens into ROVIO? I am going through a similar process but using a PX4 (Pixhawk). Would be glad if you could share some ideas! I would be happy to share mine too. Thanks!

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

2 participants