-
Notifications
You must be signed in to change notification settings - Fork 68
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
minimu9-ahrs.1/COORDINATE SYSTEMS: missing note about circular direction #16
Comments
I am not sure what the problem is. It sounds like you are using the The "ORIENTATION AS EULER ANGLES" section of the man page explains what all the angles are, by walking you through a transformation from the ground coordinate system to the body (circuit board) coordinate system. The second rotation uses the pitch angle:
The two ideas of positive pitch and negative pitch don't have a clear mapping to the two phrases "clockwise" and "counter clockwise", so I am not sure what the issue is. The computation that comes up with the Euler angles is independent of the computation of the orientation itself, so definitely the definition of pitch should be the same no matter which sensors you are using to calculate the orientation. |
It is simple that I would like to see the rotation direction documented as e.g. clockwise/counterclockwise for the different options. |
Sorry, I don't get it. The first angle is pitch. On a plane, pitch describes how far your plane is from pointing at the horizon. Are you sure you are trying to talk about pitch? Maybe you actually want to talk about yaw, which is the second angle. Or perhaps the man page is wrong, and yaw is actually the first angle? |
Right, there seems to be a problem, too. I'm using minimu9-ahrs on an AltIMU-10 v3, the first value is yaw for me, as described under "--output FORMAT" |
I noticed that the first angle is inverted when using "gyro-only". Is that on purpose? Seems natural since clockwise is the natural direction of the compass while counter clock is L3G. Still confusing... Could you maybe drop a note in the "COORDINATE SYSTEMS"?
The text was updated successfully, but these errors were encountered: