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

Baro Alt #18

Open
flybrianfly opened this issue Nov 9, 2022 · 0 comments
Open

Baro Alt #18

flybrianfly opened this issue Nov 9, 2022 · 0 comments

Comments

@flybrianfly
Copy link

It seems weird to me that barometric height (i.e. pressure altitude) is part of the navigation message. Typically the only data needed to compute and send barometric height would be the static pressure. I get that this is an estimated state, but so is indicated airspeed and true airspeed, which are grouped as separate messages in equipment/air_data.

I would argue that this is more important than just semantics. We have an air data computer CAN module, which has static and differential pressure transducers and an RTD front-end for an Outside Air Temperature (OAT) probe. I would expect our air data module to estimate and send the air data states (i.e. airspeeds and altitudes), but right now I have to either:

  1. Send static pressure and expect baro alt to be computed elsewhere
  2. Send the navigation message, which is huge, just to send the baro alt estimation

So, I propose that baro alt should be it's own message under equipment/air_data, just like the airspeed messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant