BetaFlight 4.4 GPS Rescue Auto Land📡 is AWESOME with Flywoo Explorer LR HD V2 // No Compass Needed! 

Superb, I will test on weekend. I Think you are the only one providing a cli for LR4 v2 for BF4.4(.1). Flywoo has no interest in updating theire Supportseite. Thank you, I will give feedback.

@@thekanal6774 Thank you! Please keep in mind that I have configured RPM filtering in the above config/tune, and I flashed the ESCs with esc-configurator.com to 48khz. If you don't want to use that, you can just disable the bi-directional dshot setting. I still don't think my setup is the best, but it's a work in progress, because as you said -- flywoo has given up on the V1/V2 model.

@@JohnCuppi thanks a lot for you sharing! could you continous to give us cli tuning improvement when you will have better setting.

Can you share your gps settings please? I can't get my drone to arm unless i turn of the sat lock for take off

Thanks for checking it out! 😊

Glad you enjoyed it!

Ain't like a DJI Mavic but it's more like a very early hubsan zino now 🤣

😉 well, even before this it could return to the general area but that does require not accidentally disarming it 😂

I see your wearing old goggles lol, I find that they fit better as well’

Glad it was helpful! I’m also waiting for the final release before flying it anywhere I can’t retrieve it readily - just in case there’s any major problems with the RC5.

👏 😎

Hey, Tim!! Thanks! Dude I'm subscribed but I haven't gotten any of your video upload notifications. Hope you're doing well.

Awesome Johnny! Mine is all 100% stock and what a difference from 4.1. Also, that V2.0 GPS is NMEA on the label, and configured as such in 4.1. But, it is also capable of uBlox protocol @ 10hz -- perfect and recommended for GPS Rescue self landing. Switching to uBlox, I'm now hitting almost 18 satellites, when before it was just around 13 max. 😮

Yeah! Super happy with the work the betaflight devs have done for all of us on this. 😎

Yeah, Dave_C's Explorer design that it was built off of, is a great one!

Thank you 🤗

Hope you enjoy it!

I had no clue how slow NMEA protocol was by default. So much than than UBLOX default of 5Hz, and mine can apparently do 10Hz so now it's rockin' -- thanks for watching! This quad has no compass at all so it has to rely on the GPS data to get its heading in order to complete this self landing. Remarkable how far we've come.

@@JohnCuppi yeah I saw how you tried to confuse it and still found its way back home. I think a bad compass or bad compass offsets can cause way more confusion to a drone than having no compass at all!

@@RDsRCReviews you are 100% correct, and it is why most fpv quad builders just avoid a compass. it is just not practical for these open-frame builds. They are so hard to keep calibrated, and keep clear of interference. The fact that betaflight 4.4 can gps rescue home AND auto land very close to its take off area is even less of an incentive to bother with a compass.

It is! Love the work the devs have done on this.

Hey thanks for commenting and watching!

@@Benanaslol I was thinking of making a dedicated video exploring that but only after I become more knowledgable about it. The only thing I did in u-center was increase baud rate to 115200, because without doing it there, BF was only negotiating 57600 baud rate. I wanted the fastest communication rate so I modified it there. I have seen others get a successful result at 57600, so maybe it's not necessary. Other than that, I didn't change anything else. It did allow me to verify what it was running at as well, since it was an NMEA GPS but supported ubx, I wasn't totally sure if it was running at 10khz update rate.

@@Benanaslol man that’s great to hear! Thanks for letting me know you had a similar experience.

Nope it’s not unique to the flywoo, but so many people have this specific drone, I felt like making a video about my results with it. 😎👍 thanks Ron.

thanks! yeah it is!

Wonderful thoughtful comment. Thanks so much!

👍👍

Yeah. This was definitely a bit of reading and looking into, to make sure I wasn't going to cause my quad to crash and go splat in the ground. Got the first couple successful landings on Monday, and did the video today. The most important thing is to really know your GPS first. I looked up my GPS hardware specs here: www.getfpv.com/flywoo-gm8-mini-v1-0-gps-module.html and from there I had two important things: #1 Concurrent GNSS : 1Hz-10Hz. 👍Great, because 10Hz update rate is recommended. And #2, it supports uBlox protocol. Mine said NMEA-0183 I wasn't sure, but I was lucky that it supported UBX.

