@James Blackburn good question — symmetric mobility is where a lot of BLE setups fall apart, and it's honestly one of the more interesting edge cases with this module.
The short answer is that the RF front-end itself doesn't do anything "active" in the sense of beam steering or adaptive power control per-hop, but what you do get is the receiver sensitivity headroom doing a lot of heavy lifting for you. When both ends are moving, you're constantly eating into your link budget as geometry shifts, but the MultiNav Pro+ is operating with enough sensitivity margin that the kind of fade events you'd normally see on a commodity module just don't trigger a drop — they look like a slight RSSI dip and recover. The external amplifiers on both TX and RX sides mean you're not starting from a thin margin to begin with.
The BLE stack on the STM32WB07 does handle connection parameter negotiation and has the standard adaptive frequency hopping baked in, so it's not completely passive — AFH will steer away from channels that are showing interference, which helps in cluttered RF environments where a moving vehicle might be sweeping through different noise floors. That's probably your most relevant "adaptive" behavior for the vehicle + handheld scenario.
If you want to dig deeper into the firmware side of this, the repo is public at github.com/RFOXiA/MultiNav-Pro-Long-Range-BLE-Module-Firmware-STM32WB07 — worth looking at how the connection intervals are configured, since tuning those for your specific motion profile can make a meaningful difference in perceived link stability.
