Thanks for watching!! I appreciate you!! Great question… the channel fallback settings on the left are what are applied during a Stage 1 failsafe. Without going into too much detail as to the “why”, just make sure to set your failsafe action as “Stage 2 / Gps Rescue” not Stage 1. When set to Stage 2, the fallback settings are irrelevant / not applicable.
Always always always set ground assistance type based on your region if your gps unit supports SBAS (almost all do) SBAS augments the gps signal using ground stations scattered around your region, in North America it’s called WAAS - this greatly improves navigation precision both horizontally and vertically, and for many gps recievers it takes you from feet of precision to inches, or even less than an inch Not that beta flight is going to fly it to that precision, but getting the best data can’t hurt
I use the Avatar system now with canvas mode, so just like wtfos.. The only difference is that you can select from all the elements to display on screen, instead of the limited set that came over the original dji osd.
So what do you do when your home arrow does not point back home? Disable the magnometer, calibrade your gyro in betaflight (including axis reset) and reload the fonts. What else am I missing? My home arrow does not point back to the take off possition, even after flying strainght out to 400m...
If your home arrow is not pointing to the correct home direction, you don’t have a good gps fix on home location.… You should disable the magnetometer to start. Ensure that you have a good gps fix before arming and taking off 6+ sats, the more the better. If you have done all the above and it’s still pointing in the wrong direction, the gps unit could be faulty. The gyro, accelerometer, and fonts have nothing to do with this, it’s home position / 3D fix.
@@Rogue_FPV thx for the quick response. I'll disable the manometer and see if that fixes things. I have 2x hglrc m80 pro gps units and I'm seeing the same thing with both. I always wait for 8x sats before taking off. On my second battery I usually start off with 12-15 sats. The home distance is very accurate though which I find strange since the arrow isn't pointing home all the time...
This is an awesome question, and a very observant one at that! In my particular case "AUX 4" is the switch I use for GPS Rescue in the Modes Tab. The switch you use may be a different AUX #. The Failsafe Channel Fallback setting for my "AUX 4 " basically says "If there is a Failsafe, SET AUX 4 to PWM value of 1950" or " The GPS Rescue Mode Switch is SET to High/On position”
@@Rogue_FPV Thanks for the response. I figured that was the case but was surprised there is no "gps rescue" in dark grey next to aux4 on your screen. Is this setting required for gps failsafe to perform? I thought I read that Channel Failback Settings only come into play for stage1. Curious to get your thoughts on this.
@@bleugt your right, on my Aux 4, is should also say GPS Rescue. I don’t know why it doesn’t show there, but most of my other switch modes are listed there.. strange…. Note - I didn’t set any of the channel fallbacks, these got set when I setup gps rescue as my failsafe option. I could be wrong, but I think the channel fallback settings are used for stage 1 and 2. I was always of the understanding that the channel fallbacks were “what the switches fall back to, if a failsafe occurs.”
@@Rogue_FPV fantastic I’ve just been testing it on default settings and I have to say it’s cool that it can land close to the home point But I much prefer BF4.3 GPS Rescue flight characteristics BF4.4 bobbs up and down like it’s trying to hold speed also it keeps flying forward then goes up slowly then turns BF4.3 used to WIP round really quick and start flying back whilst increasing altitude I’m flying a Chimera 7” BF4.4 put me in a tree while testing at low altitude 100m from home point 🙄
Great Question! "Stage 1 Failsafe is activated when the receiver reports failsafe to the flight controller. If the failsafe lasts longer than the time you’ve specified in Betaflight, it will go into Stage 2. This is set to a second by default (guard time). Note that you can also activate Stage 2 Failsafe directly using a switch (setup in modes tab). If the failsafe you are experiencing is just a temporary signal dropout, Stage 1 might give you a chance to regain control and recover without crashing" - Oscar Liang
Very nice - FYI: Betaflight does use the magnetometer if it's available *by default*. That being said, I'd agree that if it's something you're wanting to leverage, go with iNav and disable it for BF or at least tell GPS rescue not to use it unless you really know what you're doing on the compass front. AFAIK: Auto baud on the ports tab and Auto Baud on the GPS tab aren't really related. I don't generally recommend the GPS auto baud though. GPS rescue really needs at least 57600 to work properly (AFAIK). bf 4.3 for current altitude will allow you to set an added buffer via cli, so you can always add, say 50m or 100m to whatever your current altitude is once failsafes trigger.
Auto Baud on the ports and GPS tab are related, you can set both to auto, or set your speeds accordingly in each. It's not "GPS Rescue" that needs at least 57600, this speed is entirely dependent on the max buad speed of each gps device. All GPS Rescue needs is Min Sats and a gps fix at takeoff. I recommend that experienced users always use the max speed their device is capable of. I have had a few GPS units in the past that didn't respond to betaflight with the highest baud speed, so I don't recommend novice users to just "Set it to the max", in case they get no response from the unit. The best thing is to check the manufacturer's spec, or set it to the highest speed that works and gets responses from the gps.
@@Rogue_FPV So, we may just be splitting hairs here. The gist of things is probably to advise people use 57600 all the time if you're using auto-config. Use or don't use auto-baud (probably just don't use it), but it's not related to the ports tab (it's a different Hail Mary strategy for communicating with the GPS in order to issue the command to change the baud rate to whatever you set in the ports tab). If you notice, you can't actually set AUTO in the ports tab anyways. AUTO is the same as 57600, the BF Configurator will switch it out for you when you save and come back. That's just fixed code behind the scenes. It is however, a problem for the user to misinterpret this video and look up the spec of their GPS unit that often says "Baud: 9600" and set the baud to that. Because, while you're technically right that GPS Rescue doesn't care about the baud, 9600 is not a sufficient rate to communicate the GPS data once update rate is updated to 5hz, which it is when you have auto-config on and often the default 1hz update rate is too slow for gps rescue if you had autoconfig off. This is part of the reason GPS on a soft serial for GPS rescue doesn't work well / isn't advised. Even though the update rate is pretty slow, the baud rate that's reliable on soft serial just isn't sufficient to communicate the data fully. There's no real reason to use more than 57600 when allowing BF to setup the GPS unit - just as you said, GPS Rescue doesn't care... and 57600 is sufficient, but nothing really stopping you from using 115k either. The story might be different if you're not using auto-config, but this explanation is already a little long.
@@Rogue_FPV thanks for your patience, lol. it really is a great video .... sorry about diving into the minutia that probably makes a difference to like 14 people :) or is it 0...
Very informative video. I just have a doubt about the barometer and Betaflight 4.3… There’s a a couple of new features to improve altitude estimation with baro and gps. I use the Tbs m8.2 gps and gets satellites very quickly and wait until I have 6 satellites before arming. I was wondering what would be the right number of sats to start using both gps and baro (position_alt_gps_min_sats)? And also the right number of sats to stop using gps and switch back to baro (position _alt_baro_fallback_sats)? Thanks 👍🏼
6 sats is the very bare minimum of sats needed to acquire a home position lock with betaflight. Personally I use 8 sats min for much better position accuracy. Weather you have a gps or not, you can use the baro for better alt readings, just cover the baro with some foam. For alt_baro_fallback_sats / your min sats -2
Absolutely superb! I’m a newcomer to Betaflight so this has been invaluable in helping me set up my quad. Many thanks for your time and effort.
My pleasure! Thanks for watching!
Thank you for this video! may I ask if its mandatory to set something one the Channel fallbacksettings on the left? Thank you!
Thanks for watching!! I appreciate you!!
Great question… the channel fallback settings on the left are what are applied during a Stage 1 failsafe. Without going into too much detail as to the “why”, just make sure to set your failsafe action as “Stage 2 / Gps Rescue” not Stage 1.
When set to Stage 2, the fallback settings are irrelevant / not applicable.
Always always always set ground assistance type based on your region if your gps unit supports SBAS (almost all do)
SBAS augments the gps signal using ground stations scattered around your region, in North America it’s called WAAS - this greatly improves navigation precision both horizontally and vertically, and for many gps recievers it takes you from feet of precision to inches, or even less than an inch
Not that beta flight is going to fly it to that precision, but getting the best data can’t hurt
This is a great tip, and for Inav it probably matters more. 💪🏻💪🏻
@@Rogue_FPV yeah that’s true. Autoland features it’d be essential unless there’s lots of augmenting with other data sources
Just wondering if you have done the wtfos mod and if so maybe a new video with canvas mode? This one is great BTW thanks
I use the Avatar system now with canvas mode, so just like wtfos.. The only difference is that you can select from all the elements to display on screen, instead of the limited set that came over the original dji osd.
So what do you do when your home arrow does not point back home? Disable the magnometer, calibrade your gyro in betaflight (including axis reset) and reload the fonts. What else am I missing? My home arrow does not point back to the take off possition, even after flying strainght out to 400m...
If your home arrow is not pointing to the correct home direction, you don’t have a good gps fix on home location.…
You should disable the magnetometer to start. Ensure that you have a good gps fix before arming and taking off 6+ sats, the more the better.
If you have done all the above and it’s still pointing in the wrong direction, the gps unit could be faulty.
The gyro, accelerometer, and fonts have nothing to do with this, it’s home position / 3D fix.
@@Rogue_FPV thx for the quick response. I'll disable the manometer and see if that fixes things. I have 2x hglrc m80 pro gps units and I'm seeing the same thing with both. I always wait for 8x sats before taking off. On my second battery I usually start off with 12-15 sats. The home distance is very accurate though which I find strange since the arrow isn't pointing home all the time...
very nicely explained and shown, thank you
Thank you for the kindness!
This video is amazing. So complete and concise. I’ll be using this to set up my 4” and 7” quad. Thanks again rogue!!! 💯🙏🏽
Thanks for Watching! I;m glad it was helpful!
Great vid! Can I ask for a quick explanation of the Aux4 "set" config under the Channel Failback Settings?
This is an awesome question, and a very observant one at that! In my particular case "AUX 4" is the switch I use for GPS Rescue in the Modes Tab. The switch you use may be a different AUX #. The Failsafe Channel Fallback setting for my "AUX 4 " basically says "If there is a Failsafe, SET AUX 4 to PWM value of 1950" or " The GPS Rescue Mode Switch is SET to High/On position”
@@Rogue_FPV Thanks for the response. I figured that was the case but was surprised there is no "gps rescue" in dark grey next to aux4 on your screen. Is this setting required for gps failsafe to perform? I thought I read that Channel Failback Settings only come into play for stage1. Curious to get your thoughts on this.
@@bleugt your right, on my Aux 4, is should also say GPS Rescue. I don’t know why it doesn’t show there, but most of my other switch modes are listed there.. strange….
Note - I didn’t set any of the channel fallbacks, these got set when I setup gps rescue as my failsafe option. I could be wrong, but I think the channel fallback settings are used for stage 1 and 2. I was always of the understanding that the channel fallbacks were “what the switches fall back to, if a failsafe occurs.”
Excellent
Thanks!!! 🙌🏻🙌🏻🙌🏻
thanks that was really useful hoping you will do a review of settings in the new BF4.4 GPS rescue 🙂
I’ll be testing the new landing feature this weekend, if all is good I’ll make a video on that shortly.
@@Rogue_FPV fantastic I’ve just been testing it on default settings and I have to say it’s cool that it can land close to the home point
But I much prefer BF4.3 GPS Rescue flight characteristics BF4.4 bobbs up and down like it’s trying to hold speed also it keeps flying forward then goes up slowly then turns BF4.3 used to WIP round really quick and start flying back whilst increasing altitude
I’m flying a Chimera 7” BF4.4 put me in a tree while testing at low altitude 100m from home point 🙄
@@flipfpv4539 @rcaddict has a good video where he talks about adjusting the rth p settings for a smoother return flight.
@@Rogue_FPV thanks for that I’ll check it out 😊👍
Awesome thanks!!!
@cheese_fpv Thanks for watching! 🙌🏻🙌🏻
Hi, great video ! What is the difference between failsafe switch stage 1 and 2?
Great Question!
"Stage 1 Failsafe is activated when the receiver reports failsafe to the flight controller.
If the failsafe lasts longer than the time you’ve specified in Betaflight, it will go into Stage 2. This is set to a second by default (guard time). Note that you can also activate Stage 2 Failsafe directly using a switch (setup in modes tab).
If the failsafe you are experiencing is just a temporary signal dropout, Stage 1 might give you a chance to regain control and recover without crashing"
- Oscar Liang
@@Rogue_FPV Thanks !
Very nice - FYI: Betaflight does use the magnetometer if it's available *by default*. That being said, I'd agree that if it's something you're wanting to leverage, go with iNav and disable it for BF or at least tell GPS rescue not to use it unless you really know what you're doing on the compass front.
AFAIK: Auto baud on the ports tab and Auto Baud on the GPS tab aren't really related. I don't generally recommend the GPS auto baud though. GPS rescue really needs at least 57600 to work properly (AFAIK).
bf 4.3 for current altitude will allow you to set an added buffer via cli, so you can always add, say 50m or 100m to whatever your current altitude is once failsafes trigger.
Auto Baud on the ports and GPS tab are related, you can set both to auto, or set your speeds accordingly in each.
It's not "GPS Rescue" that needs at least 57600, this speed is entirely dependent on the max buad speed of each gps device. All GPS Rescue needs is Min Sats and a gps fix at takeoff. I recommend that experienced users always use the max speed their device is capable of. I have had a few GPS units in the past that didn't respond to betaflight with the highest baud speed, so I don't recommend novice users to just "Set it to the max", in case they get no response from the unit. The best thing is to check the manufacturer's spec, or set it to the highest speed that works and gets responses from the gps.
@@Rogue_FPV So, we may just be splitting hairs here. The gist of things is probably to advise people use 57600 all the time if you're using auto-config. Use or don't use auto-baud (probably just don't use it), but it's not related to the ports tab (it's a different Hail Mary strategy for communicating with the GPS in order to issue the command to change the baud rate to whatever you set in the ports tab). If you notice, you can't actually set AUTO in the ports tab anyways. AUTO is the same as 57600, the BF Configurator will switch it out for you when you save and come back. That's just fixed code behind the scenes. It is however, a problem for the user to misinterpret this video and look up the spec of their GPS unit that often says "Baud: 9600" and set the baud to that. Because, while you're technically right that GPS Rescue doesn't care about the baud, 9600 is not a sufficient rate to communicate the GPS data once update rate is updated to 5hz, which it is when you have auto-config on and often the default 1hz update rate is too slow for gps rescue if you had autoconfig off. This is part of the reason GPS on a soft serial for GPS rescue doesn't work well / isn't advised. Even though the update rate is pretty slow, the baud rate that's reliable on soft serial just isn't sufficient to communicate the data fully. There's no real reason to use more than 57600 when allowing BF to setup the GPS unit - just as you said, GPS Rescue doesn't care... and 57600 is sufficient, but nothing really stopping you from using 115k either. The story might be different if you're not using auto-config, but this explanation is already a little long.
@@CesiumSalami 💯 yes! 👆🏻This is the best most complete explanation 🙌🏻
@@Rogue_FPV thanks for your patience, lol. it really is a great video .... sorry about diving into the minutia that probably makes a difference to like 14 people :) or is it 0...
Subscribed
Thank You!!!
Very informative video. I just have a doubt about the barometer and Betaflight 4.3… There’s a a couple of new features to improve altitude estimation with baro and gps. I use the Tbs m8.2 gps and gets satellites very quickly and wait until I have 6 satellites before arming. I was wondering what would be the right number of sats to start using both gps and baro (position_alt_gps_min_sats)? And also the right number of sats to stop using gps and switch back to baro (position _alt_baro_fallback_sats)? Thanks 👍🏼
6 sats is the very bare minimum of sats needed to acquire a home position lock with betaflight. Personally I use 8 sats min for much better position accuracy.
Weather you have a gps or not, you can use the baro for better alt readings, just cover the baro with some foam.
For alt_baro_fallback_sats / your min sats -2
"Yeet the quad straight up in the air," I appreciate the use of highly technical jargon in your voice over. 😄😄 This is a great breakdown!
Thanks buddy!!! 🤣
Great vid, thank you!! 🙏👍🤘
Thanks @damianoAir 🙌🏻🙌🏻🙌🏻
Really great tutorial. Thanks for sharing. 💜
Thank you for watching, and the kind words 🙌🏻😁