[nav] update and harmonized navigation frequency #2796
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- use NAVIGATION_FREQUENCY for all firmwares - use 20 Hz as default, unless a PERIODIC_FREQ of 516 is used for rotorcraft (then keep 16) - remove old vehicle interface module - update some files The idea with 20Hz is to be closer to recent GPS modules providing positions at 10 to 20 Hz and to have a multiple of the common frequencies used in the system: 60, 100, 120, 500, 1000, ... Only execption is the legacy 512Hz where it is better to keep 16 to have a correct prescaler.
gautierhattenberger
force-pushed
the
nav_freq_harmonized
branch
from
0253d89
to
d6d1d64
Compare
Fabien-B
approved these changes
Nov 29, 2021
FlorianSan
pushed a commit
to enacuavlab/paparazzi
that referenced
this pull request
May 30, 2023
- use NAVIGATION_FREQUENCY for all firmwares - use 20 Hz as default, unless a PERIODIC_FREQ of 516 is used for rotorcraft (then keep 16) - remove old vehicle interface module - update some files The idea with 20Hz is to be closer to recent GPS modules providing positions at 10 to 20 Hz and to have a multiple of the common frequencies used in the system: 60, 100, 120, 500, 1000, ... Only execption is the legacy 512Hz where it is better to keep 16 to have a correct prescaler.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
rotorcraft (then keep 16)
The idea with 20Hz is to be closer to recent GPS modules providing
positions at 10 to 20 Hz and to have a multiple of the common
frequencies used in the system: 60, 100, 120, 500, 1000, ...
Only execption is the legacy 512Hz where it is better to keep 16 to have
a correct prescaler.