Skip to content

CI test build: crsf-gps-alt-msl (do not merge) - #3

Draft
raphaelhunziker1202-stack wants to merge 2 commits into
masterfrom
crsf-gps-alt-msl
Draft

CI test build: crsf-gps-alt-msl (do not merge)#3
raphaelhunziker1202-stack wants to merge 2 commits into
masterfrom
crsf-gps-alt-msl

Conversation

@raphaelhunziker1202-stack

Copy link
Copy Markdown
Owner

Draft PR only to trigger the CI firmware build on this fork for testing iNavFlight#11850. Do not merge.

…s_alt_source)

The altitude field of the CRSF GPS frame (0x02) so far carried INAV's
estimated altitude relative to the arming point, while the CRSF
specification intends this field to carry the GPS altitude (MSL), which
is also what Betaflight sends and what the GAlt sensor on EdgeTX/OpenTX
radios is expected to show.

Add a new setting `crsf_gps_alt_source`:

- ESTIMATED (default): estimated altitude above the arming point,
  identical to the previous behaviour
- MSL: raw GNSS altitude above mean sea level

The relative altitude remains available via the barometer/vario frame
(Alt sensor) regardless of this setting.

PG_TELEMETRY_CONFIG version bumped 8 -> 9.
The intermediate integer-centimeter step rounded negative estimated
altitudes differently than the previous float expression (by up to 1 m).
Use the original expression verbatim for the ESTIMATED path so the
default behaviour is unchanged, and drop raw from the MSL description
since gpsSol may carry the estimated fix when GPS fix estimation is
enabled.
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

  • maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

  • maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.


This is an automated suggestion to help route contributions to the appropriate branch.

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

RAM / Flash usage vs. base branch — commit 9eb30e9

No size baseline is available yet for this PR's base commit (no per-commit baseline has been published for it). This comment will show deltas once one exists — rebasing the PR refreshes its base commit.

Target Flash Δ RAM Δ
MATEKF405 624995 B (no baseline) 133256 B (no baseline)
MATEKF722 468367 B (no baseline) 123320 B (no baseline)
MATEKF765 645947 B (no baseline) 138768 B (no baseline)
MATEKH743 664215 B (no baseline) 139776 B (no baseline)

See RAM/flash optimization guide for techniques to reduce usage.

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

Successfully merging this pull request may close these issues.

1 participant