Been running the MultiNav Pro+ GNSS module for a few weeks now on a UAV tracking build and overall pretty impressed with the fix times and accuracy out in open terrain. My question is around multi-constellation behavior - I know the module pulls from GPS, GLONASS, Galileo etc., but does anyone know if there's any way to configure which constellations get prioritized or weighted when the receiver is computing a position solution? Or is it just doing a straight best-available fix from whatever birds are visible at the time?
The reason I'm asking is I'm getting some occasional position jumps that I suspect might be related to the receiver switching dominance between constellations during transitions, like going from a clear sky zone into a partially obstructed area. The 1.5m accuracy spec is obviously under ideal conditions, but I'm wondering if those jumps are just expected behavior or if there's something I can tune to stabilize it. Haven't been able to find anything in the docs about constellation weighting specifically, might just be buried somewhere I haven't looked.
Also curious whether the 18Hz fix rate is consistent across all constellations or if the receiver drops to a lower rate internally when it's actively switching or reacquiring. Would be really useful to understand whats happening under the hood there before I commit to the sensor fusion logic I'm building on top of it. If anyone's dug into the NMEA or proprietary output from this thing at a low level, I'd love to know what you found.
