Hi, I updated my Arduplane from 3.9.3 to Arduplane 4.0.0 on an OmnibusF4 V3 board (without current sensor) equipped with Beitian BN-880 gps.
After the update I noticed from the GPA.Delta log that there are spikes (exactly every 20 seconds) of the update rate period of the GPS that go above 250 ms and they generate a “Bad GPS Signal Health” warning.
In Arduplane 3.9.3 I have random spikes of the update rate period but they do not go above 250 ms and they stays below 220 ms -> no “Bad GPS Signal Health” warning.
How can I solve this issue?
I tried several things like using a different GPS, increasing the update rate from 5 HZ to 10 Hz, using one/two constelations instead of three but I have the same issue.
As soon as I switch back to an Arduplane older than 3.9.6 (if I’m not wrong about the exact version…but something between 3.9.3 and 3.9.6) everything works ok without “Bad GPS Signal Health” warning or update rate period above 220 ms.
Attached some pictures of the GPS.Delta showing the behaviour in Arduplane 4.0 (spikes every 20 sec that go above 250 ms of update rate period) and 3.9.3.