Betaflight GPS setup and GPS Rescue

These are the Betaflight GPS settings. The rescue numbers are on Failsafe, described in the next section.

Protocol. The GPS protocol the UART should speak. It has to match the module. Auto baud tries the usual rates.

Auto-configure u-blox. On boot, FlySpark's connected firmware sets the rate, the constellations and the messages. Leave it on for a u-blox module unless you configure that module yourself.

SBAS. The satellite-based correction source. Pick the one that covers where you fly.

Use Galileo. Adds Galileo satellites. INAV also has switches for BeiDou and GLONASS, and a minimum satellite count for a fix.

INAV dynamic model. The hint on the control says Air 2G suits most multirotors. The update rate is in hertz.

Coordinates. The fix is shown as coordinates you can copy. Until the GPS feature is on, the tab tells you to turn it on, save and reboot.

GPS Rescue is both a failsafe stage and a mode switch. The numbers live in one block titled for the rescue return. Altitude mode decides the target: the highest of the firmware's choices, a fixed altitude, or whatever height you are already at. Return altitude is metres. Extra climb is added on the way up, and the climb rate and ground speed are in metres per second.

Maximum pitch for the return is 30 to 60 degrees. Rescue will not start as a proper return inside the minimum distance from home, which is 10 to 30 metres. Descent begins at the distance you set, from 10 to 500 metres, and then uses its own descent rate. Minimum, hover and maximum throttle are the throttle limits during that descent, in microseconds.

Sanity checks can be off, on, or limited to failsafe. Minimum satellites is the count rescue itself requires, from 5 to 50. Allowing arming without a fix is off unless you enable it. The control's hint explains the consequence. FlySpark shows a rescue warning on that card when the firmware reports the feature is not in a usable state. Read that warning before treating rescue as a safety net.

INAV pilots looking for the same idea should use the INAV failsafe procedure, not this form. When that procedure is Land, the screen shows landing throttle and a motors-off delay. Near-home distance and climb behaviour are INAV settings on that failsafe card. Missions and geozones are planned on the mission planner.

Set a UART to GPS on the Ports tab at the module's baud, save, and reboot. The GPS tab then shows satellites. Indoor tests usually stay at zero satellites. HDOP is shown next to the count so a fix with many weak satellites is not mistaken for a good one.

The Betaflight configurator includes this tab with the rest of the setup. Position hold on Betaflight 2025.12 is a different, newer feature and is not configured by the GPS Rescue numbers on a 4.5 demo board.

Rescue throttle values are microseconds, the same unit as the radio endpoints on the Receiver tab. A hover throttle copied from a punch-out log is a starting point for the rescue hover field, not a promise that the descent will look like a manual landing. Try the return high and over open ground before you rely on it.