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

Guidance Motion high drift #26

Open
AlexisTM opened this issue Nov 22, 2016 · 7 comments
Open

Guidance Motion high drift #26

AlexisTM opened this issue Nov 22, 2016 · 7 comments

Comments

@AlexisTM
Copy link

Hi,

The motion (position) output of the guidance system (after calibration & setting the position of the sensors) is heavily drifting. What should I do to reduce the drift ? Why does it drift that much ?

@tangketan
Copy link
Contributor

Did You use Guidance along with a DJI flight controller?
Also, the precision is heavily influenced by the environment. Good lighting, rich texture and regular motion should give You reasonably good result.

@AlexisTM
Copy link
Author

AlexisTM commented Dec 2, 2016

Dear,
It was with ROS, but we have an A3, not a M100. Therefore, it is no DJI Flight Controller connected to it.

@tangketan
Copy link
Contributor

Guidance has a poor onboard IMU. Try to connect Guidance with a DJI flight controller. A3 should also work.

@AlexisTM
Copy link
Author

AlexisTM commented Dec 2, 2016 via email

@AlexisTM
Copy link
Author

AlexisTM commented Dec 6, 2016

Will there be any chance to be able to send the quaternion to the Guidance System from a ROS node?

@dan748
Copy link

dan748 commented Mar 29, 2017

Hi @AlexisTM, were you able to solve the high drift problem, i am also facing this problem and can't seem to be able to fix it.

Also did you figure anything out about being able to send quaternion to the guidance from ROS?

@AlexisTM
Copy link
Author

AlexisTM commented Mar 29, 2017 via email

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

3 participants