-
Notifications
You must be signed in to change notification settings - Fork 327
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
GPS Model is not aligned wth North direction. #2061
Comments
@RomanLut any chance you can fix the generic gps model for 7.1.1? I see you have a PR to add specific models for many of the common gps units in 8.0. :) |
For some reasno I pasted 2 of the same images. But the axis represent the result of the gps model with the arrow pointing to the same orientation. Isn't the X axis of the Magnetometer the North direction, according to the sensor? That is the source of my confusion. |
I updated the model on the original entry. The arrow should point to the reference North direction (X or the magnetometer) axis on the gps model. |
Ok, the confusion seems to be the assumption that arrow on Magnetometer model points to the North. Actually Magnethometer model in the tool represents Matek magnetometers (M8Q, M9N, M10Q) as most widely used models. Arrow on Matek magnetometers points to the negative Y axis (East). |
I guess this is the issue. This makes no sense (other than historical reasons). There is also plenty of gps units with no arrows, or different axis orientations, as you probably found out when modeling a bunch of them. The 270 in CW270flip is the offset of the X axis from the axis tat points to the front of the quad. |
These pictures were taken in the alignment tool, with the gps in the same orientation (CW 270 FLIP) If the Arrow on the GPS is supposed to point North, it does not match the axis view (X axis is yellow and is supposed to point North.
North Arrow pointing to the back of the quad:
X Axis pointing to left side of the quad:
This is probably one of the sources of confusion in the alignment tool.
The text was updated successfully, but these errors were encountered: