| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Makes sense thanks!
Sorry, something went wrong.
There was a problem hiding this comment.
Nice, just a comment about the simplified checks
Sorry, something went wrong.
Co-authored-by: Mathieu Bresciani <brescianimathieu@gmail.com>
|
@ischollETH please run ./Tools/astyle/fix_code_style.sh src/modules/ekf2/EKF/aid_sources/gnss/gnss_checks.hpp to fix formatting |
Sorry, something went wrong.
Co-authored-by: Mathieu Bresciani <brescianimathieu@gmail.com>
to make unit tests work.
There was a problem hiding this comment.
I checked why the unit tests were failing and it was because the GPS fix type check was not enabled anymore for them because the default value for the bitmask in the constructor when it's not overridden by the parameter (like in the unit tests) was not updated.
I'm not sure why by default it was 21 but adding the 11th bit makes it 21 + 1024 = 1045 without changing anything else and that works. See 2b0102e
@bresch Can you give it a last check?
Sorry, something went wrong.
There was a problem hiding this comment.
All good, thanks!
Sorry, something went wrong.
…lot-Ian into gps-fix-type-check
|
@bresch I changed the parameter into an enum |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Solved Problem
When using a RTK GPS setup for precise start & landing scenarios I found that if the pilot takes off before there is a proper RTK fix, on return the home position was potentially imprecise and therefore an exact landing at the same spot can fail:
--> there is currently no way to enable a pre-flight check of the GPS fix type required before takeoff
Solution
Changelog Entry
Test coverage