-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
EKF2: Spoofing GPS check #23366
EKF2: Spoofing GPS check #23366
Conversation
src/modules/commander/HealthAndArmingChecks/checks/estimatorCheck.cpp
Outdated
Show resolved
Hide resolved
Here is a log with an example with false positive spoofing. We probably want spoofing state to be >=2 for a period of time before failing the check. https://review.px4.io/plot_app?log=8e03bae1-1551-4c93-bf6b-19c22e3c78a1 |
…to completely stop fusion
I now changed it to: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would really want to completely switch from GPS to GNSS at some point...
src/modules/commander/HealthAndArmingChecks/checks/estimatorCheck.cpp
Outdated
Show resolved
Hide resolved
src/modules/commander/HealthAndArmingChecks/checks/estimatorCheck.cpp
Outdated
Show resolved
Hide resolved
src/modules/commander/HealthAndArmingChecks/checks/estimatorCheck.cpp
Outdated
Show resolved
Hide resolved
src/modules/commander/HealthAndArmingChecks/checks/estimatorCheck.cpp
Outdated
Show resolved
Hide resolved
7ae41a4
to
30211ab
Compare
@haumarco @bresch Looks like the CI for synching the px4_msgs repo failed on the deploy here. They are now out of synch, causing issues if you use the px4_ros2_interface_lib. Would you mind rerunning the action synching the msgs? |
* estimator gps check fail flag for spoofing * warn whenever spoofing state changes to true, use default hysteresis to completely stop fusion * dont introduce more GPS namings, GNSS instead * flash: exclude mantis for cuav_x7pro
Solved Problem
Currently the spoofing state, which gets set by the GPS driver, does not have any effect on the estimator.
Solution
One can now add the spoofing state to the EKF2_GPS_CHECK. For it to fail, the spoofing flag has to be consistently true over a second and vice-versa for it to pass again.
There is now also a event which gets sent once when the first spoofed message arrives. This will notify the user, independent of the settings chosen in EKF2_GPS_CHECK.