MultiNav Pro+ GNSS 18Hz fix rate - anyone actually hitting that in practice?

Kenneth Hill•June 12, 2026

🔒 Security💡 Idea

Hey all, been working on a drone tracking project and picked up the MultiNav Pro+ GNSS module mainly because of that 18Hz fix rate. On paper it's insane for what I'm trying to do - I need position updates fast enough that I can feed them into a Kalman filter without the lag killing my heading estimates. First fix in 1 second is also huge for my use case since the drone arms and goes pretty quick.

💬 2 replies👍 0 likes👁 0 views

Replies

Adrian Yang•June 12, 2026

Yeah I've been hitting 16-18Hz pretty consistently outdoors with clear sky view, though I noticed it drops to around 12-14Hz if you're in a semi-urban area with partial obstruction - still totally workable for a Kalman filter pipeline tho. One thing worth knowing: make sure you're not bottlenecking on your UART baud rate if you're pulling full NMEA sentences at that rate, bumped mine to 460800 and the jitter basically disappeared.

Cody Murphy•June 12, 2026

Adrian nailed the baud rate thing - that trips up a lot of people and the default 115200 just can't keep up at 18Hz with full NMEA output. One other thing worth checking is whether you have all the unused NMEA sentences disabled (GLL, VTG, etc.) since even at high baud you're wasting bandwidth on stuff you probably don't need for a Kalman pipeline.