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

Preflight check fail Magnetometer compass reading inconsistent mRO Pixracer #14214

Open
sritank opened this issue Feb 23, 2020 · 7 comments
Open

Comments

@sritank
Copy link

sritank commented Feb 23, 2020

Hi,
I am using the mRO Pixracer board for my drone autopilot and the Taoglas sensor as my onboard GPS sensor. I calibrated my compasses based on the PX4 guide here .

The three onboard Magnetometers have parameter names:
MAG0 - Taoglas compass 1 = External Compass Orientation
MAG1 - Taoglas compass 2 = External Compass Orientation 1
MAG2 - Pixracer's compass = Autopilot Compass orientation

Currently the "heading" arrows on both the boards (Pixracer and Taoglas GPS) point forward, i.e. direction of flight. Hence the sensor orientation for the autopilot was set to "ROTATION_NONE". Affer successfully calibrating, the orientation for the other two compasses were also set to "ROTATION_NONE". However when I try to arm them, QGroundControl (QGC) gives an error that the compasses are inconsistent. So based on this post , I found that the Taoglas compasses are oriented 90 deg away from the heading arrow. Even after accounting for this and setting the calibration sensor orientation to YAW_90 and YAW_180, I still get the same error.

I disabled MAG0 compass and was using only MAG1(Taoglas) and MAG2(Pixracer). Upon doing this I get a different preflight failure,i.e. "Yaw estimate error".

Ultimately I disabled MAG0 and MAG2 sensor and am able to arm the drone using only the MAG1 sensor enabled.

Question: Must I account for something else while calibrating the sensors? And, how do I find out which sensor is the root cause of the above inconsistency?

@sritank
Copy link
Author

sritank commented Feb 28, 2020

Any help with the above would be appreciated

@julianoes
Copy link
Contributor

@dagar you mentioned something about this, right?

@stale
Copy link

stale bot commented May 31, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale label May 31, 2020
@julianoes
Copy link
Contributor

@dagar sounds familiar?

@stale stale bot removed the stale label Jun 2, 2020
@dagar
Copy link
Member

dagar commented Jun 2, 2020

@dagar sounds familiar?

Unfortunately. @sritank can you post a photo (or link) of the exact GPS/compass unit you're using?

A flight log from boot (SDLOG_MODE 1) or the output of listener sensor_mag would also help.

@sritank
Copy link
Author

sritank commented Jun 16, 2020

I thought of replying after getting the flight log that you had requested. However, I don't know when I'll be allowed to go back and get access to the hardware. The compass I'm using is below:

https://store.mrobotics.io/ProductDetails.asp?ProductCode=mro-gps003-mr

Hope it helps

@stale
Copy link

stale bot commented Sep 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale label Sep 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants