Had it configured properly (I think)
Had enough sats
Was beyond minimum distance
Previously worked using 4.3 BF and 2.5 ELRS, now on BF 4.4 RC3 and ELRS 3.1.2
Any ideas?
#Failsafe didn't trigger GPS rescue
uncut willow
This was a manually initiated failsafe using a switch btw. I had tested it using GPS rescue switch which worked great multiple times. Only test of failsafe switch resulted in this.
uncut willow
Also the last screenshot shows what the receiver does when I cause an actual failsafe by turning off the transmitter
hasty plinth
-
GPS Rescue has been updated in 4.4 - there is some configuration needed: https://github.com/betaflight/betaflight/wiki/GPS-Rescue-for-4.4
-
Found a small bug with sanity check which is available in latest development build in failsafe handling (no control link, switch induced if there is a gps failure with OSD warning):
https://github.com/betaflight/betaflight/pull/12120
light tulip
Also the last screenshot shows what the receiver does when I cause an actual fai...
That at least confirms it's actually going to No Pulses when the throttle drops out of valid ranges
frosty nova
Would setting throttle to hold instead of auto in channel fallback settings prevent that from happening?
light tulip
No, that's the behavior you want, it's showing that the FC is seeing that the RC signals aren't real, and should be engaging in GPS RTH mode.
uncut willow
I've been out of town all weekend, will do some more testing tomorrow and follow up with y'all. Appreciate the responses.
uncut willow
Ok I am still having this issue. I just updated it to the release version of 4.4 and it has the same problem.
The GPS rescue trigger works fine
but when you manually trigger a failsafe it completely drops to the ground and then tries to throttle up and usually flips itself over
unfortunately I forgot to switch the setting on that records the OSD since I was using it for a livestream before, so no OSD data, but I had 15 satellites and was 80 meters away from it
frosty nova
but when you manually trigger a failsafe it completely drops to the ground and t...
In Failsafe Stage 1 settings, what do you have Throttle set to? Should be Hold, or set to a good hover value. If auto, it may cut motors during that brief phase of failsafe, if I recall.
frosty nova
I only see stage 2 settings
Channel fallback settings. Throttle set to auto will mean a brief cut in motors. Set to Hold, or known good hover value...
frosty nova
Ok so I'm confused
There are so many settings that play a role in GPS Rescue... If you haven't seen yet, here's a thorough Wiki covering it: https://betaflight.com/docs/wiki/archive/GPS-Rescue-v4-4#about-gps-rescue
hasty plinth
Also check this: https://github.com/betaflight/betaflight/pull/12120
hasty plinth
More explanation:
uncut willow
Ok thank you
uncut willow
Just wanted to mention that that fixed the problem (changing the dropdown to stage 2). I just tested it several times. I am a little confused what stage 1 means though since I don't see any settings for that. I'm not sure why the default setting would be a stage that doesn't exist, or why it would leave the drone armed if it was an invalid mode.
light tulip
That's the wall of channel states on the left side - it doesn't want to go into failsafe if a link drops a single frame, or is just sends one bad dataframe, so it'll wait just a little bit. Default is to drop, so that is a good way to try and hold default/previous in case the link returns quickly enough to not be a guaranteed crash