(10-Mar-2022, 05:49 PM)SoCal_FPV Wrote: Joshua just did a video for pid tuning 4.3 and I’m still anxious to try it. Is it safe yet or not ?

Just roll the dice and cross your fingers 

I use a lucky rabbit’s foot and a four leaf clover. I just flew it on 4.3 and it feels great but the rates were super spooky on Actual so I changed it to my betaflight rates. I did get errors when I did the diff all and dump.

Eeeeck. I installed bf 4.3 rc3 on a quad last night. Now I’m scared and considering rolling it back.

I'm running BF4.3rc3 on two F411-equipped quads (one with ELRS SPI RX) and have had no issues once everything was configured properly. Just make sure your CPU usage is OK, and consider running a lower PID loop rate than usual for some extra cushion until they get all of the scheduler issues sorted and you should be fine.

I took a screen shot of the cli tasks.

#
# Building AutoComplete Cache ... Done!
#
# tasks
Task list rate/hz max/us avg/us maxload avgload total/ms late run reqd/us
00 - ( SYSTEM) 12 3 2 0.0% 0.0% 0 0 92 2
01 - ( SYSTEM) 984 8 1 0.7% 0.0% 7 7 8916 1
02 - ( GYRO) 7874 9 2 7.0% 1.5% 127 0 71606 0
03 - ( FILTER) 7874 39 24 30.7% 18.8% 1337 0 71606 0
04 - ( PID) 7874 77 50 60.6% 39.3% 3300 0 71606 0
05 - ( ACC) 984 11 6 1.0% 0.5% 25 3 8905 6
06 - ( ATTITUDE) 492 23 11 1.1% 0.5% 45 5 4459 11
07 - ( RX) 15 32 2 0.0% 0.0% 9 8 548 24
08 - ( SERIAL) 100 376087 20 3760.8% 0.2% 686 0 848 20
09 - ( DISPATCH) 984 7 0 0.6% 0.0% 5 8 8917 0
10 - (BATTERY_VOLTAGE) 49 6 3 0.0% 0.0% 0 1 453 3
11 - (BATTERY_CURRENT) 49 6 4 0.0% 0.0% 0 1 453 4
12 - ( BATTERY_ALERTS) 8 8 7 0.0% 0.0% 0 1 47 7
13 - ( BEEPER) 100 22 21 0.2% 0.2% 2 2 847 21
18 - ( TELEMETRY) 492 20 0 0.9% 0.0% 9 6 4304 1
19 - ( LEDSTRIP) 100 40 16 0.4% 0.1% 2 1 847 16
20 - ( OSD) 12 57 6 0.0% 0.0% 33 32 2262 29
22 - ( CMS) 20 7 6 0.0% 0.0% 0 1 181 6
23 - ( VTXCTRL) 8 3 2 0.0% 0.0% 0 0 47 2
24 - ( CAMCTRL) 8 8 7 0.0% 0.0% 0 1 47 7
26 - ( ADCINTERNAL) 6 4 3 0.0% 0.0% 0 0 10 3
28 - (SPEED_NEGOTIATION) 100 6 2 0.0% 0.0% 0 2 845 2
RX Check Function 11 3 10
Total (excluding SERIAL) 60.9%

I have been flying BF 4.3RC3 on my F7 equipped 3" and have to say that there has not been a single issue. This is one of two quads on my wall still flying BetaFlight and the other is still on 4.2.11, but considering how well is works on The Leaf, might just go ahead and update The Explorer as well.

I’ve had five flights and it’s flying great. Feels locked in and stable in dives. Definitely feels different then the 4.2.11.

Hello.
I have experienced weird micro-drops of RSSI dbm under RC3. It is a new build so it could be something else:

Nano Diversity receiver...
Anyone experiencing similar problems?

I don’t this its a Betaflight 4.3 RC3 bug.

What Crossfire firmware are you flying?

I posted this the other day in another thread:

(13-Mar-2022, 01:28 AM)kafie1980 Wrote: 6.14 had issues with telemetry causing Betaflight to assume its was an RXloss and would freeze/stabilize and recover.

Tested 6.16 for over 20 flights now and it seems stable.

Basically I was getting RSSI DBM warnings and even had a few scary RXloss situations.

Try upgrading to the latest Crossfire firmware.

One thing I forgot to mention, this was happening to me in BF4.2.11 which is why I assume it’s Crossfire firmware related.

There are a couple of bugs reported on github against 4.3 RC3 but they have not completely figured it out.

I just know when it happened after updating to Crossfire 6.14 and over 25 flights now in 6.16 and the issue appears to be resolved.

With the Crossfire / Tracer 6.x firmware updates, TBS have started recommending that you do a factory reset on the modules / receivers to ensure that any old persisted version settings are completely wiped in order to avoid any conflict with newer firmware versions, and they are also advising that you do a delete and rediscover of all telemetry sensors on your transmitter.

The sensor rediscovery is a bit of PITA if you have logical switches set up that are linked to telemetry sensors because when rediscovered there is no guarantee what order the sensors reappear in, so if they are in a different order than previously it means having to go through and edit any related logical switches, so also keep that in mind. Just make a note of the sensor order before doing a rediscovery and check to see if any that are linked to logical switches have changed their order after rediscovery.

What Crossfire firmware are you flying? 6.13.

Interesting thanks. I will try the new 6.17 Beta and see if I can reset the receiver and my Tango 2..

Gil.

I have only tried 6.16 so far and seems stable enough.

I am not aware that 6.17 beta was available and no idea whats in the changelog.

Crossfire 6.17 Release Note:

- disables CRSF V3 due to reports in a few Betaflight FCs.

(14-Mar-2022, 01:14 PM)SnowLeopardFPV Wrote: With the Crossfire / Tracer 6.x firmware updates, TBS have started recommending that you do a factory reset on the modules / receivers to ensure that any old persisted version settings are completely wiped in order to avoid any conflict with newer firmware versions, and they are also advising that you do a delete and rediscover of all telemetry sensors on your transmitter.

The sensor rediscovery is a bit of PITA if you have logical switches set up that are linked to telemetry sensors because when rediscovered there is no guarantee what order the sensors reappear in, so if they are in a different order than previously it means having to go through and edit any related logical switches, so also keep that in mind. Just make a note of the sensor order before doing a rediscovery and check to see if any that are linked to logical switches have changed their order after rediscovery.

  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?