mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-11-22 14:19:57 +08:00
* feat(gnss): check that the position change matches the velocity A receiver computes its position from the code (time of flight) and its velocity from the Doppler shift. Multipath and other degradation hit the two differently, so a degraded receiver's position change stops matching its velocity, often before its reported accuracy shows it. The existing drift checks compare the two only at rest on the ground. The new strict check filters the position change rate minus the mean velocity over about 1 s and fails above GNSS_REQ_POSVEL, also in flight, so the selection prefers another receiver that passes. It is off by default (GNSS_CHECK bit 12) until the threshold is tuned on logs; the filtered value is logged in sensors_status_gnss either way. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com> * fix(gnss): skip the position step at a fix type change in the consistency check When a receiver starts or stops applying differential or RTK corrections, its position steps by up to a few meters in one epoch while the Doppler velocity is unaffected. That is a new solution, not degradation, and it shouldn't demote a receiver that just reached RTK fixed. On a 10 Hz log with DGPS dropping in and out, these steps drove the filtered value to 4.5 m/s; without them it peaks at 0.8 m/s, during a real vertical drift. Only the interval spanning the change is skipped and the filter keeps its state, so a receiver that keeps switching isn't blind for longer. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com> * refactor(gnss): Reduce check description * fix(GNSS): Make the feature enabled by default but with more margin * fix(gnss): restrict the position/velocity consistency check to horizontal Receivers that don't report the vertical velocity failed the check on any climb. Merge the consistency tests into fewer cases. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com> * refactor(gnss): mark the position/velocity consistency check as horizontal The check only compares the horizontal position change with the horizontal velocity. Name the parameter, flags and status field after that, so that a vertical counterpart can be added later as GNSS_REQ_VPOSVEL / CHECK_VPOSVEL. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com> * refactor(gnss): rename the position/velocity check to kinematic consistency HPOSVEL read like a check on position and velocity separately, next to HDRIFT and HSPEED. "Kinematic consistency" names the property being tested and leaves room for a vertical counterpart (VKIN). Messages, flag comments and the parameter's long description keep the plain wording, since "kinematic" alone can be read as RTK. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com> --------- Signed-off-by: Andrea Bernasconi <andrea.bernasconi@auterion.com>