So I finally got this all hooked up and tested. ArduPilot checks for a location update every 20ms. So the GPA.Delta log shows that timing, and that is why it appears to be in 20ms intervals. These are on my test Solo sitting out on my deck using the brand new mRo M8N GPS. I had good reception and navigational use of all three systems.
The results confirm what I afraid of. I have not flown it to see if the results get event worse in flight, but they certainly may.
- With the typical configuration of 2 systems enabled (GPS & Glonass), the location updates come in on time with a new location every 20ms or less, where you see them at 0 to 220. There are no errors, and everything is happy.
- With the mRo configuration of 3 systems enabled (GPS, Glonass, & Galileo), location updates are consistently running late, and have quite a bit of jitter, where you see them spike up to 240. And there are numerous delayed updates in excess of the error threshold, where you see them spike up to 260.
- The mRo configuration will repeatedly trip "BAD GPS HEALTH" errors whenever it exceeds the error threshold (245) so every one of those spikes up to 260 is an error condition.
- The mRo configuration may result in poor navigation performance and EKF errors in flight. Jittery position updates being fed into a position controller is generally not a good thing. I'm going to show these results to the EKF engineers on the ArduPilot dev to see what they think about it's potential affects.
View attachment 7804