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

Ambiguous reference frame for accelerometer measurements in /msg/sensor_accel.msg #16328

Closed
rblilja opened this issue Dec 3, 2020 · 5 comments
Assignees
Labels
Documentation 📑 Anything improving the documentation of the code / ecosystem

Comments

@rblilja
Copy link
Contributor

rblilja commented Dec 3, 2020

Files:

/msg/sensor_accel.msg
/msg/sensor_accel_fifo.msg

Description:

The comments of the x, y, z variables makes little sense in terms of the frame of reference, e.g. for the x axis: "# acceleration in the NED X board axis in m/s^2"

  1. Unclear if NED refers to the actual navigation frame. Then mentioning of "board" makes no sense.
  2. If NED is incorrect. Unclear if "board" refers to the sensor frame or body frame of a circuit board?
@LorenzMeier
Copy link
Member

The sensor measurements get transformed into the board's NED frame and so the description is correct and accurate.

@rblilja
Copy link
Contributor Author

rblilja commented Dec 3, 2020

To me it makes little sense that the board can have a NED frame. Possibly a NED frame attached in e.g. the COG of the board. What I'm getting at is that it shall simply be the NED frame (which in literature often is called the navigation frame).

Looking in https://dev.px4.io/v1.11/en/contribute/notation.html, it mentions FRD and NED. So cleaner to just refer to those?

It makes me wonder. It is actually not the FRD frame the accelerations are transformed to? Then I understand your argument.

@bresch
Copy link
Member

bresch commented Dec 4, 2020

It makes me wonder. It is actually not the FRD frame the accelerations are transformed to?

@rblilja Yes, it's FRD. Could you please make a PR to fix that please?

@bresch bresch added the Documentation 📑 Anything improving the documentation of the code / ecosystem label Dec 4, 2020
@rblilja
Copy link
Contributor Author

rblilja commented Dec 4, 2020

@bresch Sure. No problem. Thanks for ironing this one out!

@rblilja
Copy link
Contributor Author

rblilja commented Dec 6, 2020

@bresch Made a PR. It is my first time contributing - so please correct me if I did any mistakes. Not sure how I link a PR with an issue, but the system seems to have picked it up above :)

Alos note that I have found other messages files that needs to be looked at. Please see the description of the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation 📑 Anything improving the documentation of the code / ecosystem
Projects
None yet
Development

No branches or pull requests

3 participants