When you gonna become PotatoFPV already!?

Search for WTFOSD for DJI, it’s a hack for the DJI FPV system. 👍

Thanks 👍 it's a ton of fun! I still recommend the flywoo explorer lr.

Great question thanks! Betaflight does not need a compass / magnetometer and it is better to not enable it, since mounting one without interference is really difficult. Mine doesn’t have one at all. The option will be right below the Barometer setting to make sure mag/compass is turned off. (See 4:15 in the vid)

Hi, thanks so much for the feedback! #1) When you say HD OSD are we talking about the "WTF OSD" as I am using here in this video? The default DJI OSD has never given me this problem, but I only ever used BF 4.1 with mine. I never migrated it to 4.2 or even 4.3, so if something was going on there then I missed all of that entirely (sounds like I made a good call not updating until now then). However, now that you bring this issue up, the HD WTF OSD though that I'm showing off in this video has had the glyphs or images glitch before for me, but NOT on my Flywoo Explorer yet. I've had that problem on my iNav 5.1 based airplane. And it only happens in one instance -- where video link is lost and regained. The fix has just been the OSD on/off mode option in the modes tab, if the glyphs/images get out of wack, then all I have to do is toggle it and that resets it and fixes them on my plane. That should work the same way for the flywoo. Since I only just started flying the explorer v2 again, and haven't had my signal cut yet, that's prob why I haven't seen this, but thanks for the reminder for me to go ahead and add that on/off OSD setting on a switch :D And I can give you my HD OSD settings on the vista that have been working well for me on my iNav plane, because I intend to put them on my flywoo explorer lr v2 now. #2) It takes a few minutes to get the first satellite lock of the day (3 min max), you can technically get a 3D fix with just 5 satellites but I like to wait until 8. Every flight does not require waiting this long, only the FIRST flight of the afternoon or so. This GPS has temporary cache memory for ephemeris data. It remembers the general position of the satellites and can find them faster on the next flight, because the sats will not have moved that fast especially if you next flight is within the hour. So, what I do is turn down power on the vista to 25mw, that helps it acquire those first set of sats a little faster, then crank it back up once it's done. Once it gets over the hump of getting the first 6-8 sats then the number grows much quicker, even after the putting the vista back at full power level. I only ever recall having a max of around 12 or 13 satellites on this quad with the GPS in NMEA mode on betaflight 4.1 with the very slow baud rate of 9600bps and 1hz update rate. With the increased baud rate speed and GPS in Ublox mode @ 10hz, I'm now getting 18+ sats... I was able to reproduce this same result again on a different day after making this video, it wasn't a fluke, so I'm really happy about this! I cannot honestly complain much about the flywoo 2.0 GPS other than the initial wait for sats. Since that GPS has some ephemeris data cached in memory once it finds the first satellites, the next flight(s) are always fast and lock in very quickly after that first one of the day because of this. 👍 However you will find this experience will vary widely based on which version of the flywoo they received, AND if the GPS wire is shielded. Mine is, and that is the big KEY. There is a little copper shield on the twisted wires. I think I showed this off in my review, you can see a copper wrap all around the GPS wires. Again this is CRITICAL to getting and sustaining a lock at all in any reasonable timeframe. My understanding is that Flywoo starting from the point of V2 when I did my review was shipping them with the wires copper shielded. V1 and some earlier V2 were hot garbage setups without it for the digital version. But in the worst case scenario, if you find they didn't shield it at the factory because they were lazy, a roll of copper tape should do the trick. I have a roll of it and use it to shield GPS wires when I need to, it really work. Hope this helps for you to maybe decide on getting one of these or not. I still think this is a wonderful little build and I'd probably buy another one if mine were to die or become lost, even 2 years later.

​@@JohnCuppi Thanks for the long and detailed reply! Wow! Cheers, Bill

Throttle at mid or just slightly above that is the best place to put it once you are in GPS Rescue Mode -- if it isn't already around mid throttle already when you trigger RTH. Definitely not dropped all the way down OR throttle all the way up, either! When you take back control, you want it to hand it off back to you gently. Happy flying! By the way, I decided to update my ESC firmware to 48khz and enable RPM filtering on the Flywoo, so I'll be experimenting with that. I figured I might as well do RPM filtering since I'm trying to re-tune it more perfectly anyway, and see how it all goes. Too windy today to fly today unfortunately, but things are starting to look up temperature wise. One thing I did not discuss in this video, which I am sure you you probably read or saw already but just in case you didn't, are the gps rescue "Channel Fallback settings." I directly copied these and kept them the same as 4.1, but they MUST be configured for GPS Rescue to work. A glimpse of them is at 5:50 if you need to see. The most important part is that when rescue is triggered, my aux3 channel which sets angle mode or horizon mode, puts the quad into angle mode. This has always been a MUST for GPS rescue to work, and without it the quad will totally just crash. Again, I just copied what already existed on my explorer lr v2, but please just ensure that configure GPS Rescue + Angle mode to be activated at the same time similar to this as well. You seem to be extremely on top of all of this though so I think you got this!👍Send it out over a safe place for the first time without being high up, watch your arrow to point the direction home is correctly, then GPS rescue test is a-go! I'm sure you'll bring it back home every time!

THANK YOU JOHN for your amazing answer! I will be following each step in your video and line by line in your answer to get the GPS settings right when I set up my Explorer HD LR 4 v2.2. I am hoping to receive it by the end of the week from Flywoo in China. It will be coming with extra front and rear arms, side arm supports and antennas like you advised in your initial review. I can't fly my other drones anyway as the termerature high is -31C then down to -40C here. Amazingly it warm up tomorrow to -14C with snow. Cheers, Bill

This is a great question.! I just have that set to ‘On’ because I can get satellites quicker by taking off and flying around close by, rather than letting it sit on the ground plugged in. It also helps keep the vista cool. I land when there’s enough satellites to get a fix, and then arm/disarm the drone. You may want to keep it off, because if you accidentally fly off without a fix, then you have no GPS rescue. Your on screen display will warn you about this, however. I seem to get satellites a lot faster these days after making those changes from NMEA to Ublox, so I’m probably going to now change Allow Arming Without A Fix to OFF. It’ll prevent mistakes especially if you are new to GPS rescue. The betaflight 4.4 default setting is OFF so you may want to go with that.

Hi! The font is by SneakyFPV, you can find his video here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-quJ5fGhXyXM.html I'm using the V1.1 font I believe here. But I have switched to a different newer font. 😊 BTW I’m out right now flying BF 4.4 stable and working on the tune for this quad right now!

@@JohnCuppi Thanks for your quick reply. I used the same font, but I didnt do the Cli-inputs. With the Flywoo Explorer it just works fine, with other quadcopters I have that huge bolt letters... That why I asked. You think I will need to di the CLI-Inputs? Do you have that OSD in other Quads working?...So great to hear that you are working on the tune. Will you post it here or make an other Video? Thank you for your great work , mate. Enjoy your flight.

Yes. Stock 4.4 betaflight tune on this and crossfire preset. You can see I was able to do a little freestyle and it seems to fly okay. There is probably room for improvement for sure. I'll be working on it and update my diff and description.

This feature is available to all betaflight quads, but you’ll need to check what type of gps module you have. I just did some quick searches and I could not find any information at all that indicates whether or not the GPS supports UBLOX protocol at 10hz or not. Worst case scenario if it does not, you can swap it to an IFlight M8Q-5883 GPS module.

@@JohnCuppi thank you.

Before Betaflight 4.4, GPS Rescue existed, BUT it could not self land extremely close to where you took off at the home point, like in this video. The changes BF have made to "auto landing" return to home possible without needing a compass are truly fantastic. It adds so much more value to GPS Rescue mode now. GPS Rescue mode in versions prior could successfully fly your quad back to your general home area. It worked great for me on this quad every time. But, it had no way to land at the home point. You were expected to take back control; and it had to be landed yourself. Now if, for some rare reason you could not take control after a failsafe... you were kind of SOL! I have had the horrifying experience of watching a friend's quad on an older version of 4.x go into GPS Rescue, when a power flaw occurred on his transmitter. Anyway, it failsafed into GPS Rescue mode, and the quad just aimlessly floated around the home area at the set altitude. It's very, very unnerving to watch something like this happen in person. Eventually, it would have ran out of battery and landed... somewhere nearby. Luckily he MacGuyvered something together on the spot, got it fixed, and managed to get the quad down. The Auto Land feature of BF 4.4 would have been a god send in that moment. Also I agree, I need to do some further testing, it does seem a little rough on the way down. I'm not sure if I could change some things with that. There was some wind as you pointed out, so it wasn't ideal, but I think it was still good to test it in some breezy conditions anyway. The ground speed has got to come up, 5m/sec is a good starting point to test this, but that is definitely just too slow. Running out of space on this comment to answer the second half with the DJI stuff, so ending this here, and will write more in the next.

For the question regarding DJI Digital FPV. I currently own 3 digital HD FPV systems; DJI, HDzero (vrx), and WalkSnail (vrx). Flying my DJI setups with Caddx vistas and/or the original air units is what I still prefer. I am kind of pissed and disappointed though that DJI 'left' the original FPV system behind so to speak and hasn't done any updates to that side of things, but at this point the community has stepped in and gave us what DJI would not. The pretty on screen display that you see in this video is not stock, it's a software modification for the DJI FPV Goggle V2 that adds a fully featured on screen display and lets me record it to show in videos like these here on youtube. I think the DJI O3 setup is really nice too, but I've only sort of experienced that through flying the Avata. There's a lot of latency and compromises there, it's not what I would prefer to fly with every day. Overall, right now is such a difficult time to be buying into any HD FPV ecosystem. There are benefits to all of them out there right now. Talking about the current state of things and choices could fit into an entire video itself. Consumers have a lot of competition in this space right now which is great for all of us, but meanwhile they're all rapidly developing things and changing how the choices are weighed it seems every couple of months. Just look at HDzero with their new 90fps camera and awesome goggle. Even WalkSnail, as bad as it was a year ago, I have to say has been impressive to me in its current state and there is some potential there if Caddx continues to develop it. I think that if you can build a drone and are confident in soldering, that you should go that route -- but there also wouldn't be anything wrong with selecting a bind and fly quad with quality comparable components either. There is something to be said for having a complete, professionally built solution all set and done to "learn backwards" from. It's how I started in the FPV hobby, and many others as well!

Nice, hey, are you using iNav on the flywoo explorer?

@@JohnCuppi Yes, it is just the analog version of the quad.

@@vasobg12 That’s cool. What version are you using? I remember there was an unofficial iNav target a while back that got posted and I’m not sure if they ever added it as an official for flywoof7nano or not.

@@JohnCuppi Yes the target is officially added. I am using 6.0 features realise firmware , at thise time 6.0 firmware is at RC1 state (does not have the time to tast is yet) but I have same results with 5.1 firmware. Note that having compass in your quad is required to use these features!

@@vasobg12 Great information, I didn't know it was official now.👍Yeah, I know a compass is required for iNav and multirotors. I flashed mine with an unofficial inav build a bit back, and realized that I was not going to be able to use it without a compass.

Yes. I do think the tune needs work. I am going to work on it when weather warms up around here and update my diff config file.

I should have probably checked the accuracy of my barometer before doing this. Unfortunately I didn't. I don't remember it being way off, though. It's not like I land for example and recall it thinking I'm in the negatives. I'll do a flight when I can and let you know if I notice anything is off.

@@JohnCuppi Thanks, no worries! I'm going to try covering the barometer with a bit of foam to see if that helps. It's pretty exposed to the 7" props, I imagine that could throw it off.

I wonder how landing works under the covers. I wonder if it uses both the barometer and the gyro to determine that it landed.

@@RebelGoatFPV BF doc on GPS rescue does state "If a Baro is present, enabling it will improve IMU altitude estimations significantly...Usually this results in better altitude control and more reliable landings." So it's definitely using the barometer to aid in the landing process. My barometer is on the FC itself.

@@RebelGoatFPV Yes, the Baro plays a role in landing phase. As the quad enters ground effect and pressure rises, this is read by the baro as a quick drop in altitude. This translates to a quick rise in the Throttle Dterm (gps throttle pids) which can trigger the disarm on it's own before it touches down, sometimes.

Not sure, sorry -- I do not have an O3 air unit.

RID sucks but the implementation of this won't be a net positive or negative in that regard. BF's GPS rescue and the GPS units we buy off the shelf by themselves alone will never become "approved" for RID by the FAA. You're probably gonna see stick on broadcast modules this year for around $20-$30 you can move from drone to drone, and they'll be self-contained with no connection to the FC.

You can not go wrong with an ExpressLRS 2.4 Ghz or Crossfire at 900mhz control link. My preference today would be ExpressLRS.

@@JohnCuppi 🥰 thank you

Hi, you need the WTF-OSD mod for DJI fpv goggles. You can find it at fpv.wtf/

My board is an F7 so it doesn't have softserial at all. I guess the earlier versions may have had softserial configured for the GPS? I'm assuming that's not the LR V2, it's the V1? Softserial setup are additional commands that need inputted to be activated/setup, the ports page by default will only show hardware uarts.

@@JohnCuppi Thank you John for taking the time To answer my question ! Have a great day

Best to wait for the final BF 4.4 stable release I'd say. I'm currently not really 'sending it' much until then. I'm flying around in an an area where I can do the long walk of shame and get it no matter what, but nothing over water, etc.

That was a great video John! Thank you for all the information soon as I am be able to get my quad to arm since upgrading to 4.4.0 my Armin is disable.

@@luigivincenzi9155 Thanks!

It disarms itself. Also, strongly suggest moving toward updating to 4.5 if you haven’t already.

@@JohnCuppi this is all new to me, haven’t even flown yet, just learning how to use beta flight, I just downloaded it on to my computer yesterday, it was a version of 10.9 or something like that, can’t remember right now. Is it a GPS version 4.5?

I found my default settings in betaflight 4.1 were NMEA and 9600 baud, which seemed stupid slow in retrospect but I didn’t know better. With ublox I seem to be able to acquire more satellites. I’m not sure why that is. It still takes 3 min or so to get enough sats before it’s “hot” for the afternoon to fly. Try uBlox, and set the baud rate to 57600 (mine was automatically negotiating that speed in BF before I set it manually) and see how it works for you. Can’t think of a good reason not to use uBlox! The implementation of UBLOX in the slightly older (4.3) and current Betaflight code is far superior compared to NMEA. Does your v2 have copper shielding in the wires like mine as well?

@@JohnCuppi Thanks John, I don't have the copper shielding yet but was planning on sorting that out before Spring how hard would it have been for Flywoo to fit it lol. I will give it a try and see what happens thanks 👍

@@BMFPV On later V2 versions like mine, they actually do shield the wiring. It’s important, so definitely something to do before spring. I’m looking forward to spring as well, the weather is so droll…

@@JohnCuppi My one's 2.2 I'll have to get it out and have another look? 👍

Just checked and no copper at all and not even twisted, I shall get some copper tape ordered lol 👍

Weird. Mine has no motor mapping at all so they must have changed something… if you flash back to the older version of bf it had, Does it work?

@@JohnCuppi Hey, yes if i switch back to 4.2.11 it works. If i use the Firmware higher than that i get trouble with the mapping. Also with version 4.2.11 i had problems with the motor mapping. But with the correct CLI file i got from Flywoo it worked. But now i can not use this mapping. Regards Wolfgang

Sorry mybe i have missanderstand somthing. I also tryed to update the 4.4 FC firmeware with an older BF Version. There is the same phenomenon. In the beginning motor 3 dosent work. After i use the mapping from by backup no motor is working

It’s coming in 4.4.1, they’ve addressed this issue but the best you can do for now is try playing with the ground speed and the altitude option. Mine disarms early if my ground speed is set any higher than 7m/sec. A number of great improvements have been made further to gps Rescue in 4.4.1 but it’s not out yet. Development version only.

Just a different development philosophy and prioritization with time spent on features. BF’s GPS Rescue has always been more of an afterthought rather than a feature focus. That’s why I think call it GPS “rescue” and not “return to home” since its main goal has never been to self-land you back at the home point. Just bring your quad back toward your home location so you can take control again yourself. That’s still recommended, I think. Anyway, most people flying BF are using it for freestyle or racing. So GPS functionality just isn’t the core of the project’s priorities. It’s all an open source and completely free development from both projects, so I’m super grateful they improved it. If I was very serious about GPS and wanted position hold etc, I would be on iNav and have a compass.

Also thanks I appreciate adding your input and for watching!

The font is by SneakyFPV, you can find his video here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-quJ5fGhXyXM.html I'm using the V1.1 font I believe here.

It does not work if you arm the quad before you get a fix. It'll even warn you "GPS Rescue Off" if you don't have a fix when you take off. Here's why I have kept "Allow Arming Without Satellite Fix" on: I can fly around close by while I wait for a fix, and I get that fix significantly quicker in my experience this way, rather than just waiting with it on the ground. My DJI vista also doesn't have to cook while I fly around. Once I get the minimum number of satellites required for a fix, *then* I can land, rearm, and GPS rescue will be enabled.

@@JohnCuppi so if you lock it once after you put new battery there will be same spot? or you have to do this every single lipo?

@@Bobikska1 Not exactly. You do need to wait for a lock/fix between each battery, HOWEVER-the GPS receiver has a short memory that it retains of whereabout the satellites are after finding them for the first time. So to be as clear as possible, your first battery of the afternoon will be the slowest to find satellites and get a lock. Your next battery, if plugged in after the first flight, will be significantly faster, nearly almost instantly it will find sats and get a lock. It uses its list known memory of satellites near you and tries to reconnect to them. Honestly, though? The absolute safest setting is to disallow arming without a fix. Because if you accidentally get caught up in the moment, take off and forget to land again, or wait for that fix, then you have no gps rescue. It’s fine as long as you’re paying attention to everything, but if you want to minimize your risk of making a mistake, turn “allow arming without a fix” off. These days after making those gps changes my flywoo is finding sats so much faster, that I don’t really feel like I need to have “arming without a fix” enabled anymore.

GPS rescue will not work at all if you take off before you have a 3D fix. However, it is nice to be able to arm and fly around to cool off the vista while you wait for the initial satellites to lock for the day. You can also acquire the initial sats a bit faster this way as well. I usually keep a small pack and fly it around for a minute or two to get sats, not the one I intend to do a real flight with. Helps to do a preflight check, etc. When you have enough satellites even with allow arming without a fix =on, you can just land, re-arm, and gps rescue will be active.

Awesome 👌

The OSD is a hack/mod for DJI called WTFOSD, you can find videos on that here on youtube.

This issue has been fixed in later firmware, it was something that occurred in the RC and 4.4.0 - Have you tried 4.4.2?

@@JohnCuppi I have 4.4.1 but mine is worse than yours in the video. I'll try .2 tomorrow. Thanks for the info.

@@michaeln.8311 definitely give it a try and see how it goes, 4.4.2 brought significant improvements to the GPS rescue. github.com/betaflight/betaflight/releases/tag/4.4.2 By the way, what GPS are you using? M10 or M8?

@@JohnCuppi I use the Flywoo goku GM10 Pro I'm very happy with it. GPS rescue landing sometimes less than 1m away.

@@michaeln.8311 Ah that’s important to know. With m10 gps in particular, unfortunately there are issues with them in 4.4.x. There are issues with the update rates, auto config and pitch anomalies during RTH that you describe. Auto config basically doesn’t work with BF 4.4.x for m10 gps, while it does for m8. Betaflight currently supports a maximum update rate of 10 Hz, so using 15 Hz or 16.667 Hz GPS causes twitching or bobbing on the pitch axis during return flight. And I think some M10 gps can run at this rate, it’s really important to use ublox u-center to configure m10 gpses to be sure youre at 10hz since auto config doesn’t work. Betaflight 4.5 will really improve m10 gps performance, but it’s a ways off

In betaflight in the ports tab, you can manually switch the baud rate there, but you might only be able to set it at 57600 baud. 115200 may not be accepted as a baud rate by the GPS itself until you access it with ublox u-center and increase it there first. That's what I had to do with my V2.0 flywoo GPS. Ublox u-center had an option where I could configure maximum accepted device communication rate, and I raised it. Then, BF was able to negotiate the fastest allowable baud rate in the options. You will know right away if when you save your GPS baud rate setting in the betaflight ports tab to 115200, if when you reboot the quad and check it again, it did not take effect, and automatically downgrades it to 57600. HOWEVER, don't go running on a wild goose chase to do this. This is actually fine, though, as I've recently learned from some of the other GPS rescue tutorials that have come out now. It seems not necessary to increase the baud rate beyond 57600 for this feature to work. I would NOT want to use anything lower, though, make sure it's 57600!

Thanks! I was just wondering if it will improve my GPS in picking up satellites and comms wise. Thank you.

@@russgrgda8198 The faster the navigation update rate, the more messages have to be sent from the GPS to the flight controller. In order to keep up, the GPS/FC interface needs to run at a high enough speed. 57600 seems to be enough. I also think the faster communication rates keep sats from being dropped as easily, so they stay locked -/ but I could be wrong on this. I am getting way more satellites after changing from NMEA to Ublox and setting the higher aid rate than before, but - have made zero changes to the quad. So I can only conclude it DOES make a huge difference. 9600 baud over NMEA at 1hz was ungodly slow, even though it worked fine to return me back home area every time, that would have been a NO go for the self landing.

No. If you want position hold, you need to look into iNav and get a GPS that has a compass. The compass needs to be mounted away from the electronics too, they're suspectable to interference.

Are you on betaflight 4.5?

@JohnCuppi I use the firmware: 4.4.2 isn't that good ?

@@user-yk6qk8dj6xyou need to just upgrade to 4.5 and start from there, because 4.4.x had a lot of issues. 4.4.x is no longer recommended at all for GPS rescue. I’ve already upgraded the quad in this video to 4.5. make sure you start with the all new 4.5 GPS default settings

@JohnCuppi alright, thank you so much for helping me. Have a nice day 😊

Re-add soft serial using this as general guide: www.multirotorguide.com/guide/guide-how-to-set-up-the-softserial-uart/ I would reference your original betaflight configuration to see how softserial was setup and try to copy that. I’m assuming your explorer is a V1? They had soft serial on those for the gps unfortunately. I have absolutely no idea how it’ll behave at a higher baud rate either by the way, if you’re trying to use this self land feature.

I tried to reinstall the original but I've saved to computer as a .txt so it doesn't want to load it back onto fc it seems

Yes it's the v1 I just want to try get the soft serial port back at the moment and really have just gotten stuck on what to do

@@jacktaberner9878 You can open the file up and copy/paste all of of it into the CLI if you need to. That will do the same thing.

Thats ace ill try that now thank you so much no one has responded this much im new at this and just don't know what I'm doing I found out my rx is on uart1 GPS is uart2 and vtx was the soft serial

Interesting, I have not tried it without a barometer yet but I know having a barometer greatly helps BF GPS Rescue as a whole. True, iNav is the ultimate for doing GPS stuff, but as you said, it has limited flight controller support -- and some people do not want to deal with installing a compass.

@@JohnCuppi yes a baro greatly helps i suggest a speedy be 745 aio a compass comes with the mq8 gps module its tiny too. yea i find the cheap m80 gps modules that come with all long range stuff are just garbage hard to lock on etc its hit or miss with them too

@@jerrypatterson55 The M8Q-5883 is what I exactly what I run in my Heewing T1 Ranger airplane with iNav. That thing picks up satellites immediately, even inside the house. I originally purchased it for my Flywoo Explorer LR V2 to get position hold setup, but decided to bail on the idea since I didn't really need it.

I’ll update it tomorrow. I’ve got a new one for 4.4.1

@@JohnCuppi ok, i wait for you . Thank you🥺

@@tanin23605 4.4.1 improved gps rescue further, it’s more stable during return to home, and the speed of return can be faster :)

@@JohnCuppi i update last version but softserial lost. Then i coppy cli from google but cannot used.

@@tanin23605 mine does not use softserial, it’s hardware uart. Is your FC F745Nano? If not, my config won’t work, sorry.

Very conservative just to test. Definitely needs increased. A slow speed is a good starting point IMHO for testing this, based on what I've seen from other's vids.

Are you running any different esc firmware?