@John Wilson good question, and yeah this is worth nailing down before you commit to a power architecture.
The short answer is that automatic adaptive TX power control isn't something that happens transparently at the hardware level on the MultiNav Pro+ — the module doesn't have a closed-loop system that reads RSSI and backs off the amplifier on its own. What you *can* do is control TX power explicitly through firmware, so if your nodes are consistently at 50-200m you're leaving a lot of headroom on the table that you can absolutely trade for current draw. That's where the AI Firmware Builder in the Dev Hub is actually useful here — you can describe your deployment scenario and have it generate the power management logic rather than writing it from scratch.
For a short-range tracker build like yours, it's worth thinking about this at the application layer: poll RSSI after link establishment and step down TX power programmatically if you're consistently seeing strong signal, then ramp back up if the link degrades. It's not automatic but it's not hard either, and you get full control over the tradeoff curve rather than relying on something opaque in the hardware.
If you want to dig into the specific power registers and what current draw actually looks like at reduced TX levels, post back here — Moamen has shared some of that data before and it's worth having in the thread for anyone else doing battery-powered builds.
