Betaflight 4.3.0 RC4 has now been published. Details have been added to the first post of this thread. There are no formal release notes yet but they will be added within the next day or two.

EDIT (6th April 2022): The formal Betaflight 4.3.0 RC4 release notes have now been added to the first post.

Betaflight Devs Wrote:NOTE: Long-range users should NOT rely on GPS Return until they have confirmed normal operation with a real radio-off failsafe!  Please report test results here!

Updates include:

• Extensive failsafe code changes.
  
• Improved RC link stability especially for Crossfire and ELRS over SPI.
  
• BMI Gyros now default their hardware filter to something closer to MPU gyros (no need for special filter setups).
  
• Scheduler and general stability fixes.
  

(02-Apr-2022, 03:31 PM)Rob3ddd Wrote:   I’m thinking of making the changes to betaflight 4.3.
  Is there any reason not to treat quad as a new build and start from ground 0?
 I use defaults and then I may tune and increase rates if needed.
  
 So TBS is saying with 6.x to do a factory reset on tx module and all receivers when going to 4.3?
Just out of curiosity is companies using different chips creating a bit of a tread lightly as you go effect?

Sure you can start fresh. No issue with that. I tend to copy the Modes, Rates, Ports. Just easier to take these parts from the old config

TBS is not saying to reset your Crossfire gear when going to BF4.3. There is no need for that. But you should upgrade to 6.17 because there is a bug in 6.16

Betaflight 4.3.0 RC5 was released earlier today. Details have been added to the first post of this thread.

GitHub Release Notes: https://github.com/betaflight/betaflight.../4.3.0-RC5

Take note that the following known issues are still not fixed in the RC5 release...

*** WARNING *** DO NOT use GPS Return with the RC4 and RC5 builds *** See GitHub issue #11527 for more details. While that issue has been reported for an ELRS setup, it's clear that the problem is present for an FC with any type of receiver connected to it.

Betaflight 4.3 Known Issues

• #11518 iFlight Beast H7 V2 no SPI-Flash (BMI270 version)
  
• #11517 FrSky SPI D8 - significant range reduction starting from PR #11380
  
• #11506 Kakute H7 Mini 4.3-RC4 locks up when performing certain actions
  
• #11502 UART1 shows twice in Ports tab, BF Configurator 10.7.2, Diatone Mamba MK4 H743
  
• #11496 clracingf4 goes into DFU mode when setting set_displayport_msp_serial
  
• #11488 Kakute H7 Mini SPI Flash not working
  
• #11484 ESC passthrough configuration behaviour change (non-BL Heli)
  
• #11473 BF4.3 RC3 communication with the equipment is constantly lost Flysky IBUS
  
• #11455 Lumenier H7 ultimate Receiver Glitching Out
  
• #11453 GPS working on H745 in BF4.2 but not in BF4.3 RC3
  
• #11448 BF4.3.0-RC3 Betaflight-tx-lua-scripts are not saved with SPI rx(ExpressLRS)
  
• #11440 HolyBro Kakute H7 Mini ESC Firmware Issue (Blackbox)
  
• #11438 ACC Trim via OSD has been broken somewhere during the implementation of the BF 4.3
  
• #11424 Dshot commands causing motors to spin (when BDIR=OFF)
  
• #11367 READY_BEEP
  
• #11347 OSD stats display shifted vertical moving the title off the top of the display
  
• #11334 'Reboot to bootloader' boots to wrong bootloader
  
• #11286 Power & Battery - Auto Calibration Issue
  
• #11260 CAMERA CONTROL on BF 4.3, difficult to enter the menu, or select the right line in the OSD
  
• #11233 VTX management via OSD don't work - BETAFPVF4SX1280 - 4.3.0 RC-3
  
• #11416 Configurator hangs after flashing / save & reboot
  
• #11157 Failure to boot caused by re-use of SPI pins.
  
• #11137 Dshot not working on latest master build on G4
  
• #10946 STM32G47X FLASH write not working with blackbox_mode=NORMAL
  
• #10936 Stats is not being saved when Rate profile adjustments are set (latest Master)
  
• #10825 JHEMCU F405 Pro AIO "No Gyro" Error
  
• #10796 Camera control does not work as it should on target ZEEZF7V2
  
• #10769 Can't change the blackbox logging on MatekF722SE Firmware
  
• #11527 Cannot regain control after failsafe (GPS rescue) because stick input is not registering therefore stick treshold cannot be reached
  

Not great news for H7 users then 

I've been running numerous builds of 4.3 on a couple of quads now for a while with no issues.
Not that I really needed to run 4.3, but being somewhat new to the hobby, i've been using it as a way to learn about setting up a quad from scratch and tuning etc.
So far so good 

(15-Apr-2022, 06:10 PM)Luap Wrote: Not great news for H7 users then   

I've been running numerous builds of 4.3 on a couple of quads now for a while with no issues.
Not that I really needed to run 4.3, but being somewhat new to the hobby, i've been using it as a way to learn about setting up a quad from scratch and tuning etc.
So far so good 

Yes, not good news at all. There even seem to be a number of issues with H7 FCs on Betaflight 4.2.x so having an H7 FC isn't a great place to be right now. Unfortunately some manufacturers decided to use H7 MCUs due to the shortage and long lead times of F7 MCUs. I was planning to get the Holybro H7 stack for my Apex 5" build but I think I will probably pass on that now and look for something else.

I know people are having some success with the Betaflight 4.3 RC builds but there are still way too many bugs in it for my liking and way more than we have seen in any previous Betaflight release. My quads will therefore be remaining firmly on Betaflight 4.2.11 (which they are flying great on) until we get a Betaflight 4.3.0 release with just a small handful of known bugs remaining.

One of the BF devs just posted that GPS failsafe does not work (and if it activates, you don't regain control when RC link is re-established) in RC4 or RC5, so something to be aware of.

I have been running the 4.3 RCs with good results on my whoops and small proximity quads, but a crash/flyaway with those would not be a major event. Hoping they can nail down the remaining bugs, because it really flies great!

(16-Apr-2022, 12:51 AM)V-22 Wrote: One of the BF devs just posted that GPS failsafe does not work (and if it activates, you don't regain control when RC link is re-established) in RC4 or RC5, so something to be aware of.

That is actually quite a serious bug. I read about some of the GPS issues I get sent in GitHub notifications but I didn't realise it was that bad. I see that the devs have now added a big warning message to the top of the release notes for the RC4 and RC5 releases that weren't previously there informing users of those releases NOT to use GPS rescue in those builds. I rely on GPS rescue so save my quad in one of the locations I fly where retrieving a downed quad in the event of a failsafe could be difficult, so I'm even more glad that I chose not to move to Betaflight 4.3.0 yet.

EDIT #1: I now see that the GPS Rescue problem as been reported under GitHub issue #11527. While it has been reported for an ELRS setup, it's clear that the problem is present for an FC with any type of receiver connected to it.

EDIT #2: There are now two emergency fix PR's to try and fix the GPS Rescue issue. See PR #11530 and PR #11531.

This whole Betaflight 4.3.0 release seems to have turned into a much bigger mess of bugs and unpredictable behaviour that was originally thought and it is clear that it was moved to the RC release phase way too early. From what we've seen in all the RC releases so far, the Betaflight 4.3.0 release just appears to have turned into one big alpha test by the whole FPV community.

Something which boggles me is that once firmware/software reaches release candidate phase there should be very little additional changes needed to fix remaining minor bugs in order to get to a full final release. There should never be any major code rework going on between RC releases and certainly not changes which actually break functionality that was working in a prior RC release. What is currently going on breaks the fundamental rules of the software application development lifecycle methodology and starts to make you wonder if there are any real controls in place for the development that is being done.

(15-Apr-2022, 11:36 PM)SnowLeopardFPV Wrote: I know people are having some success with the Betaflight 4.3 RC builds but there are still way too many bugs in it for my liking and way more than we have seen in any previous Betaflight release. My quads will therefore be remaining firmly on Betaflight 4.2.11 (which they are flying great on) until we get a Betaflight 4.3.0 release with just a small handful of known bugs remaining.

I keep an eye on the bug list, and from that I got the impression that remaining bugs were largely specific to certain FC setups. Very little of it looked related to any of the stuff I happen to have, so I took a brave pill and went for it! Also, my main test pig is a well thrashed Tinyhawk II which is mostly flown indoors, so no worries about flyaways etc with that. Once I built up trust with 4.3 on the Tinyhawk, I put 4.3 on 1 of my outdoor quads too (Mostly because I wanted the barometer to work at last!) and even then I waited until RC3 or so...

I've learned heaps about tuning during all this though, so thats good! Right!? 

I know I can’t paste in a dump or diff from 4.2.x when updating to 4.3, but I am okay to do so when updating from 4.3 rc3 to rc5, yes?

(19-Apr-2022, 12:22 AM)Lemonyleprosy Wrote: I know I can’t paste in a dump or diff from 4.2.x when updating to 4.3, but I am okay to do so when updating from 4.3 rc3 to rc5, yes?

Yes.

Betaflight 4.3.0 RC6 (and Betaflight Configurator 10.8.0 RC6) was released a few hours ago. Details have been added to the first post of this thread.

One important thing to note is that the GPS Rescue failsafe bug that was present in the RC4 and RC5 releases has been fixed in this RC6 release.

*** WARNING *** If you have an ICM-20689 gyro on your FC then DO NOT flash the RC6 build to your flight controller because doing so will risk irrecoverably damaging the gyro. See GitHub PR #11584 for more details.

• Betaflight 4.3.0 RC6 Release Notes: https://github.com/betaflight/betaflight.../4.3.0-RC6
  
• Betaflight Configurator 10.8.0 RC6 Release Notes: https://github.com/betaflight/betaflight...10.8.0-RC6
  

EDIT: Chris Thompson (one of the Betaflight devs) has also posted the following advice regarding configuration of GPS Rescue on Betaflight 4.3...

Source (Facebook): https://www.facebook.com/groups/betaflig...7348108475

In channel fallback settings, I understand the 1340 for the throttle level, but what does the 1500 mean for angle?

(10-May-2022, 08:43 PM)opossum.fpv Wrote: In channel fallback settings, I understand the 1340 for the throttle level, but what does the 1500 mean for angle?

It just sets that Angle Mode auxiliary channel value to 1500us i.e. the middle switch position of the 3-position switch used for that mode where a value of 1000 is the bottom (or back) position, a value of 1500 is the middle position, and a value of 2000 is the top (or front) position.

Thank you!

I tried a bunch of tests yesterday to get gps rescue set up again. I put GPS rescue on a switch and when I'd flip it on, the quad would drop.

I set up GPS rescue as the stage 2 failsafe and put failsafe on a switch. When I'd flip the switch to trigger GPS rescue, it would drop again.

I had between 10 and 14 satellites and bf said I had a gps fix. I used the settings from the post above (only a small adjustment for the throttle level)

Any idea why the quad would be dropping rather than GPS rescue activating?

Do not flash RC6 if you have an ICM-20689 gyro!

See here: https://intofpv.com/t-potentially-seriou...f4-3-0-rc6