-
Notifications
You must be signed in to change notification settings - Fork 17.2k
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
Incorrect Altitude being reported in ADS-B Mavlink Msg's #5424
Comments
Hi Jeff, Here's the problem code: And The GPS alt unit is an easy fix, my bad! The pressure alt one is less obvious. I did not implement it because it wasn't clear what the data was. I can fix the GPS alt right away, would you be able to supply the description of the pressure sensor data? |
GPS alt is fixed via 372837b |
The pressureAltitude reported should be calculated using a standard reference pressure of 1013.25mbar. I've attached a little doc that describes the calculation which is already referenced to this reference. |
@jwuavionix I just noticed this is still lingering. Please assist on what the data is supposed to be, I want to make sure it's correct. per the mavlink packet note: Barometric pressure altitude relative to a standard atmosphere of 1013.2 mBar and NOT bar corrected altitude (m * 1E-3). (up +ve). If unknown set to INT32_MAX So is it feet above sea level? |
I left a comment on Dec 20th that attached an equation that is used to calculate the standard pressure altitude from the compensated(temp) baro pressure. This isn't AGL or MSL and should be calculated using the equation attached and just the baro pressure. |
is it OK if it is temperature compensated? |
yes, the equation needs to use temperature compensated baro pressure as the input. |
great! Then I think this ends up being easier than we thought. I was thinking into it too much. Thanks @jwuavionix ! |
See PR #5761 |
In mavlink 2's ADS-B send_dynamic_out msg, the GNSS Altitude is being reported in decimeters instead of the correct mm's.
Also, the pressure Altitude isn't implemented and is always being sent as invalid.
Arduplane V3.7.1 and Arducopter 3.4.3 on a pixhawk
The text was updated successfully, but these errors were encountered: